DNS Record Lookup - Free DNS Checker Tool

Instantly query any DNS record type for any domain - A, AAAA, MX, CNAME, TXT, PTR, NS, SOA - using Google, Cloudflare, OpenDNS, or Quad9. Free, real-time, no signup required.
Record types
Real DNS lookup via Google DNS · Cloudflare · OpenDNS · Quad9 · no signup required

What This DNS Checker Shows You

Run a quick DNS lookup and get the information you need to troubleshoot your domain:

8 DNS record types
Check A, AAAA, MX, CNAME, TXT, PTR, NS, and SOA records.
Multiple DNS resolvers
Compare results from Google, Cloudflare, OpenDNS, and Quad9.
TTL visibility
See the TTL for each returned record to understand how long the response can remain cached.
Quick, no-signup checks
Enter a domain, select the records and resolver you want, and get results instantly.
Free and unlimited
Run DNS checks without creating an account or worrying about query limits.

How to Use the DNS Record Lookup Tool

1
Enter a domain name (e.g. example.com) in the input field - the tool strips https:// and trailing paths automatically
2
Select a DNS resolver - Google, Cloudflare, OpenDNS, or Quad9
3
Select which record types to display using the checkboxes - All selects all eight types at once
4
Click Check DNS - results appear grouped by record type with all relevant fields. Toggle checkboxes to filter the view without re-querying

DNS Record Types - What Each One Does

DNS records are entries in the Domain Name System that provide information used to locate services, route traffic, delegate DNS zones, and publish other domain-related data. Each record type has a specific purpose.

Record type What it returns What breaks if it’s wrong
A An IPv4 address associated with a domain name Websites or services using IPv4 may become unreachable
AAAA An IPv6 address associated with a domain name Services may be unreachable over IPv6
MX The mail servers designated to receive email for a domain Incoming email delivery can fail or be routed incorrectly
CNAME An alias pointing a domain name to another canonical name Subdomains, hosted services, or CDN configurations may stop resolving correctly
TXT Text data published in DNS, including SPF, DKIM, DMARC, and domain verification information Email authentication or domain verification can fail
PTR A hostname associated with an IP address through reverse DNS Reverse DNS checks can fail, potentially affecting mail server trust and deliverability
NS The authoritative nameservers for a DNS zone DNS delegation can fail or point queries to the wrong DNS servers
SOA Zone administration details such as the primary nameserver, serial number, and timing parameters DNS zone updates and troubleshooting can be affected
MX, TXT, and PTR records directly affect email deliverability

Check each one with our dedicated free tools.

Why DNS Results Differ Between Resolvers

Different DNS resolvers can sometimes return different results for the same domain. This usually happens because resolvers cache DNS responses for the duration specified by the record’s TTL.

Recent DNS changes
A resolver may continue showing the previous record until its cached response expires.
Different cache states
Google, Cloudflare, OpenDNS, and Quad9 may refresh and cache records at different times.
TTL impact
Records with longer TTLs can remain cached for longer, which can delay when a change appears through a particular resolver.
Resolver comparison
Checking multiple resolvers helps you identify whether a DNS change is being reflected consistently.

Why DNS Records Matter for Email & Security

DNS records do more than route web traffic - they are the backbone of email authentication and domain security. Misconfigured or missing DNS records are the most common cause of email deliverability failures and one of the primary attack vectors for domain spoofing.

Email authentication
SPF, DKIM, and DMARC all live in TXT records. Without them, receiving servers can't verify your emails are legitimate.
Mail routing
MX records tell the internet which servers accept email for your domain. A missing or wrong MX record means lost email.
Reverse DNS (PTR)
PTR records map your sending IP back to a hostname. Many spam filters reject email from IPs without a valid PTR record.
Propagation & TTL
DNS changes don't apply instantly - TTL controls how long records are cached. Lower TTL during migrations speeds up rollout.

Frequently Asked Questions

What is a DNS record lookup?
A DNS record lookup queries the Domain Name System to retrieve records associated with a domain or IP address. Records include routing instructions (A, AAAA, MX), aliases (CNAME), authentication data (TXT), reverse DNS (PTR), nameserver information (NS), and zone administration details (SOA). This tool performs live lookups in real time using your choice of DNS resolver.
How do I check DNS records for a domain?
Enter the domain name in the tool above, select the record types you want (or All), and click Check DNS - results appear instantly, grouped by type. Alternatively, you can use nslookup -type=MX example.com in a terminal, though this tool queries all record types at once and displays results in a structured format without needing command-line access.
What is the difference between an A record and an AAAA record?
An A record maps a domain name to an IPv4 address (e.g., 93.184.216.34). An AAAA record maps a domain to an IPv6 address (e.g., 2606:2800:220:1:248:1893:25c8:1946). Most domains publish both A records for IPv4 connectivity and AAAA records for IPv6. If only an A record exists, IPv6-only clients may not be able to reach the domain.
What DNS records affect email deliverability?
Three record types directly affect email: MX records define which servers receive your email; TXT records publish SPF, DKIM, and DMARC for authentication; PTR records map your sending IP to a hostname, which is checked as a trust signal by receiving mail servers. Missing or misconfigured records in any of these types can cause email to be rejected or land in spam.
What is the difference between a DNS lookup and nslookup?
nslookup is a command-line utility for performing DNS queries. A DNS lookup is the broader process of querying DNS to retrieve information about a domain or IP address. This browser-based tool lets you perform common DNS lookups without using the command line and presents supported record types in a structured format.
Why do results differ between DNS resolvers?
Different DNS resolvers can return different results because they may have different cached responses. When a resolver has a cached DNS record, it can return that response until its TTL expires. If you have recently changed a record, one resolver may already show the new value while another still returns the previous cached value.
Is this DNS checker free?
Yes. The DNS checker is free to use and does not require an account or sign-up. You can look up supported DNS records for a domain and select from Google, Cloudflare, OpenDNS, or Quad9.
What's the difference between a DNS lookup and a DNS checker?
A DNS lookup is the process of querying DNS to retrieve information about a domain or IP address. A DNS checker is a tool that makes those queries easier to perform and interpret. In practice, the terms are often used interchangeably. This tool lets you perform DNS lookups for eight supported record types and compare responses from selected resolvers.
How long does it take for DNS changes to propagate?
There is no single propagation time for every DNS change. Resolvers cache DNS responses according to their TTL, so a resolver may continue returning an older value until its cached response expires. Other factors, including DNS delegation and local caching, can also affect what you see. Checking multiple resolvers can help you identify whether a change is being reflected.
Which DNS resolver should I check against?
There is no single resolver that is always the right choice. Checking more than one can help you identify differences caused by caching or resolver-specific behavior. Google, Cloudflare, OpenDNS, and Quad9 are public DNS resolvers that can be used for comparison. To compare them, run the same lookup once per resolver and watch for differences in the values and TTLs you get back.