A / AAAA
IPv4 and IPv6 addresses used to find servers.
KEVRIQO · Domain tools
DNS Checker
Look up A, AAAA, CNAME, MX, NS and TXT records for any public domain.
Public DNS lookup. DNS queries run through a single public resolver with timeouts and shared server-side limits. No direct connection to the target website is made.
What do DNS records tell you?
DNS records connect domain names to addresses and services. This report shows what Google Public DNS currently returns, including nameservers and mail routing.
CNAME
Aliases pointing one DNS name to another.
MX / NS
Mail exchangers and nameserver delegations.
TXT
Text policies and verification records, including SPF.
How to check DNS records online
1. Enter a hostname
Type example.com or a subdomain such as www.example.com. Do not include https://, a slash or a port.
2. Run the DNS lookup
One check requests A, AAAA, CNAME, MX, NS and TXT information from Google Public DNS.
3. Review results and TTL
Read each record value and the TTL reported by the resolver. Compare it with the settings at your authoritative DNS host.
Common DNS lookup results and what they mean
A / AAAA: connect a hostname to IPv4 or IPv6 addresses. If you see an address, the DNS lookup worked; the website itself may still fail to load due to HTTPS or server configuration.
CNAME: links one hostname to another DNS name. Many root domains have no CNAME, so a missing result at example.com can be normal even when www.example.com has one.
MX: specifies where inbound mail is routed. For a complete email setup check, including SPF, DKIM and DMARC, open the Email DNS Checker.
NS (Nameserver): indicates DNS servers associated with the queried zone. Results from one recursive resolver do not prove the correct delegation at every registry or parent zone.
TXT: can store verification data and mail policies. TXT records also exist at specific subdomain names such as _dmarc.example.com; checking example.com does not automatically reveal all subdomain records.
TTL (Time to Live): is the caching lifetime in seconds. Recursive resolvers can return remaining TTL values. A changed record may appear at different times for different users.
Troubleshooting a missing DNS record
First confirm that you entered the exact hostname. Compare the record type, name and value with your domain’s DNS hosting panel. If the record was changed recently, allow cached answers to expire; the TTL is a useful clue. “Not found” means this resolver returned no record of that type at the queried name, while “Unavailable” means the lookup could not be completed.
Need registration details or the expiration date? Try our Website & Domain Checker. For mail authentication, use the MX, SPF, DKIM & DMARC checker.
Frequently asked questions
How do I check the DNS records of a domain?
Enter the domain name without https:// or a path and select Check DNS records. You will see separate responses for A, AAAA, CNAME, MX, NS and TXT records, including the TTL returned by the resolver.
Why does my domain show no CNAME record?
Many root domains use A and AAAA records rather than CNAME. A missing CNAME at the exact name entered is not necessarily an error. Try the specific hostname, such as www.example.com, if that is where the alias should exist.
Why are my new DNS changes not showing yet?
Recursive DNS resolvers can cache older answers until their TTLs expire. Our checker reads Google Public DNS only. If a change is missing, confirm the authoritative records in your DNS hosting dashboard and check again later.
Does this tool check DNS propagation worldwide?
No. One resolver cannot represent every ISP or geographic location. A worldwide propagation checker must compare results from multiple independent resolver networks.
Does an A record mean the website is online?
No. An address record only indicates a potential server location. It does not test HTTP, HTTPS, the TLS certificate, or whether a web page responds.
What does TTL mean in DNS?
Time to Live is a caching lifetime measured in seconds. The value shown here is returned by a recursive DNS resolver and may be the remaining cached TTL rather than the original TTL set at the authoritative DNS host.
Technical references: DNS records (RFC 1035) and Google Public DNS-over-HTTPS documentation.
Explore related tools
DNS Propagation Checker is planned separately. Checking a single resolver cannot confirm whether a recent DNS change has propagated across different networks.