DNS Lookup Tool

Query A, AAAA, CNAME, MX, TXT, NS, SOA, and SPF records for any domain

Perform DNS Lookup

Domain or Hostname *

Record Type *

A AAAA CNAME MX TXT NS SOA SPF

Quick Lookups

Record Types

AMaps domain to IPv4 address

AAAAMaps domain to IPv6 address

CNAMEAlias to another domain

MXMail exchange servers

TXTText records (SPF, DKIM, etc.)

NSAuthoritative nameservers

SOAStart of authority info

SPFSender Policy Framework

Tips

Use _dmarc.domain.com for DMARC records
DKIM selectors: selector._domainkey.domain.com
DNS changes may take up to 48 hours to propagate

Want automated management?

DMARC Busta's Autopilot manages SPF, DKIM, and DMARC automatically with AI-powered decisions.

Get Started Free

Understanding DNS Records for Email

The foundation of email delivery, authentication, and security

The Domain Name System (DNS) is the foundation of email delivery. Every time an email is sent, receiving servers query DNS to determine where to route the message, how to verify the sender's identity, and whether the message should be trusted. Without correctly configured DNS records, your email may never reach its intended recipients.

Several DNS record types play a role in email. MX (Mail Exchange) records tell other servers where to deliver mail for your domain. TXT records carry critical authentication data — they are used to publish SPF policies that define authorised sending servers, and DMARC policies that instruct receivers how to handle authentication failures. CNAME records are commonly used for DKIM key delegation, pointing selectors to your email provider's signing infrastructure.

Beyond email-specific records, A records map your domain to IP addresses, NS records identify your authoritative nameservers, and SOA records contain administrative information about your DNS zone. Understanding how these records interact is essential for maintaining reliable email delivery and strong domain security.

Use this DNS Lookup tool to inspect any record type for your domain and verify that your email infrastructure is correctly configured.

Example DNS Records


                                A      203.0.113.10
                                MX     10 mail.example.com
                                TXT    v=spf1 include:_spf.google.com ~all
                                CNAME  alias.example.com
                                NS     ns1.provider.com

DNS & Email Flow

Sender's server looks up your MX records

Receiver queries TXT for SPF & DMARC

CNAME resolves DKIM signing keys

Authentication results determine delivery

What This Tool Checks

Query and inspect eight DNS record types that power your domain

A & AAAA Records

Maps your domain name to an IPv4 or IPv6 address. Essential for web hosting and used by some email configurations to resolve sender IP addresses.

MX Records

Identifies the mail servers responsible for receiving email for your domain. Priority values determine the order in which servers are tried.

TXT & SPF Records

Stores text-based data including SPF policies, DMARC policies, domain verification tokens, and other authentication information critical for email security.

CNAME, NS & SOA Records

CNAME creates aliases for DKIM delegation. NS specifies authoritative nameservers. SOA contains zone administrative information.

Common DNS Issues Affecting Email

DNS misconfigurations that can break your email delivery

Missing MX Records

Without MX records, other mail servers have no way of knowing where to deliver email for your domain. This is one of the most fundamental DNS requirements for receiving email. Fix: Add MX records pointing to your mail servers with appropriate priority values.

Incorrect TXT Records

SPF and DMARC policies are published as TXT records. Syntax errors, duplicate records, or outdated entries can cause authentication failures. Fix: Use our SPF Checker to validate your records. Remember, SPF requires exactly one record per domain.

DNS Propagation Delays

After making DNS changes, it can take anywhere from a few minutes to 48 hours for updates to propagate across the internet. During this period, different resolvers may return different results. Fix: Plan DNS changes in advance and use lower TTL values before making critical updates.

CNAME Conflicts

A CNAME record cannot coexist with other record types at the same name. Fix: If you need both a CNAME and a TXT record at the same hostname, restructure your DNS. This is particularly relevant when setting up DKIM delegation alongside other subdomain records.

Automate this: Identifying DNS issues early prevents email delivery problems. DMARC Busta continuously monitors your DNS records and alerts you to misconfigurations before they affect your email flow.

Frequently Asked Questions

What DNS records does email need?

At a minimum, your domain needs MX records to route incoming email to your mail servers. For proper authentication, you also need TXT records for SPF (defining authorised senders) and DMARC (setting authentication policy and reporting). DKIM typically uses CNAME records to delegate signing key lookups to your email provider. Together, these records ensure email is delivered reliably and securely.

What is an MX record?

An MX (Mail Exchange) record specifies the mail servers responsible for receiving email on behalf of your domain. Each MX record includes a priority value — lower numbers indicate higher priority. When sending servers deliver mail to your domain, they try the highest-priority (lowest number) server first, falling back to lower-priority servers if the primary is unavailable.

How long do DNS changes take to propagate?

DNS propagation typically takes between 1 and 48 hours, depending on the TTL (Time to Live) value set on the records being changed. Records with shorter TTL values propagate faster because DNS resolvers refresh their caches more frequently. Before making critical changes, consider lowering the TTL in advance so the transition is smoother.

Why isn't my DNS change showing?

The most common reason is DNS caching. Your ISP, operating system, and browser all cache DNS results based on the record's TTL value. Try clearing your local DNS cache, or use this tool to query authoritative nameservers directly. If the change is very recent, simply waiting for the TTL to expire will resolve the issue. You can also check with multiple DNS resolvers to confirm whether propagation is in progress.

Related Tools

More free tools to secure your email authentication

Automate DNS Monitoring for All Your Domains

DMARC Busta continuously monitors your DNS records, detects misconfigurations, and fixes issues automatically — so your email authentication stays healthy without manual effort.

Start Monitoring Free