Email Tracker + Email Tracking Detector & Blocker 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 reportEdge listing ID: bakpenfpnjfmhjjpcehnmapnnidjdane
Permissions (12)
- View open tabs
- Access browser cookies
- Execute scripts in pages
Related extensions
Email Tracker For Gmail - MailerPlexProductivity
Mailcastr - Email tracker for free.Productivity
MailTracker: Email tracker for GmailProductivity
Email Tracker + Email Tracking Detector & BlockerProductivity
EmailTrackApp — Email Tracking & Read Receipts for GmailProductivity
Unified Inbox Checker for Gmail™Communication
Frequently asked questions
Is Email Tracker + Email Tracking Detector & Blocker safe to use?
Our latest automated scan rates the Edge listing of Email Tracker + Email Tracking Detector & Blocker at 73/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 Email Tracker + Email Tracking Detector & Blocker require?
Email Tracker + Email Tracking Detector & Blocker requests 12 permissions. The most significant: View open tabs, Access browser cookies, Execute scripts in pages. See the full breakdown in the security report.
Who develops Email Tracker + Email Tracking Detector & Blocker?
Email Tracker + Email Tracking Detector & Blocker is published by 11669532 Canada Inc.. 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
- Edge
- Checked version
- 5.0.67
- Current listed version
- 5.0.67
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 20 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.