AJ Qureshi 8 min read Updated 28 Oct 2026
The DNS Records Checker shows the live DNS records of any domain: A, AAAA, CNAME, MX, NS, TXT, CAA and SOA, plus what the www version points to. It is the fastest way to confirm a hosting change, fix email that does not arrive, or see why a site is not loading.
What DNS is, in one minute
DNS, the Domain Name System, is the internet’s address book. People remember names like example.com. Computers connect using numbers called IP addresses. DNS turns the name into the right number, and also tells the world where to deliver email for the domain, which services are allowed to send email for it, and much more.
These instructions live in DNS records. When you change hosting, add email or verify your site with Google, you are editing DNS records. If one of them is wrong, your site or email stops working, even though nothing is wrong with the website itself.
How to use the checker
-
Type the domain, for example example.com, or a subdomain like shop.example.com.
-
Press Check DNS. The tool asks Google Public DNS for every common record type.
-
Read each section. Each record type has its own block with the values and their TTL (time to live).
-
Check the www line at the bottom to make sure www.yourdomain.com also points somewhere.
Every record type explained
| Record | What it does | Typical value |
|---|---|---|
| A | Points the domain to an IPv4 server address | An address like 192.0.2.10 |
| AAAA | Points the domain to an IPv6 address | A long address with colons |
| CNAME | Makes a name an alias of another name | www pointing to example.com or to a service |
| MX | Tells the world which servers receive email | A priority number and a mail server name |
| NS | Lists the name servers in charge of the domain | ns1 and ns2 of your host or DNS provider |
| TXT | Holds text such as SPF, DKIM, DMARC or verification codes | v=spf1 include:… or a long verification string |
| CAA | Says which certificate authorities may issue SSL for the domain | 0 issue “letsencrypt.org” |
| SOA | Technical details about the zone and its primary server | Primary name server, admin email and serial number |
Common problems and how DNS shows them
The website does not load after moving hosting
Look at the A record. If it still shows the old host’s IP address, the change has not been made or has not spread yet. If your name servers point to the new host, make sure the A record there is correct. Compare it with the IP shown in your hosting dashboard.
The site works without www but not with www
The www section at the bottom of the results will be empty. Add a CNAME record for www pointing to your main domain, or an A record with the same IP.
Email does not arrive
Check the MX records. If there are none, email has nowhere to go. If they point to the wrong provider, for example the old host after you moved email to another service, update them to the values your email provider gives you.
Email lands in spam
Look at the TXT records for an SPF entry starting with v=spf1, and for DMARC on the _dmarc subdomain. Missing or broken SPF and DMARC make providers like Gmail distrust your messages. Your email provider shows the exact values to add.
SSL certificate will not issue
If a CAA record exists and does not include the certificate authority your host uses, the certificate is blocked. Either add the right authority or remove the CAA record.
Changes in the dashboard do nothing
Check the NS records. If the name servers point to a different company than the one where you are editing records, your edits are ignored. Records only work at the provider listed in NS.
Why DNS changes take time: TTL and propagation
Every record has a TTL, shown in seconds in the results. It tells other DNS servers how long they may keep a copy before asking again. A TTL of 3600 means one hour.
When you change a record, servers around the world that cached the old value keep using it until their copy expires. That delay is what people call propagation. Most changes show up within minutes to a few hours. Name server changes can take longer because the parent registry also has to update.
Tips to make changes go smoothly:
- A day before a planned move, lower the TTL of the records you will change, for example to 300 seconds.
- Make the change, then check here. This tool asks Google Public DNS, which reflects changes quickly.
- If the change shows here but not on your phone, your phone or internet provider may still have the old copy. Switch between Wi-Fi and mobile data, or wait for the TTL to pass.
- After everything works, raise the TTL again to a normal value like 3600.
Email records explained: SPF, DKIM and DMARC
If you send email from your own domain, three TXT records decide whether your messages land in the inbox or in spam. You can see them all with this checker.
SPF
SPF lists the servers allowed to send email for your domain. It is a TXT record on the root domain that starts with v=spf1. A typical record includes your email provider and ends with ~all or -all. Every service that sends email for you, such as a newsletter tool or your website’s contact form, should be included in that one record.
DKIM
DKIM adds a digital signature to every message. Your email provider gives you a TXT or CNAME record to add on a special name like selector._domainkey. To check it here, type the full DKIM name your provider shows you.
DMARC
DMARC tells receiving servers what to do when SPF or DKIM fails, and where to send reports. It is a TXT record on _dmarc.yourdomain.com that starts with v=DMARC1. Type that full name in the checker to see it. Start with a relaxed policy like p=none and tighten it once everything passes.
Quick test
After adding these records, send an email to a Gmail address, open it, and choose “Show original”. Gmail shows whether SPF, DKIM and DMARC passed.
Reading the SOA and NS records
The SOA record holds the primary name server and a serial number that changes when the zone is edited. You rarely need to touch it, but a changing serial is a quick sign that someone has edited the DNS. The NS records list every name server for the domain. They should match the name servers set at your registrar. If they do not match, records may behave strangely during a move.
Checking subdomains
Subdomains like blog.example.com or shop.example.com have their own records. Type the full subdomain to see them. A subdomain often uses a CNAME to point at a service, such as a store platform or a landing page builder. If the CNAME is missing or misspelled, the subdomain shows an error.
DNS checklist for a new website
-
NS points to the provider where you manage records (your host or registrar).
-
A for the root domain points to your hosting IP.
-
www has a CNAME to the root domain or an A record with the same IP.
-
MX points to your email provider, if you use email on the domain.
-
TXT has one SPF record that includes every service that sends email for you.
-
SSL is active. Confirm with the SSL Certificate Checker.
If you are setting up hosting for the first time, my Hostinger guide walks through connecting a domain, and the Dynadot guide shows where to add records at the registrar.
Setting up a new site?
Hostinger connects your domain, DNS, email and free SSL from one dashboard.
Frequently asked questions
Which DNS server does this tool use?
It asks Google Public DNS, with Cloudflare as a fallback. These resolvers update quickly, so they are a good way to see the current state of your records.
How long does DNS propagation take?
Most record changes appear within minutes to a few hours, depending on the TTL. Name server changes can take up to a day or two in rare cases.
Why do I see different results on my phone?
Your phone or internet provider may have cached the old record. It updates when the TTL expires. Switching networks often shows the new value sooner.
Can I have two SPF records?
No. A domain should have only one SPF TXT record. Combine all senders into one record with several include entries.
What does an empty MX section mean?
The domain has no mail servers, so email sent to it will fail. Add the MX records your email provider gives you.
Is the DNS checker free?
Yes, it is free for normal use with no signup.
What is a good TTL value?
For records that rarely change, 3600 seconds (one hour) or more is normal. Lower it to around 300 seconds a day before a planned change, then raise it again afterwards.
Can I check DKIM and DMARC records here?
Yes. Type the full record name, such as _dmarc.example.com or the DKIM name your email provider gives you, and look at the TXT section.