Full Page Screenshot & Screen Recorder by KitlyApps extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: oifbalpnffnifogoghcfmkikdegeknde
Permissions (6)
- Execute scripts in pages
- Manage downloads
- Capture tab content
Related extensions
FullPage Screenshot – Full Page Screen Capture & Webpage Capture ToolTools
Full Page Screenshot & Screen CaptureTools
Screen Recorder & Capture Full Page ScreenshotProductivity
Screenshot Tool - Capture Full Page, Tabs, or AppsTools
Fullpage Capture ScreenshotMake Chrome Yours
Capture Studio: Recorder & ScreenshotsTools
Frequently asked questions
Is Full Page Screenshot & Screen Recorder by KitlyApps safe to use?
Our latest automated scan rates the Chrome listing of Full Page Screenshot & Screen Recorder by KitlyApps at 82/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Full Page Screenshot & Screen Recorder by KitlyApps require?
Full Page Screenshot & Screen Recorder by KitlyApps requests 6 permissions. The most significant: Execute scripts in pages, Manage downloads, Capture tab content. See the full breakdown in the security report.
Who develops Full Page Screenshot & Screen Recorder by KitlyApps?
Full Page Screenshot & Screen Recorder by KitlyApps is published by avayeerfan. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.0.2
- Current listed version
- 1.0.2
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 1 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.