Advanced reference · Advanced
Read protection status and site rules
Use configuration diagnostics and static website-rule lookup without treating them as a recording of page activity.
Overview
The Protection Center helps explain which sources and rule groups Shield has prepared and what the browser has admitted. Site rules looks up installed rules that may apply to a hostname. Neither view is a recording of everything a page requested or every rule that ran.
Use these views to investigate a concrete question: is an added source available, did a browser limit omit rules, or could an exception override protection? For ordinary broken-page recovery, begin with website not working.
Where to find it
Open Shield’s Protection Center, then choose the protection-status view or Site rules. Enter a website hostname in Site rules, such as news.example. A hostname identifies the website scope; it is not a full page URL or a URL path search.
What to check
In protection status, read the overall state and the specific reason for a warning. Source details can distinguish bundled data from added-source downloads, show freshness or failures, and identify browser capacity limits. Page-fix setup is reported separately from request blocking and ad hiding.
A source can be configured but not fully active: it may be disabled, unavailable, awaiting a successful update, partly unsupported, or limited by the browser. A successful update means the source was fetched and processed; it does not establish that every line was accepted or that an ad disappeared.
In Site rules, read the current protection and exception state before interpreting the rule inventory. Rules listed for a host are potential matches from installed configuration. Request types, initiating websites, priority and current settings can change their effect. A disabled source can still have inventory evidence without its rules being active.
Preview a site rule
Site rules can prepare a request-blocking or request-allowing host rule. Review the generated preview and its stated scope before confirming. The action targets the hostname and its subdomains; it does not pause all of Shield’s protection on the website.
For example, a host block can generate ||ads.example^, while a host allow can generate @@||ads.example^. These are network rules. Allowing requests can permit ads or tracking to load, and it does not cancel an unrelated cosmetic hide. To pause the website’s protection instead, use the website controls described in pause and resume.
After confirmation, wait for the save result, inspect warnings and reload the affected website. Manage or remove the resulting rule under Settings → Protection → Advanced Settings → Your Rules. Site-rule confirmation uses a fresh proposal check; an old preview alone is not a completed save.
Limits
Configured, compiled, registered, admitted and observed are different kinds of evidence. Browser admission confirms a setup step, not that the intended request happened. Page-reported effects are labeled as unverified; they should not be treated as a trusted activity log.
Site rules does not start request capture. A missing hostname match can reflect scope, unsupported grammar or unavailable evidence rather than proof that a site has no ads or tracking.
Share a report
The Local report section lets you preview configuration diagnostics and download them. Read the preview before saving or emailing it. Report creation does not upload anything; contact support explains how to share useful context deliberately.