The DNS records lookup tool gives you an instant snapshot of any domain's DNS configuration — mail servers, IP addresses, nameservers, and authentication records. Whether you're troubleshooting email delivery, migrating to a new host, or connecting a CDN, you get the raw data you need in seconds.
How to use the tool
Type a domain name into the field above (for example, example.com) and click "Check". The tool queries authoritative nameservers and returns a full records table in real time. No sign-up required.
- Enter the domain without http:// and without a trailing slash
- For a subdomain, enter it in full: mail.example.com
- Run the lookup again after making changes to confirm propagation
What the results show
The tool displays all major record types along with the TTL (time-to-live in seconds) for each entry:
- A / AAAA — IPv4 and IPv6 addresses the domain resolves to
- MX — incoming mail servers with priority values; the first place to look when email isn't arriving
- NS — authoritative nameservers responsible for the domain zone
- TXT — text records including SPF, DKIM, DMARC, and site verification tokens for Google, Meta, etc.
- CNAME — an alias that points one name to another (commonly used for subdomains and CDN endpoints)
- TTL — how long resolvers cache the record; a lower value means faster propagation after changes
Frequently asked questions
Why am I not receiving emails on my domain?
Check the MX records — they must point to your mail provider's server. If MX records are missing or incorrect, incoming messages will be rejected or lost. Also look at the TXT records: a missing or broken SPF entry is a common reason legitimate emails land in spam.
What is TTL and why does it matter?
TTL (Time To Live) is the number of seconds DNS resolvers are allowed to cache a record. A value of 3600 means one hour. Before moving your site to a new server, lower the TTL to 300–600 well in advance — this minimises the window where some visitors still reach the old IP.
How long does DNS propagation take?
In theory, no longer than the current TTL. In practice, ISPs and upstream resolvers may cache records for up to 24–48 hours. If you just updated a record, the tool may still show the old value until the cache expires across the network.
What is the difference between a CNAME and an A record?
An A record maps a domain name directly to an IP address. A CNAME is an alias that points to another domain name rather than an IP. CNAMEs cannot be used on the apex (root) domain — only on subdomains. Third-party services like CDNs, Webflow, and Shopify typically require a CNAME rather than an A record.
Want a deeper dive into DNS record types and configuration best practices? Read our complete DNS records guide.