Nofollow Link Checker: Dofollow & Broken Link Highlighter 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: ofcjecdgjjmaeakmfehceddgdpfdbgeb
Permissions (3)
- Execute scripts in pages
Related extensions
Nofollow & Dofollow Link Checker — SEO Link Highlighter | LinkVizDeveloper
Follow, Nofollow Link Checker 🔗Developer
Nofollow Link CheckerProductivity
Dofollow/Nofollow Link HighlighterMake Chrome Yours
NoFollow, Sponsored, UGC Links CheckerProductivity
Nofollow Link Highlighter — Dofollow, Sponsored, UGCDeveloper
Frequently asked questions
Is Nofollow Link Checker: Dofollow & Broken Link Highlighter safe to use?
Our latest automated scan rates the Chrome listing of Nofollow Link Checker: Dofollow & Broken Link Highlighter at 80/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 Nofollow Link Checker: Dofollow & Broken Link Highlighter require?
Nofollow Link Checker: Dofollow & Broken Link Highlighter requests 3 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Nofollow Link Checker: Dofollow & Broken Link Highlighter?
Nofollow Link Checker: Dofollow & Broken Link Highlighter is published by notionplates@gmail.com. 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.0
- Current listed version
- 1.0.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 0 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.