Guide Your website is blocked. Work out which filter did it, then get unblocked.

Visitors tell you your site is "blocked," and the warning page names someone who isn't you: Comcast, Cisco, Google, a school district. Your server is probably fine. A filter between the reader and your site made a decision about your domain, and each filter keeps its own list and runs its own review process. The work is to prove the site itself is healthy, work out which filter is doing the blocking from where the block appears, fix whatever got you flagged, and then ask that specific filter for a review.

What a block page actually is

A block page is an interstitial drawn by something sitting between your visitor and your server: the browser's own reputation system, a DNS filter on the network they're using, an ISP's threat or parental controls, or a workplace firewall. Most of them name their maker on the page. That name is the vendor whose review process you need, not the vendor you feel like complaining to.

There is no single unblock list

Google Safe Browsing, Microsoft SmartScreen, Comcast's Xfinity controls, Cisco Umbrella, Spamhaus and the antivirus vendors each maintain separate reputations for your domain. Being cleared by one does nothing for the others. Fix the underlying cause once, then walk each review queue that actually flagged you.

What stops it working

Requesting a review before you've cleaned the site. Safe Browsing rejects reviews for sites that still serve the problem. Emailing the wrong queue. Cisco's rapid no-reply review form explicitly does not accept unblock, false-positive or categorization requests — those go through Umbrella support (checked October 12, 2026). And fighting someone else's parental controls. If a household or school filtered you on purpose, the account holder manages that list, not you.

Prove the site is actually up

Open your site on your phone over cellular, then on your home Wi-Fi, then through any VPN or proxy you have. If it loads everywhere except one network, the site is fine and that network's filter is the story. If it fails everywhere, you have a hosting or DNS outage, and nothing in this guide is the problem yet.

Check the basics a filter report won't tell you: the domain resolves, the certificate is valid, and the page returns a normal status code. A site that's half-broken can look like a block from the outside.

Let the pattern tell you which filter it is

One browser warns, other browsers don't: the browser's own reputation system — Google Safe Browsing in Chrome and Safari, Microsoft SmartScreen in Edge. Not your network.

One network blocks, cellular doesn't: a DNS or ISP-level filter — Xfinity parental or threat controls, a school or workplace firewall, or a public DNS filter like OpenDNS or CleanBrowsing. This is the classic "Comcast blocked me" case.

Everyone, everywhere, gets a warning: your domain has landed on reputation blocklists that security products subscribe to. This is the most serious variant, because the flag follows your visitors around.

Browser warnings: Safe Browsing and SmartScreen

Look your domain up in Google's Safe Browsing Transparency Report. If it's flagged, Google's Search Console shows the exact problem under Security Issues — typically malware, deceptive content, or harmful downloads. Clean the compromise, then request a review from the same panel. Reviews are judged by people and by re-scans, and a still-infected site fails them.

SmartScreen works from Microsoft's own URL reputation. If Edge or Defender warns on your site while Safe Browsing is clean, report the false positive through Bing Webmaster Tools after you've verified the site is clean.

ISP and DNS filters: Xfinity, Umbrella, schools and workplaces

If a household's Xfinity xFi parental controls or Advanced Security filtered you, the account holder manages that list — Comcast will not unblock a site for someone who isn't their customer. The practical route is to ask the person whose network it is. Business and school networks route through an IT department and a product like Cisco Umbrella, Palo Alto or Fortinet, and they can see and override the category the filter assigned.

For DNS-security products, check how your domain is categorized: Cisco's Talos Intelligence lookup shows the Talos verdict. A categorization dispute is a support case, not a form fill — Cisco's rapid review form says plainly that it doesn't take unblock or false-positive requests. DNS filter vendors generally have a domain-category or listing-request channel; expect days, not hours, and answer their questions about what the domain hosts.

Blocklists: is your domain or your IP listed?

The reputation lists that security products quietly consult include Spamhaus' domain blocklist, SURBL, and abuse.ch's URLhaus. Look your domain up directly. A listing usually traces to something concrete: a compromised site serving malware, spam sent from the domain, or a phishing lookalike page someone staged on your infrastructure.

Shared hosting adds a wrinkle: your site can be blocked for a neighbor's behavior. Dozens of sites share an IP address, and a spam wave from any of them can poison the address for everyone. If your domain is clean but your IP is listed, the durable fix is cleaning the server and, if the neighbor problem persists, moving.

Fix the cause, then watch the flags drop

Every one of these systems wants the same thing before it clears you: the cause gone. Remove the malware or spam, close the compromised account or plugin, take down the lookalike page — whatever the flag actually was about. Then run the review requests from the sections above, one filter at a time, and keep the responses. Re-check the lookups weekly until every one is clean; listings linger after the fix unless someone asks for removal.

Treat a block page as a reputation event, not just a technical one. If your site was compromised badly enough to be flagged, whatever was staged on it may already be indexed, mailed around, or reported elsewhere.

Flagged, filtered, and invisible to customers

A block page is a reputation problem wearing a technical costume. We find out which list or filter has your domain, clean whatever triggered it, walk the right review queue, and keep monitoring so the next flag surfaces in days instead of when a customer mentions it.

Have us do it.

See the scope, price, and next steps for the help this guide describes.

See the service

Every filtered network is a closed door

While your domain sits on one blocklist, every customer behind that filter sees a warning instead of your site. We diagnose the flag, fix the cause, and handle the review queues. Search and AI visibility work assumes your site is reachable; we make sure it is.

Run a business that lives on its website? See how we keep it reachable

Explore your options

Every guide we publish is free and ungated. Browse all of them, see what we do and what it costs, or read why we built this company.

Written by Drew Chapin, who ran all of this on his own name first.

© The Discoverability Company Privacy Terms