Norton Safe Web "Norton blocked this dangerous web page"

What’s actually happening

Visitors running Norton 360 / Norton Security or the Norton Safe Web browser extension get a full-page red block instead of your site; everyone else loads it fine. It shows up as a chunk of users who simply can't reach you, often after a hosting move or a shared-IP neighbor got compromised. This is Norton's own reputation engine — separate from Microsoft SmartScreen and from Google Safe Browsing, so each has to be cleared independently.

Common causes

• A genuine compromise — injected malware, a phishing kit, or a malicious redirect Norton's crawler detected.
• False positive from shared hosting: a different site on the same IP was flagged and the reputation bled onto yours.
• A new or recently transferred domain with little reputation history, which the engine rates cautiously.
• Outbound links or embedded third-party scripts (ad networks, sketchy CDNs) that Norton associates with malware.
• A stale rating left over from a prior infection you already cleaned but never resubmitted.

How to fix it

1. Look up your current ratingGo to safeweb.norton.com and enter your URL. It shows Norton's verdict and sometimes the specific threat category (Malware, Phishing, Scam). This confirms it's Norton and not SmartScreen/Safe Browsing throwing the block.
2. If it's a real infection, clean it firstDon't dispute a live hack. Scan and remove injected files/redirects, patch the vulnerability, rotate credentials. Confirm clean output for the URLs Norton flagged before you submit anything.
3. Submit a dispute / re-rating requestOn the Safe Web result page use "Dispute this rating" (free Norton account required). State that the site is clean and give the fix date. Re-evaluation usually lands within a few days; it is not instant.
4. Rule out a shared-IP neighborIf your code is clean but you're still flagged, the IP may be the problem. Check what else resolves to your server IP; ask your host to move you to a clean IP or consider a dedicated one.