Haven
Troubleshooting → Device protection

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

Most likely

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.

Check this firstTwo different devices, both verified as set up correctly, both failing. A phone on mobile data passing while everything on the home Wi-Fi fails is the clearest version of this.
  1. 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.
  2. Re-run the verification check. Encrypted DNS defeats most interception outright.
  3. 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.
Cause 2

The router is set to hand out its own DNS and to block anything else, which some provider-supplied routers do by default.

Check this firstIt fails on every device on this Wi-Fi and passes on mobile data.
  1. Use the encrypted route above — it goes over HTTPS and the router cannot intercept it.
  2. 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.

A provider that blocks encrypted DNS as well.That is a policy decision by a company, not something a setting on your laptop can undo. It is exactly what Haven Voice is for — the complaint is pre-written and the coalition count is real.

Next door to this

I followed the setup, but the check still says this device is not protected

Still stuck?

Two doors, and neither of them is a queue you never hear back from.

Report this — it did not work Have a technician do it with you Re-run the protection check My provider is the problem

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.