Everything is set correctly and it still fails, on every device
When the setup is right on more than one device and protection still does not hold, the thing changing the answer is upstream of your house. Some internet providers intercept DNS and answer it themselves.
What is probably going on
The provider intercepts port 53 and answers DNS queries with its own resolver regardless of what the device asked for. It is usually done for their own redirect pages and it catches family DNS as collateral.
- Switch to the encrypted route, which interception cannot read: DNS-over-HTTPS at https://family.cloudflare-dns.com/dns-query on desktop, Private DNS at family.cloudflare-dns.com on Android, or the Haven DNS profile on iPhone.
- Re-run the verification check. Encrypted DNS defeats most interception outright.
- If it still fails, open Haven Voice: it records what happened, gives you an FCC complaint with the details already filled in, and shows how many other households have reported the same provider.
The router is set to hand out its own DNS and to block anything else, which some provider-supplied routers do by default.
- Use the encrypted route above — it goes over HTTPS and the router cannot intercept it.
- If you can reach the router's settings, look for "DNS relay", "DNS rebind protection" or a fixed DNS server, and turn it off. Haven does not depend on router settings, which are fragile and often locked; this is optional.
What Haven cannot fix here
Stated plainly, because a product that hides its edges is how you end up trusting a surface nobody is covering.
Next door to this
Still stuck?
Two doors, and neither of them is a queue you never hear back from.
Last checked 2026-08. Nothing on this page was written by a model — a made-up menu path is worse than no instruction at all, and this is the page somebody reads when they are already stuck.