01 / LOOK UP
See what is published
Query A, AAAA, CNAME, NS, MX, TXT, CAA and DMARC through two independent public DNS resolvers.
DNS LOOKUP & WEBSITE DIAGNOSTICS
Is your website
connected correctly?
Enter your domain. Check your DNS settings and find a clear next step.
Free · no accountLive DNS queriesSnapshots stay on your device
DNS recordsUnderstand issuesNext steps
01 / START WITH YOUR DOMAIN
02 / YOUR DNS REPORT
Not tested: HTTP redirects, SSL certificates, worldwide propagation and recursive SPF limits. Check these separately.
DNS observations only: no uptime or security guarantee. AD=false does not prove DNSSEC is broken. Missing email records may be intentional.
Full DNS records and technical details
Answers are grouped by resolver. TTL is remaining cache lifetime, not a guaranteed propagation deadline. Geographic and CDN answers can legitimately differ.
Raw DNS / JSON
LESS GUESSWORK, MORE CLARITY
From a DNS record to your next step.
02 / UNDERSTAND
Find what needs attention
Separate a missing record from a failed query. Review Blogger targets and basic email authentication without a misleading health score.
03 / FIX & COMPARE
Change, then verify
Save a baseline before editing your DNS provider. Re-run the check and compare added and removed records. Export a report for your records.
CONNECTION PLAYBOOK
A practical path to a working domain.
Blogger
Use the blog CNAME shown in Blogger (usually ghs.google.com), plus your account-specific security CNAME. The root-domain redirect uses separate A records: 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21. Do not replace a working subdomain with root A records. If CAA restricts issuance, review letsencrypt.org permission and inherited CAA.
Blogger official guide ↗WordPress / Cloudflare
WordPress hosting providers specify different IP addresses and CNAME targets. Copy your host’s exact target into the expected-value field. Cloudflare proxying can hide origin IPs and CNAMEs; public DNS cannot validate the hidden origin. Also review hosting domain mapping, proxy mode and HTTPS in your provider dashboard.
Cloudflare official guide ↗Site launch checklist
1. Check the exact host and www separately. 2. Confirm your platform’s expected target. 3. Preserve MX and TXT when migrating. 4. Review security CNAME or TXT ownership tokens. 5. Open the site to check redirects and HTTPS manually. 6. Verify Search Console in Google’s dashboard. DNS alone cannot confirm those last two steps.
DNS questions, plain answers.
Why do Google and Cloudflare return different answers?
Caching, DNS changes, CDN routing and geolocation can produce different responses. A mismatch is an observation, not proof of an outage. Neither resolver tells you what every visitor worldwide sees.
Does an empty result mean my domain is broken?
No. NOERROR with no matching answer means that record type was not returned. NXDOMAIN means the queried name does not exist according to that response. SERVFAIL and timeouts need investigation and must not be treated as missing records. A domain does not need every record type.
Can this fix DNS automatically or check SSL?
This browser tool only reads public DNS. Make changes at your DNS provider and recheck. HTTP redirects, certificate chains, origin health, global propagation, inherited DMARC/CAA and recursive SPF lookup counts require additional checks and are not certified here.
What do SPF, DMARC and DKIM tell me?
SPF describes authorized senders; DMARC describes policy and alignment; DKIM publishes keys under a selector chosen by your email service. This tool flags duplicate SPF records, +all and basic DMARC policy. It does not perform a full mail-delivery audit or count recursive SPF lookups. Ask your email provider before changing live mail records.
Where are my queries and snapshots stored?
Your browser sends queried hostnames and your IP address to Google and Cloudflare using HTTPS. No DNS provider credentials are requested. Baselines are stored only in this browser’s local storage until cleared. Exported reports include the entered hostnames and public DNS answers. This site uses Blogger hosting, which may process standard service data.
About DNS Fix Lab
A free, independent troubleshooting tool for site owners and developers, operated as part of kioptrix.com. It is not affiliated with Google, Cloudflare or nslookup.io. Checks explain public DNS observations, not guaranteed diagnoses. No account, payment or DNS-provider access is required.