Processed on our server. Your input is sent to our server to produce the result. Uploaded files are not kept, and nothing is sold or shared; our privacy policy lists what is logged.
Check DNS Records for Any Domain
The Tools Kit’s free DNS Lookup checks the DNS records of any domain or subdomain: A and AAAA for its IP addresses, MX for its mail servers, TXT for SPF and verification strings, NS for its nameservers, plus CNAME and SOA. Pick a record type, run the query and you get every matching record with its value and TTL, ready to copy.
The lookup runs on our server and asks Google Public DNS (8.8.8.8), not the resolver your computer or ISP uses. That makes it a quick DNS checker for the question that matters after an edit at your DNS provider: what does the rest of the internet see right now? To find out who registered a domain and when it expires, use the WHOIS lookup instead; DNS tells you where a domain points, WHOIS tells you who owns it.
How to Use the DNS Lookup Tool
- 1
Enter the domain name
Type a bare hostname such as example.com or mail.example.com into the Domain Name box. Leave out https:// and any path; the tool looks up exactly the name you type.
- 2
Pick a record type
Choose A, AAAA, MX, TXT, NS, CNAME or SOA from the Record Type list. A (the IPv4 address) is selected by default.
- 3
Run the lookup
Press Enter or click Lookup. The query is sent to Google Public DNS (8.8.8.8) and every matching record is listed with its value, its TTL in seconds and, for MX records, its priority.
- 4
Copy or clear the results
Click Copy records to copy the values one per line, or Clear to reset the form and check another domain or record type.
Each lookup returns one record type. To audit a whole domain, run NS, then A, then MX and TXT in turn.
DNS Record Types Explained
DNS works like a directory for a domain: each record type answers a different question. Here is what each type in the dropdown does and what the tool shows for it.
| Type | What it stores | Example value | What the tool shows | Check it when |
|---|---|---|---|---|
| A | IPv4 address of the name | 192.0.2.10 | The address | Website or server not loading, checking a hosting move |
| AAAA | IPv6 address of the name | 2001:db8::10 | The address | IPv6 reachability, dual-stack setups |
| MX | Mail servers for the domain, with a priority | smtp.google.com, priority 10 | Mail server and priority | Email not arriving, switching mail providers |
| TXT | Free-form text strings | v=spf1 -all | Each text string | SPF, domain verification codes |
| NS | Authoritative nameservers for the zone | ns1.google.com | Each nameserver | Confirming a nameserver change at the registrar |
| CNAME | Makes one name an alias of another | www.example.com to example.com | Whether the alias exists, and its TTL | Checking an alias is in place |
| SOA | Start of authority: zone serial and timers | Primary server, admin, serial | Whether the record exists, and its TTL | Confirming the zone is served |
An A record lookup on an aliased name such as www.example.com returns the CNAME in the chain as a row marked N/A, followed by the final IP addresses. Once you have an address, the reverse DNS lookup runs the opposite query and finds the hostname that IPv4 address points back to, and the blacklist checker tells you whether that IP or domain is listed on common spam blocklists.
MX and TXT Lookups for Email Problems
When mail is not arriving, start with an MX record lookup. Each mail server comes back with a priority number, and sending servers try the lowest number first, falling back to higher ones. If the MX records still point at your old provider after a switch, mail keeps going there until the old TTL runs out.
Email authentication lives in TXT records. SPF is a TXT record on the domain itself beginning with v=spf1; DMARC sits at _dmarc.yourdomain.com and begins with v=DMARC1; DKIM sits at selector._domainkey.yourdomain.com. You can type any of those names into the box with TXT selected. The DMARC / SPF checker goes further and explains what the policies mean, while the email validator checks a single address’s format and whether its domain has MX records at all.
One limit to know: the query travels over UDP, and when a domain publishes so many TXT strings that the answer does not fit in one response (large providers often do), the tool returns “No records found” rather than a partial list.
TTL and DNS Propagation
Every answer carries a TTL, the number of seconds a resolver may reuse it before asking the authoritative nameserver again. “DNS propagation” is simply old cached answers expiring. If an A record had a TTL of 3,600 when you changed it, a resolver that cached it a moment before the change can serve the old address for up to an hour.
Because this tool asks a resolver, the TTL you see is usually the time left on Google’s cached copy, not necessarily the value set at your DNS provider. Our server may also reuse a recent answer for up to about 30 minutes, so the TTL can look frozen between repeat lookups. When the new value appears here, a major public resolver has picked it up, a good sign that most of the internet will follow as other caches expire. Lowering a record’s TTL a day before a planned move shortens the switchover. After the DNS points at a new server, confirm the site works over HTTPS with the SSL certificate checker.
Common uses
- Confirming an A record change has gone live after moving a website to a new host
- Checking MX records point to Google Workspace, Microsoft 365 or another mail provider
- Finding a domain verification TXT code or an SPF record
- Verifying the nameservers after transferring a domain or changing DNS providers
- Seeing whether a domain has an IPv6 (AAAA) address
- Diagnosing why a domain or subdomain does not resolve
For more network and domain utilities, such as working out the address range of a block with the CIDR subnet calculator, browse all security tools.
DNS terms explained
| Term | What it means here |
|---|---|
| Resolver | A server that answers DNS questions for clients by following the chain of nameservers; this tool asks Google Public DNS at 8.8.8.8 |
| Authoritative nameserver | The server that holds the real records for a zone, named by its NS records; resolvers copy answers from it |
| TTL (time to live) | How many seconds a resolver may keep a cached answer before asking again; a lower TTL means changes are picked up sooner |
| Propagation | The period after a change while old cached answers expire across resolvers worldwide; it is governed by the old TTL |
| Zone | The set of records for a domain managed together at one DNS provider, described by its SOA record |
| Apex (root) domain | The bare domain such as example.com, as opposed to a subdomain such as www.example.com |
Frequently Asked Questions
Enter the domain name, choose a record type such as A, MX or TXT, and click Lookup. The tool queries Google Public DNS and lists every record of that type with its value and TTL. Run it once per record type you want to see.
Queries are sent from our server to Google Public DNS at 8.8.8.8 with recursion enabled, not to your own ISP or router. That shows what the public internet sees, which is usually the question after you change a record. Answers can be cached on our side for up to about 30 minutes, so a record you changed only minutes ago may not show its new value here straight away.
Seven: A, AAAA, MX, TXT, NS, CNAME and SOA. For A, AAAA, MX, TXT and NS the record values are shown. For CNAME and SOA the tool currently confirms that the record exists and shows its TTL, but does not display the alias target or the SOA fields.
Select MX in the Record Type list and run the lookup. Each mail server is listed with its priority; the lowest number is tried first and higher numbers are backups. For example, google.com returns smtp.google.com with priority 10.
TTL (time to live) is the number of seconds a resolver may cache the answer. Because the result comes from a resolver, the TTL shown is the time left on its cached copy, so it can be lower than the value set in your DNS provider. A repeat lookup may be served from our short-term cache, so the TTL will not always change between runs.
It depends on the TTL that was on the old record. A resolver that cached the old answer keeps it until that TTL runs out, so a 300-second TTL clears in about five minutes and an 86,400-second TTL can take a day. Nameserver changes at the registrar often take longer because parent zone records carry long TTLs.
The name may simply have no record of that type (many domains have no AAAA or CNAME at the root), it may be misspelled, or it may include https:// or a path, which must be removed. Very large TXT record sets that do not fit in a single UDP response can also come back empty here; the DMARC / SPF checker is a better fit for those domains.
When a name such as www.example.com is an alias, the answer contains the CNAME record followed by the final addresses. The CNAME appears as a row showing N/A and a TTL, and the IP addresses follow it. Copy records copies only the rows that have a value.
Yes, they are all TXT records. Look up TXT on the domain for SPF (it starts with v=spf1), on _dmarc.yourdomain.com for DMARC, and on selector._domainkey.yourdomain.com for DKIM. The DMARC / SPF checker fetches and interprets them for you instead of only listing them.
No. This tool looks up names, not addresses. To find the hostname behind an IPv4 address, use the Reverse DNS Lookup tool, which runs the PTR query for you.
Yes. There is no sign-up and no fee. Only the domain name and record type you enter are sent to our server to run the query.
Reviewed by Raja Jahangir · Last reviewed: October 7, 2026
What do DNS record types mean?
An A record points a domain to an IPv4 address and AAAA to IPv6. CNAME aliases one name to another, MX directs email, TXT holds verification strings such as SPF and DKIM, and NS names the authoritative servers. Changes propagate over the record's TTL.
