How to Check DNS Records Online (And What Each One Means)

Why DNS Records Matter

Every time someone visits your website, sends you an email, or checks if your domain is legitimate, DNS records are what make it work. They are the phone book of the internet - a set of instructions that tell browsers, mail servers, and other systems where to find you and how to communicate with you.

Most of the time DNS just works. You notice it when it breaks: email stops arriving, a new domain takes days to resolve, or a security scanner flags a missing record that is exposing your domain to spoofing. Knowing how to check your DNS records is a basic skill for anyone running a website or managing a domain.

When You Need to Check DNS Records

• After a migration - Moving to a new host or mail provider means updating DNS records. You need to verify the new records propagated correctly and the old ones were removed.
• Email deliverability problems - Missing or misconfigured SPF, DKIM, or DMARC records are the most common cause of email going to spam. A DNS check reveals the problem in seconds.
• New domain setup - A fresh domain has no records by default. You need to add A records for your website, MX records for email, and TXT records for verification and security.
• Security audit - An attacker who can spoof your domain can impersonate your company in email. Checking your DNS reveals whether your defenses are in place.
• Propagation verification - DNS changes can take up to 48 hours to spread worldwide. Checking from multiple resolvers tells you if a change has propagated.

What Each DNS Record Type Does

A Record

Maps your domain to an IPv4 address. When someone visits example.com, the A record tells their browser which server to connect to. If your A record points to the wrong IP, your site goes down. This is the most basic DNS record.

AAAA Record

Same as an A record but for IPv6 addresses. Most modern hosting setups support both IPv4 and IPv6. If your host provides an IPv6 address, add an AAAA record alongside your A record.

MX Record

Mail Exchange record - tells other mail servers where to deliver email for your domain. If you use Google Workspace, your MX records point to Google's mail servers. Missing or wrong MX records mean email sent to you bounces or disappears.

TXT Record

A catch-all record type for text-based information. Used for SPF records (email authentication), domain ownership verification (Google Search Console, Stripe, etc.), and DKIM public keys. If something requires you to "add a TXT record to verify ownership," this is where it goes.

CNAME Record

Canonical Name record - an alias that points one domain name to another. Commonly used for subdomains: www.example.com pointing to example.com, or shop.example.com pointing to a Shopify or other ecommerce domain.

NS Record

Name Server record - identifies which DNS servers are authoritative for your domain. When you register a domain and point it to Cloudflare, AWS Route 53, or another DNS provider, you change the NS records. If these are wrong, nothing else about your DNS will work.

CAA Record

Certification Authority Authorization - specifies which certificate authorities (CAs) are allowed to issue SSL certificates for your domain. Without a CAA record, any CA can issue a cert. Adding one is a security measure that prevents unauthorized certificate issuance.

DMARC Record

Domain-based Message Authentication, Reporting and Conformance - a policy record stored as a TXT record at _dmarc.yourdomain.com. It tells receiving mail servers what to do if an email fails SPF or DKIM checks. A missing DMARC record means your domain can be spoofed without any enforcement action.

How to Check DNS Records

The fastest way is to use a real-time DNS lookup tool. The Queldrex DNS Health Checker queries both Cloudflare (1.1.1.1) and Google (8.8.8.8) resolvers simultaneously - which lets you spot propagation differences between providers. It checks A, MX, NS, TXT, CAA, DMARC, SPF, and DKIM records in one pass and flags anything missing or misconfigured.

If you prefer the command line, dig works on Mac and Linux: dig MX yourdomain.com returns your MX records. nslookup is the Windows equivalent. These tools query a single resolver and show raw output - useful for debugging but less convenient than a visual tool that checks multiple record types at once.

Reading Propagation Status

DNS changes do not take effect instantly. Your registrar pushes the change, but the TTL (Time To Live) on your existing records determines how long other DNS servers cache the old value. A TTL of 3600 means cached servers hold the old record for up to an hour. During a migration, temporarily lowering your TTL to 300 seconds before making changes reduces propagation time significantly.

If you check your records from two different tools and get different results, you are seeing a propagation difference - some resolvers have the new record, others are still serving the old cached value. This is normal and usually resolves within a few hours.