DNS Lookup
Analyse DNS Records and Find Problems Instantly
Look up A, MX, TXT, NS, CNAME and AAAA records. SPF, DKIM and DMARC security analysis, a DNS Health Score and smart recommendations. Completely free.
Has Your DNS Change Spread Worldwide?
Query different DNS resolvers to check whether your change has propagated.
DNS Problems and Fixes
When a website won't load or email doesn't arrive, the cause is usually a single wrong or missing record. Pick your situation to see the likely causes and which record to check.
Website Won't Load
Possible causes
- Wrong A record — the IP points to the old server
- AAAA record error — the IPv6 connection fails
- DNS propagation isn't complete yet
- High TTL — the cache hasn't refreshed
Check that the A record points to the IP address your hosting provider gave you; www is a separate record (A or CNAME), so look it up too. If the record is right but the site still loads from the old server, it's a cache issue: wait for the TTL to expire or run ipconfig /flushdns on your computer. If an AAAA record points to an old server, delete it, or visitors on IPv6 won't reach the site.
Email Not Arriving
Possible causes
- MX record missing or wrong
- The MX server is unreachable
- SPF failure (unauthorised server)
- PTR record doesn't match
If there's no MX record, or it still points to your old mail provider, email goes to the wrong server. The MX value is a server name (not an IP address), and that name must have an A record. If you switched mail services, delete the old MX records; the server with the lower priority number is tried first.
MX LookupEmails Landing in Spam
Possible causes
- SPF record missing or too broad
- DKIM signature missing or invalid
- No DMARC policy defined
- Server IP is on a blacklist
Receiving servers use SPF, DKIM and DMARC to verify that email really comes from you; if one is missing, your mail lands in spam or gets rejected. Check all four together in email security mode, and make sure the SPF record includes every service that sends email for you (mail provider, newsletter tool, website).
Run the email analysisDNS Change Not Active Yet
Possible causes
- TTL too high (86400 s)
- Browser / local DNS cache
- ISP cache
- NS change pending
A DNS change doesn't reach everyone at once: resolvers keep the old answer cached for the record's TTL (usually 1 hour, at most 24 hours). A nameserver change is updated at the extension's registry and can take 24–48 hours. Use the propagation check below to see what different resolvers return, and lower the TTL to 300 seconds a day before a planned move.
Check propagationSPF Check Fails
Possible causes
- 550 SPF check failed — unauthorised sender
- Too many DNS lookups (limit of 10 exceeded)
- An old mail service is still listed
A domain must have exactly one SPF record: two separate v=spf1 records invalidate both. At most 10 DNS lookups are allowed, includes counted; remove services you no longer use. The SPF lookup tool shows the lookup count and every nested include.
Cloudflare DNS Problems
Possible causes
- Orange cloud (proxied) — some services don't work
- SSL/TLS mode mismatch
- CNAME flattening issue
- Proxy used with MX
Cloudflare's orange cloud (proxy) is for web traffic only. Keep the A records of your mail server and the MX target on the grey cloud (DNS only), or email and FTP stop working. If you get SSL errors, set Cloudflare's SSL/TLS mode to Full (strict) and make sure your server has a valid certificate.
What Is DNS and What Does a Lookup Show?
DNS turns your domain into the records that say where your website, email and verifications go. Those records live on the domain's nameservers (NS), so a record change is always made in the panel that manages those servers. Our guide to managing domain DNS shows step by step how to change records and nameservers at Atak Domain.
This tool asks Google Public DNS (or Cloudflare if there's no answer) for the records from your browser over DNS-over-HTTPS and interprets the answer: it shows missing or wrong records, the services in use and the next step. The answer may come from cache for the record's TTL.
- Domainatakdomain.com
- Nameserver (NS)Where the records are kept
- RecordsWebsite, email, verification
How to Read a DNS Record
example.com.Name: The name the record belongs to. In a panel the root domain is written as@, and subdomains by their prefix only (www,mail).3600TTL: Cache time in seconds. Resolvers keep the answer this long, so it's the value that really decides how fast a change spreads.INClass: Stands for Internet; today almost every record says IN.AType: What the record does: A and AAAA point the site to an IP, MX points email to a mail server, CNAME points one name to another; TXT carries verification and security text.192.0.2.10Value: Depending on the type, an IP address, a server name or text. In an MX record, a priority number comes before the value.
When typing a value in a panel, don't add your domain to the end of a server name: some panels append it themselves, producing broken records like mail.domain.com.domain.com. If you see such a value in the results, fix the record.
Which Record Controls What?
Which record to check first, depending on the problem you have.
| Record Type | Purpose | Target | When to Check? |
|---|---|---|---|
| A | IPv4 routing | IP address | Site won't load, hosting change |
| AAAA | IPv6 routing | IPv6 address | IPv6 connectivity issue |
| MX | Mail server | Mail server domain | Email not arriving, mail setup |
| TXT | Verification / Security | Text value | SPF/DKIM/DMARC issue |
| NS | Authoritative DNS server | Nameserver domain | Moving to Cloudflare, hosting change |
| CNAME | Alias routing | Another domain | www issue, subdomain setup |
| CAA | Restricting SSL issuance | CA name | SSL certificate error |
| PTR | Reverse DNS lookup | Domain name | Mail server spam issue |
Frequently Asked Questions
About DNS records, propagation time and lookup results.
-
A DNS lookup shows a domain's DNS records — A, MX, TXT, NS, CNAME and more — in real time. It's used to check the hosting connection, email routing and security settings.
-
A record change is live on the nameserver immediately, but resolvers keep the old answer cached for the record's TTL: with a TTL of 3600, at most 1 hour. A nameserver (NS) change is updated at the extension's registry and can take 24–48 hours. You can follow propagation with the check on this page.
-
Your computer, router and internet provider may keep the old answer for the TTL, while this tool shows Google Public DNS's current answer. Clear your computer's cache with
ipconfig /flushdnson Windows orsudo dscacheutil -flushcacheon macOS. If resolvers give different answers, the change is still spreading. -
The DNS server (resolver) your computer uses is usually your router's or your internet provider's. On Windows it is listed under DNS Servers in the output of
ipconfig /all; on macOS, in the nameserver lines ofscutil --dns. This tool shows Google Public DNS's answer, not your resolver's; to see your IP address, use IP Lookup. -
An A record maps a name straight to an IPv4 address (
example.com → 192.0.2.10). A CNAME record points a name to another name (www.example.com → example.com), and the IP address is then read from that name's A record. The root domain (@) can't be a CNAME, because a CNAME can't share its name with other records such as NS and MX. -
You change NS when moving to Cloudflare, switching to a different hosting provider or when you want to run your own DNS server.
-
Choose NS / Nameserver as the query type and enter the domain: the tool lists the domain's nameservers and, when it recognises the provider (such as Cloudflare, GoDaddy or Atak Domain), names it too. On the command line,
nslookup -type=ns example.comon Windows ordig NS example.com +shorton macOS and Linux gives the same list. -
The MX (Mail Exchanger) record determines which mail server receives the email sent to your domain. If you see
mail.protection.outlook.com, Microsoft 365 is in use;aspmx.l.google.commeans Google Workspace. -
Receiving servers check that an email really comes from you with three TXT records: SPF (which servers may send), DKIM (the message signature) and DMARC (what to do when the checks fail). If one is missing or wrong, the email can land in spam or be rejected. Run the Email Security mode to see all three at once.
-
DNSSEC is a security layer that prevents DNS spoofing (cache poisoning) by cryptographically signing DNS answers.
Need More Than DNS?
Domain, hosting, SSL and business email — on one platform, at competitive prices. .COM from $8.99.