Find DNS Record

DNS Records Explained in Simple Terms

DNS records are instructions that tell the internet where to find a domain and how to handle traffic for it. They link a human-friendly domain name (like example.com) to technical details such as IP addresses, email servers, and security settings. Instead of typing a long number like 192.0.2.1, you type a domain name, and DNS looks up the right records and connects you to the correct server. That's why DNS is often called the "phonebook of the internet."

DNS records are stored in a domain's zone file (a text-based list of settings) and hosted on authoritative name servers. When someone visits your website or sends you an email, a DNS query is made: DNS servers read the zone file, follow the records, and return the answer needed to load the site or deliver the message. Each record also has a TTL (Time To Live) — how long other servers may cache it before checking again. A lower TTL makes updates appear faster; a higher TTL reduces lookups.

How do I look up a domain's DNS records?

1. Enter the domain name in the box above (example: example.com).
2. Choose the record type you want — A, AAAA, CNAME, MX, TXT, NS, SOA, and more — or select ALL to pull every available record at once.
3. Click to run the lookup and read the clean, sorted results in seconds.

This is ideal for troubleshooting, verifying a change you just made, or auditing a domain's full setup.

Common DNS record types you should know

A Record (IPv4 Address)

An A record connects a domain or subdomain to an IPv4 address (example: 93.184.216.34) — used to point example.com or www.example.com to your web server.

AAAA Record (IPv6 Address)

An AAAA record does the same job as an A record but for IPv6 addresses, which are growing because IPv4 addresses are limited.

CNAME Record (Alias)

A CNAME makes one hostname act like an alias of another — for example, pointing blog.example.com to example.com so you only update the main target once.

DNAME Record (Subdomain Alias)

A DNAME redirects many subdomains at once to another domain, useful when moving a group like app., shop., and help. to a new domain.

MX Record (Email Routing)

An MX record tells the internet where to deliver email for your domain. Without correct MX records, mail to [email protected] may fail.

NS Record (Authoritative Name Servers)

NS records show which name servers control your domain's DNS — they hold the "final" answers, so they're essential for your site and email to work.

SOA Record (Zone Information)

The SOA record holds core admin details for the DNS zone, including the owner, refresh timing, and serial number that keep DNS servers in sync.

TXT Record (Verification + Security)

A TXT record stores text data used for domain-ownership verification (Google, Microsoft, etc.) and for email-security records like SPF, DKIM, and DMARC.

SPF Record (Email Sender Rules)

SPF tells receiving mail servers which systems may send mail for your domain, reducing spoofing and spam. It's usually published as a TXT record.

PTR Record (Reverse DNS)

A PTR record maps an IP address back to a hostname (reverse lookup). It's used for email trust and anti-spam checks and is typically managed by your host or ISP.

SRV Record (Service Location)

An SRV record points services to the correct server and port — often used for chat, VoIP, or Microsoft services.

CAA Record (SSL Certificate Control)

A CAA record lets you choose which Certificate Authorities may issue SSL/TLS certificates for your domain, preventing unwanted issuance.

CERT Record (Stored Certificates)

A CERT record can store certificates in DNS. It's less common today but supports certain security setups.

ALIAS Record (Root Domain to Hostname)

An ALIAS record works like a CNAME but is used at the root domain (apex), where supported, letting example.com point to a hostname instead of an IP.

NSEC Record

An NSEC record is part of DNSSEC and helps prove that a record does not exist, reducing fake responses in DNSSEC-enabled zones.

URL Redirect / Forwarding

Some providers offer URL forwarding (301, 302, or masking). It isn't a classic DNS record but a provider feature that redirects one URL to another.

Why does checking DNS records matter?

Knowing how to read DNS records helps you troubleshoot a site that won't load, fix email that isn't being delivered, confirm a domain-verification TXT record was added correctly, and tighten security with SPF, DMARC, and CAA. After a migration or DNS change, a quick lookup confirms whether your new records have propagated.

Frequently asked questions

How long do DNS changes take to apply?

It depends on the record's TTL and propagation, ranging from a few minutes to 24–48 hours. A lower TTL set before the change makes it appear faster.

Why can't I see a record I just added?

Caching and propagation delays are the usual cause. Wait for the TTL to expire, or query a different DNS server to check.

What's the difference between an A record and a CNAME?

An A record points to an IP address directly; a CNAME points to another hostname, which then resolves to an IP.

Which records control my email?

MX records route mail, while TXT-based SPF, DKIM, and DMARC records control authentication and anti-spoofing.

Related tools

• Domain to IP — resolve a domain's A/AAAA records to its IP.
• Domain Hosting Checker — find the host behind a domain.
• Blacklist Checker — check a mail server IP against blacklists.
• Website SEO Score Checker — audit the wider health of a site.