Check common DNS records for any domain, inspect mail and verification records, and run reverse PTR lookups for IP addresses. This tool is useful for sysadmins, developers, and anyone troubleshooting DNS, email delivery, SSL validation, or hostname configuration.
Use it to quickly review A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, CAA, and SRV records from different resolvers without leaving the browser.
A, MX, TXT, NS and more, from the public resolver you pick.
Server lookup, rate limitedTry: google.com, cloudflare.com, 8.8.8.8
How to use
- Enter a domain name such as
example.com,zaur.it, or an IP address for reverse lookup. - Choose a resolver if you want to compare how public DNS providers answer for the same name.
- Select a record type, or keep
ALLto load the most common records in one view. - Click Lookup DNS. After results are loaded, you can switch record types to filter the existing response instantly.
- Use the copy icon on result rows to copy an exact value such as an IP address, MX target, TXT string, or nameserver hostname.
Understanding the results
Each row shows the record type, the returned value, and the TTL. TTL stands for time to live and tells recursive resolvers how long they may cache that answer before asking again.
- A → IPv4 address for a hostname
- AAAA → IPv6 address for a hostname
- MX → mail server responsible for receiving email for the domain
- TXT → text-based policy or verification record, often used for SPF, domain verification, or custom metadata
- NS → authoritative nameservers for the zone
- CNAME → alias pointing one hostname to another hostname
- SOA → zone authority information such as primary nameserver and serial
- PTR → reverse DNS mapping from IP address to hostname
- CAA → certificate authority restriction policy for SSL/TLS issuance
- SRV → service location record used by some protocols and applications
Practical examples
Example 1 - check a website IP address
Look up A or AAAA for a domain to see where the website resolves. This is useful when validating CDN changes, migrations, or DNS cutovers.
Query: zaur.it Record type: A
You should get one or more IPv4 addresses. If the domain is dual-stack, check AAAA as well to confirm IPv6 is configured correctly.
Example 2 - verify email routing
Use MX to see which mail hosts receive email for the domain. This helps when testing Microsoft 365, Google Workspace, IONOS, Zoho, or on-prem mail delivery.
Query: yourdomain.com Record type: MX
Check that the hostnames are correct and that the priority values make sense. Lower priority numbers are preferred first.
Example 3 - inspect SPF or domain verification records
TXT records often contain SPF policies, ownership verification tokens, or service-specific metadata.
Query: yourdomain.com Record type: TXT
This is useful when troubleshooting “domain not verified”, “SPF missing”, or “mail authentication failed” style issues.
Example 4 - confirm nameserver delegation
Use NS to verify which authoritative nameservers are assigned to the zone. This is especially helpful after registrar updates or delegation changes.
Query: yourdomain.com Record type: NS
If the nameservers are not what you expect, the domain may still be delegated elsewhere or not fully updated yet.
Example 5 - check reverse DNS for an IP address
Reverse lookups use PTR. This is important for mail server reputation, hostname consistency, and general network diagnostics.
Query: 8.8.8.8 Record type: PTR
A working PTR record maps the IP back to a hostname. If there is no PTR, many mail-related checks will fail or look suspicious.
Example 6 - check if SSL certificate issuance is restricted
Use CAA to see which certificate authorities are allowed to issue certificates for the domain.
Query: yourdomain.com Record type: CAA
This is useful when validating certificate automation and diagnosing unexpected issuance failures.
FAQ
Why do different resolvers sometimes return different answers?
Public resolvers can cache data for different lengths of time, refresh at different moments, or still hold older answers during propagation. If one resolver shows a new value and another still shows the old one, the zone may still be propagating or one resolver may still be serving a cached response.
What does TTL mean in DNS results?
TTL means time to live. It tells recursive resolvers how many seconds they may cache a record before asking again. A higher TTL usually means slower visible propagation after a record change, because old cached answers remain valid for longer.
Why do I see “No records found” for some types?
That usually means the domain simply does not publish that record type. For example, a normal website may have A and AAAA but no CAA or SRV. It does not always mean something is broken.
When should I use A and when should I use AAAA?
Use A to check IPv4. Use AAAA to check IPv6. If a service should be reachable over both protocol versions, both record types should be reviewed.
What is the difference between CNAME and A record?
An A record points directly to an IPv4 address. A CNAME points to another hostname instead. That alias hostname is then resolved again until an address record is found.
Why are MX records important?
MX records control where incoming mail for a domain is delivered. If they are missing or wrong, email may fail completely or go to the wrong provider.
What should I look for in TXT records?
TXT records often contain SPF policies, domain verification strings, DKIM selectors, or custom provider metadata. If you are validating email, ownership, or third-party service setup, TXT is often the first place to check.
What is PTR and why does reverse DNS matter?
PTR is reverse DNS. It maps an IP address back to a hostname. Reverse DNS is especially important for mail servers, because missing or mismatched PTR records can damage trust and deliverability.
Why would I check CAA records?
CAA records restrict which certificate authorities may issue certificates for a domain. They are useful for tightening certificate policy and troubleshooting ACME or certificate issuance issues.
Can I use this tool for DNS propagation checks?
You can compare answers from different resolvers, which is often enough for a quick propagation check. For deeper propagation testing across many locations, a dedicated DNS propagation checker is more appropriate.
Common use cases
- Validate website DNS after migration
- Confirm email routing and MX priorities
- Inspect SPF or verification TXT records
- Check if a hostname uses IPv6
- Review authoritative nameservers after registrar changes
- Test reverse DNS for mail or server reputation
- Inspect CAA before certificate issuance troubleshooting
Related guides and tools
Related guides
- nslookup in Windows: DNS troubleshooting from basic queries to AD diagnostics - resolving the same records from the Windows command line
- ipconfig command in Windows: beyond /all - reading the local adapter configuration behind these values
- DNS record types cheat sheet: every DNS record type and what it is for, on one printable page.