Manual check · Safari Content Blocker

Is Ward stopping this ad script?

This page checks that the test site is reachable, then tries one known advertising-script URL only after you press the button. The result is a useful signal, not a guarantee about every request.

User-triggered test

Run the Safari check

Open this page in Safari after enabling Ward's Content Blocker. The probe targets the pagead2.googlesyndication.com host, which is included in Ward's starter rules.

01 / SAME-ORIGIN CONTROL

Not run. This checks whether the current test page can be fetched again.

02 / THIRD-PARTY AD-SCRIPT PROBE

Not run. No request is made until you press “Run test.”

A successful script load means the current setup did not stop this URL in this run. A failed load can mean Ward blocked it, or that DNS, networking, a server response, another extension, or Private Relay prevented it.

How to read the result

Compare both checks.

Control succeeds + script fails: consistent with a blocked probe, but not proof. Retry after checking Safari settings and network access.
Script succeeds: Ward did not stop this probe on this run. Verify the Content Blocker is enabled and that Ward has installed rules.
Control fails: this page could not confirm its own host was reachable, so the script result is inconclusive.

Scope: this tests one Safari Content Blocker URL only. It does not measure all page requests, Advanced scriptlets, other browsers, or Ward All system filtering.

Safari does not expose a blocked-request count to Ward. Use Ward → Protection check for the operating system's extension status and installed rule-pack status.

OPEN SETUP GUIDE ↑