What this checker shows
The tool queries A, AAAA, CNAME, MX, NS, TXT, CAA and SOA records. Results include the record value and TTL returned by the selected public resolver.
Free website utility
Look up the public DNS records for a domain. Check common records such as A, MX, NS and TXT to troubleshoot configuration and verify what a public resolver currently returns.
| Type | Name | TTL | Answer |
|---|
The tool queries A, AAAA, CNAME, MX, NS, TXT, CAA and SOA records. Results include the record value and TTL returned by the selected public resolver.
A DNS answer is one resolver’s response at lookup time. Cached answers may remain visible until their TTL expires, and other resolvers can show different results during propagation.
DNS is the plumbing behind everything: a wrong A record takes the site down, broken MX records silently kill email, and missing TXT records break SPF, DKIM and domain verification. For SEOs, DNS lookups verify ownership records, confirm redirects during migrations, and diagnose why a site or its email suddenly stopped working. Seeing TTL values also tells you how long a change will take to fully propagate.
It queries A, AAAA, CNAME, MX, NS, TXT, CAA and SOA records. Choose one record type for a focused check, or run all common types together to get a full picture of a domain's DNS configuration in one pass. TXT records are especially useful for verifying domain ownership and email authentication setups.
No key or account is required. Your browser sends DNS-over-HTTPS lookups to Google Public DNS, which offers a web-friendly JSON interface. The page does not save the domain you enter. The tool is informational only; it never changes any DNS settings on your behalf.
No. The tool reports the answer from Google Public DNS at lookup time. DNS caches, TTLs and resolver locations mean other resolvers can return different answers until changes have fully propagated, so check again after the TTL expires. Propagation is complete only when resolvers worldwide consistently return the new values.
MX records decide which servers receive a domain's email, so a wrong or missing MX record silently breaks inbound mail. Marketers and SEOs check MX and related TXT records when setting up email authentication like SPF and DKIM, which protect deliverability and sender reputation.
Resolver: Google Public DNS. A DNS lookup is informational and does not make changes to your domain settings.