How to look up DNS records for any domain
Use the free DNS lookup tool — enter any domain name and select the record type you want to check. Results show the current live DNS values as seen from public DNS servers. No account required.
DNS record types explained
A record (Address)
Maps a domain to an IPv4 address. This is the most fundamental record — it says "example.com points to IP address 93.184.216.34."
Check this when: a domain is not loading, you recently changed hosting, or you want to verify where a domain resolves.
AAAA record
Like an A record but for IPv6 addresses. Modern sites serve both A and AAAA records for full IPv4 and IPv6 compatibility.
CNAME record (Canonical Name)
Points a subdomain to another domain name (not an IP address). Example:www.example.com CNAME → example.com. Used extensively by CDNs (Cloudflare, Fastly), hosting platforms, and services like Shopify and Squarespace to route your subdomain through their infrastructure.
Check this when: a subdomain is not working after adding a service, or you need to verify a CDN configuration.
MX record (Mail Exchange)
Specifies which mail servers handle email for the domain. MX records have a priority number — lower number = higher priority. Example:
10 mail1.example.com
20 mail2.example.com (backup)Check this when: email is not delivering, you have migrated email providers, or you need to verify your email hosting setup (Google Workspace, Microsoft 365, etc.).
TXT record
Text records that store arbitrary string data. Used for many purposes:
- SPF: lists authorized mail servers to prevent email spoofing
- DKIM: stores a public key for cryptographic email signing
- DMARC: email authentication policy
- Domain verification: Google Search Console, Microsoft 365, Stripe, and many services ask you to add a TXT record to prove domain ownership
Check this when: verifying email authentication, troubleshooting email deliverability, or confirming a domain verification record was added correctly.
NS record (Name Server)
Specifies which DNS servers are authoritative for the domain — i.e., which servers hold the actual DNS records. Changing your hosting or DNS provider involves updating NS records.
Check this when: diagnosing why DNS changes are not propagating, or verifying which DNS provider controls a domain.
DNS propagation
When you change a DNS record, the change does not take effect everywhere immediately. DNS records have a TTL (Time To Live) — the number of seconds other DNS servers cache the record before checking again. A TTL of 3600 means the old record may be cached for up to one hour after you change it.
Global propagation — the change being visible from most DNS resolvers worldwide — takes 1–48 hours depending on TTL settings and resolver refresh schedules.
The DNS lookup tool shows the current value from the authoritative name server, which updates immediately after a change — even before propagation completes everywhere.
Common DNS debugging scenarios
| Problem | Record to check |
|---|---|
| Website not loading | A record — does it point to the right IP? |
| Email not receiving | MX record — is it set correctly? |
| Email going to spam | TXT record — are SPF, DKIM, DMARC set? |
| Subdomain not working | CNAME record — does it point to the right target? |
| Domain verification failing | TXT record — was the verification string added? |
Summary
Check any DNS record with the free DNS lookup tool — no account. A records control where domains point. MX records control email routing. TXT records handle verification and email authentication. CNAME records alias subdomains. Allow 1–48 hours after a change for full global propagation.