DNS Record Checker
Enter a domain or hostname to look up its supported DNS records through Google Public DNS. This is a record lookup, not a worldwide propagation test.
Enter a domain above to see its records.
Records are fetched via Google Public DNS and cached for this session. Use Refresh to fetch fresh results. If you just changed nameservers or email records, allow time for caches to expire — what you see here is what Google Public DNS currently returns, not a global propagation test.
What does a DNS record checker do?
A DNS record checker asks a DNS resolver for published information about a hostname. That information can help you check where a website points, which servers receive its email and whether a domain-verification value is visible. This tool uses Google Public DNS; it does not inspect every resolver around the world.
DNS and hosting have different roles. If the distinction is new to you, read our domain vs hosting explanation before changing records.
Which DNS record should you check?
| Record | Typical purpose | What to compare |
|---|---|---|
| A | IPv4 address for a hostname | The address supplied by your hosting provider |
| AAAA | IPv6 address for a hostname | The applicable IPv6 destination |
| CNAME | Alias from one hostname to another | The target hostname supplied by the service |
| MX | Mail-routing destination and priority | Your email provider’s instructions |
| TXT | Text values, including some verification and email-policy data | The exact expected value and hostname |
| NS | Nameserver information for the queried name | The intended DNS provider and delegation context |
For a technical record-type reference, see Cloudflare’s DNS record documentation.
Query the exact hostname a service gives you. A verification value at a subdomain does not necessarily appear when you query only the root domain. A CNAME is often attached to a hostname such as www, while some email-related TXT records use more specific names.
How to use the checker after moving hosts
Enter the relevant hostname, run the lookup and select the record type. Compare the returned value with the new provider’s instructions. Also check whether email records should stay with the existing mail provider rather than move with the website.
Do not cancel the old hosting merely because one lookup returns the new address. Verify the website, important forms and email separately. Our WordPress migration guide explains the broader cutover process.
TTL and why an old value can remain visible
TTL is a cache-related time value shown in seconds. A change at the authoritative DNS provider does not instantly replace every cached answer elsewhere. The resolver queried, previous caching and the kind of change affect what you see. There is no single countdown in this checker that proves a change has completed everywhere.
If a repeat lookup appears unchanged, refresh the lookup where supported or rerun it after reloading the tool. Compare another appropriate resolver when necessary, rather than treating one response as a global verdict. A CDN can also affect which service address appears, so an unfamiliar IP alone does not establish a hosting problem.
What a missing answer can mean
There may be no record of the selected type, you may have queried the wrong hostname, or a resolver/network error may have prevented a usable answer. A good diagnostic result distinguishes these cases. Do not keep adding duplicate records simply because a lookup did not return the value you expected.
If DNS looks correct but WordPress still returns an application error, continue with the WordPress troubleshooter. DNS resolution and application health are different checks.
Common questions
Is this a global DNS propagation checker?
No. It reports the response from Google Public DNS, not a network of geographic test locations.
Can it check domain verification?
It can display supported record types. Query the exact name and compare the result with the verification service’s expected value.
Does an MX record prove email works?
No. It is one routing check; account configuration, delivery policy and other factors still matter.
Does a DNS lookup change my settings?
No. A lookup reads published records. Editing DNS requires access to the service that manages your DNS zone.