Filtering appears active
The control responded, while the configured test hostname could not be reached from this browser and network. A block or other network interruption can cause that result.
Device check
Check this browser and network.
Run a small reachability test from this browser. It can indicate whether the configured test hostname is reachable on this network; it does not confirm real DNS behavior or cover other apps and devices.
Ready when you are. Nothing has been tested yet.
What the result means
A narrow browser check, with an honest fallback.
Test hostname reachable
Both requests responded. Filtering may be bypassed for this browser or network, or the test hostname may not be covered by your configuration.
Inconclusive
The control was unavailable, or this environment has not enabled its test hostname. Check connectivity and try again; do not treat this as a filtering result.
Test hostname:
This check stores no results, sends no analytics, and starts test requests only after you select Start check.
Select Start check to see if the temporary list is available.
Add the hostname above as a temporary exact deny rule, or copy the one-host test list link. In Pi-hole, add the URL under Lists and update Gravity. In AdGuard Home, add it under Filters → DNS blocklists. Remove the temporary rule or list when you finish and update Gravity again if you used the Pi-hole list.
Temporary setup
Remove a temporary setup when you are done.
- Open your DNS resolver, router, or device DNS settings.
- Remove the temporary rule or list you added. If you changed the device’s DNS server for the test, restore its previous setting.
- Apply or save the change, then refresh the resolver or reconnect the device if it requires it.