Something got through that should not have

It was reached inside an app rather than in a browser. A native app pins its own connection and ignores DNS entirely — no DNS product can see inside one, Haven included.

1. Open the coverage map — every app that bypasses DNS is listed there with its browser equivalent.
2. Swap the app for its website. The same account, the same feed, and it sits fully inside your protected space with Haven on the page.
3. Remove the app afterwards, or the swap is only a suggestion.

The page was already cached, or its address was already resolved. DNS answers live for minutes to hours, and a page open before protection started keeps working.

1. Close the browser fully and reopen it.
2. Try again after a few minutes.
3. If it still resolves, it is not caching — read the next cause.

The site is genuinely not in the resolver's adult-content category. Category lists are large and good but they are not complete, and a brand new domain can take days to be categorised.

1. Add it as a household rule — a block you write yourself applies on every device in the household and takes effect on the next sync.
2. Tell us, so the gap is on the record. The report form takes the address of the page.