Public DNS tools

DNS filtering tools for clear, bounded checks

These DNS filtering tools inspect the hostname a resolver can receive, separate it from URL details, and compare records returned by two named public resolvers.

See the boundary before testing a rule

A DNS decision applies to a hostname. It does not select one page, search phrase, account screen, or file when those destinations share that hostname.

This check stays in your browser and sends no request to the entered destination.

Compare answers from public resolvers

A comparison can reveal different public records or DNS response codes. It does not inspect the DNS resolver selected by your operating system, browser, router, VPN, or filtering service.

Only after you select Compare, your browser sends the hostname directly to Google Public DNS and Cloudflare. Those normal cross-origin requests also disclose your connection IP and browser request metadata, including this site's origin and referrer under its referrer policy. Veilty does not proxy or store these lookups.

Cloudflare 1.1.1.1

Results appear here after you run the comparison.

Google Public DNS

Results appear here after you run the comparison.

Read the result without overclaiming

Different answers may be normal because caches, geography, and record changes affect public DNS. A matching answer does not prove that filtering is active.

What this comparison checks

It sends the same record request directly to two named DNS-over-HTTPS services and shows each response independently. HTTP errors, timeouts, and DNS response codes remain separate rather than silently falling back to another provider.

What requires a different test

To verify a filtering policy, use the filtering provider's documented harmless test hostname from the affected device and network. Never test with a live malicious domain. This page does not discover system, router, VPN, or browser DNS settings.