Free tool · no signup · runs in your browser
AI & DNS privacy leak test.
Four checks, about ten seconds. Who answers your DNS, which trackers still reach this device, whether attention-pull networks get through, and what an AI assistant would receive if you pasted your last prompt.
What leaves this device?
We check your resolver, send a bare request to 8 tracker endpoints and 6 push and recommendation endpoints, and score the result. The paste check below never sends anything anywhere.
The probe requests carry no cookies and no referrer. The test id and your resolver's address are kept only long enough to show your result.
AI prompt leak check
Paste a prompt, a log or a config you were about to hand to an assistant. Sentinel's scanner runs here in the page and marks what the assistant would receive.
Runs entirely in your browser. No request, no storage, no analytics on this box.
Under the hood
What the four checks actually measure.
The DNS check asks check.guardino.ai, a name that only resolves for a device whose DNS goes through Guardino, and lists the resolvers our test nameserver saw answer for you.
The two reachability checks send one bare request each to well-known tracker endpoints and to push and recommendation endpoints from our Mind Shield list: no cookies, no referrer, no cache. An answer means the name resolved and the host was reached. A failed request is reported as not reached, because a browser extension or a proxy fails the same way as a DNS filter.
The paste check runs Guardino Sentinel's secret and personal-data scanner inside this page. It highlights masked values, never the original, and nothing you paste is sent or stored.
Common questions
About this test.
Does the test send my data to the trackers it probes?+
It sends one request per endpoint with fixed dummy parameters, no cookies and no referrer. The endpoint sees a connection from your address and nothing else. That is the minimum needed to learn whether the name resolves.
Why does it say "not reached" instead of "blocked"?+
A page cannot see why a request failed. A DNS filter, a browser extension, a corporate proxy or a flaky network all fail the same way. We report what we can observe.
What happens to the text I paste?+
It stays in your browser. The scanner is plain code that runs on the page; there is no request, no storage and no analytics on that box. The highlighted values are masked copies.
Is a low score dangerous?+
It is the default state of most connections, not an emergency. It means your resolver and the usual trackers can see this device's lookups. Whether to change that is your call; the test shows you where things stand.