About this tool
Look up A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records, compare public resolvers, and check SPF, DMARC and DNSSEC.
Records are queried over DNS-over-HTTPS from Cloudflare, and compared with Google’s resolver and the 1CLIK server’s resolver to spot propagation differences. TXT records are checked for exactly one SPF policy, _dmarc is queried for DMARC, and the resolver’s DNSSEC validation flag is shown.
Example: check Domain = github.com.
After a change, resolvers keep old answers until the TTL expires, so differences can be normal for a while.
Quick steps
- Enter the address of a public page or domain.
- Press Check. The 1CLIK server visits it, which can take a few seconds.
- Read each line — Good, Improve, Problem or Info — with a hint on what to fix.
1CLIK’s server fetches only the public address you enter. Private and internal addresses are refused, and results are cached for a few minutes, not saved to your account.
FAQ
How does the DNS Lookup & Propagation Check work?
Records are queried over DNS-over-HTTPS from Cloudflare, and compared with Google’s resolver and the 1CLIK server’s resolver to spot propagation differences. TXT records are checked for exactly one SPF policy, _dmarc is queried for DMARC, and the resolver’s DNSSEC validation flag is shown.
What should I keep in mind?
After a change, resolvers keep old answers until the TTL expires, so differences can be normal for a while.
Why can the result differ from what I see in my browser?
The check sees what the server sends to 1CLIK, before any JavaScript runs. Sites can also answer automated requests differently, block them, or vary by country.