Find DNS records
Введите URL
Find DNS Records
DNS is the internet’s directory.
It connects a domain name to the servers that handle the website, email, and related services.
This free DNS lookup tool shows the public records configured for a domain so you can verify setup, troubleshoot issues, or inspect basic infrastructure.
Look Up a Domain
- Enter the domain only (example:
example.com) - Choose record types if the tool allows selection
- Run the lookup
- Review the returned records by type
You can also check subdomains such as www.example.com or mail.example.com.
Record Types Explained
| Record | What it does |
|---|---|
| A | Maps the domain to an IPv4 address |
| AAAA | Maps the domain to an IPv6 address |
| MX | Tells mail systems where to deliver email |
| CNAME | Creates an alias to another hostname |
| TXT | Stores text data (SPF, verification, policies) |
| NS | Lists the authoritative name servers |
| SOA | Zone authority and timing details |
Different problems require different records. Email issues start with MX/TXT. Website pointing issues usually start with A/AAAA/CNAME.
What Each Lookup Is Good For
Website not loading correctly
Check A/AAAA records. Confirm the domain points to the expected server IP.
Email delivery problems
Check MX records first, then TXT records for SPF (and related authentication entries).
After a migration
Verify DNS no longer points to the old host and that new records have updated.
CDN or service setup
CNAME records often show connections to Cloudflare, email providers, or third-party platforms.
Ownership / DNS control checks
NS records show which systems currently control the domain’s DNS zone.
How to Read Common Results
- Multiple A records can mean load balancing or multi-server setups
- MX priority numbers matter — lower values are tried first
- CNAME on www is common; the final destination still depends on the target host
- TXT with
v=spf1usually indicates SPF email policy configuration - Missing MX generally means the domain is not set up to receive mail
- NXDOMAIN means the name does not exist in DNS
DNS changes are not always instant. Propagation and caching can delay what different networks see.
Troubleshooting Flow
- Confirm the domain spelling
- Check NS records (who controls DNS?)
- Check A/AAAA or CNAME (where does the site point?)
- Check MX/TXT (is email configured?)
- Re-check later if you just changed records
- Pair with hosting/IP tools if you need infrastructure context
If records look correct but the site still fails, the issue may be server-side rather than DNS.
FAQ
Is this DNS lookup free?
Yes. Standard queries do not require an account.
Should I enter a full URL or just the domain?
Use the domain/host name. Prefer example.com over a long page URL.
Why don’t I see an AAAA record?
Many domains still use IPv4 only. Missing AAAA is common and not automatically an error.
Can DNS explain slow website speed?
Sometimes indirectly (for example, distant hosting or misconfiguration), but speed also depends on server performance, page weight, and CDN setup.
Do results update immediately after I change DNS?
Not always. TTL values and resolver caches can cause delays.
Related tools
Note: DNS responses can vary by resolver and caching. For critical changes, verify from more than one source and allow time for propagation.