DNS MX Record Propagation Checker

Audit DNS records worldwide: inspect A, AAAA, CNAME, MX (mail exchange), TXT (SPF, DKIM, DMARC), and NS records across global recursive resolvers.

Record Type:

Enter domain without www or http (e.g. example.com)

Explore More Free Tools

Complementary diagnostic tools to audit your website infrastructure, security, and conversion funnels.

Domain Availability & WHOIS

Query global authoritative root servers across .com, .ai, .io, and .co without registrar front-running.

Use Tool

Password Entropy Generator

Calculate exact Shannon cryptographic entropy bits and GPU brute-force cracking resistance.

Use Tool

Conversion Rate Calculator

Benchmark your site conversion efficiency and see the exact revenue lift from CRO improvements.

Use Tool

How to Use the DNS & MX Propagation Checker

Query authoritative global DNS Anycast nodes to inspect record propagation, mail exchange priorities, and SPF/DKIM verification.

01

1. Enter Your Domain Name

Type your bare root domain or subdomain (e.g., example.com or mail.example.com). Omit https:// or www to audit clean DNS zone configurations.

02

2. Select Target Record Type

Choose between MX (Mail Exchange routing), TXT (SPF, DKIM, DMARC), A (IPv4 address), AAAA (IPv6 address), CNAME, or NS (Nameservers).

03

3. Inspect Authoritative TTLs & Values

Review returned records, numerical priority weights, and Time-To-Live (TTL) countdown values across globally distributed recursive nameservers.

DNS Resolution Architecture & TTL Cache Expiration

The Domain Name System (DNS) acts as the global distributed directory of the internet. When an external mail transfer agent (MTA) like Google Workspace or Microsoft Exchange attempts to deliver an email to [email protected], it issues a recursive DNS query to resolve your zone's authoritative Mail Exchange (MX) records.

DNS propagation is governed strictly by the Time-to-Live (TTL) parameter specified in the Start of Authority (SOA) and resource records. Intermediate recursive resolvers (ISPs, public DNS like Cloudflare 1.1.1.1 and Google 8.8.8.8) cache query responses until the TTL timer decrements to zero across each hop in the global lookup pipeline:

Global DNS Recursive Query & Mail Routing Pipeline RFC 1035 & RFC 5321 Standards
Hop 01

Stub Resolver

Client OS or local router checks cached query records.

Hop 02

Recursive DNS

ISP or Anycast node (1.1.1.1, 8.8.8.8) queries root zone.

Hop 03

Authoritative NS

Cloudflare or Route53 returns active MX hostnames and TTL.

Hop 04

SMTP Handshake

Sending MTA establishes TLS connection to lowest MX priority.

MX Priority Delivery Rule: Inbound MTAs deliver strictly to the lowest preference integer first (Priority 1 before Priority 5, and Priority 5 before Priority 10). Higher numerical values serve solely as failover backup relays.
Real-World Enterprise MX Record Hierarchy Standard Google Workspace Cluster

A properly configured commercial domain publishes multiple redundant MX endpoints across distinct geographic server tiers:

1. Primary Target (Priority 1)
ASPMX.L.GOOGLE.COM
Handles 99.9% of inbound SMTP connections
2. Backup Relays (Priority 5)
ALT1.ASPMX.L.GOOGLE.COM
ALT2.ASPMX.L.GOOGLE.COM
3. Standby Failover (Priority 10)
ALT3.ASPMX.L.GOOGLE.COM
ALT4.ASPMX.L.GOOGLE.COM
Recommended Production TTL: 3600 seconds (1 hour). Pre-migration TTL: 300 seconds (5 minutes).
Status: High Availability Active

DNS Propagation Timelines & Cache Decay Milestones

When you update DNS records at your registrar or Cloudflare/AWS Route53, changes do not propagate instantaneously worldwide. Propagation follows a predictable decay curve based on resolver cache hierarchies.

Elapsed Time Propagation Tier Global Coverage Operational Status & Technical Reality Primary Responding Nodes
0 – 5 Min Authoritative Tier 10% - 25% Authoritative nameservers update immediately. New queries with zero prior cache receive fresh records instantly. Cloudflare NS, Route53, Namecheap
15 – 60 Min Public Anycast Resolvers 60% - 80% Tier-1 public recursive resolvers (1.1.1.1, 8.8.8.8, 9.9.9.9) flush expired TTLs and re-query authoritative NS. Google DNS, Cloudflare, Quad9, OpenDNS
2 – 12 Hours Regional Telecom ISPs 90% - 98% Commercial broadband providers and mobile carriers honor standard 3600s–14400s TTL intervals. Comcast, Verizon, AT&T, Vodafone, Orange
24 – 48 Hours Legacy Stub Caches 99.9% Full Strict corporate proxies and non-compliant resolvers enforcing artificial minimum cache durations finally expire. Government proxies, rural mobile base stations

Core DNS Record Types for High-Deliverability Domains

Modern inbox providers (Gmail, Yahoo Mail, Outlook) mandate full cryptographic alignment. Missing any of the records below will cause your transactional and marketing emails to land directly in spam folders.

Record Core Purpose Example Value Syntax Impact on Email Deliverability & Domain Security
MX Inbound Mail Routing 10 mail.example.com Directs inbound emails to designated mail servers. Without valid MX records, your domain cannot receive customer emails or support tickets.
TXT (SPF) Sender Policy Framework v=spf1 include:_spf.google.com ~all Explicitly authorizes which IP addresses and third-party services (SendGrid, Postmark, Google) are permitted to send mail on behalf of your domain.
TXT (DKIM) DomainKeys Identified Mail v=DKIM1; k=rsa; p=MIGfMA0GCS... Attaches an asymmetric cryptographic signature to email headers, proving that messages were not intercepted, forged, or altered in transit.
TXT (DMARC) Domain-based Message Auth v=DMARC1; p=reject; rua=mailto:... Instructs receiving mail servers how to treat messages that fail SPF or DKIM checks (p=none, p=quarantine, or p=reject). Mandated by Google and Yahoo since 2024.
A / AAAA Host IP Mapping 192.0.2.1 / 2001:db8::1 Maps your domain or hostnames to web servers and mail exchangers. Required for MX records that reference hostnames.

6 Critical DNS Errors That Send Your Emails to Spam

Email delivery failures rarely occur at random. Inbox rejection and blacklisting trace back to these recurring DNS misconfigurations.

01

Exceeding the 10-DNS-Lookup SPF Limit

RFC 7208 mandates that evaluating an SPF record cannot require more than 10 recursive DNS lookups (via include, a, mx, or redirect). Stacking multiple SaaS services causes PermError, instantly invalidating SPF.

02

DMARC Policy Left on p=none

Setting p=none merely monitors traffic without blocking spoofed emails. Phishers can impersonate your exact brand domain without receiving mail servers rejecting the fraudulent messages, degrading your domain sender reputation.

03

Missing or Inverted MX Priorities

Configuring backup mail relays with identical or lower priority values than primary servers causes inbound SMTP traffic to hit servers without active mailboxes, returning 550 5.1.1 User unknown bounce codes.

04

Broken DKIM Selectors After Migration

When migrating between email marketing platforms (e.g., Mailchimp to Klaviyo), forgetting to update or add new CNAME/TXT selector keys causes receiving MTAs to fail cryptographic verification and flag messages as forged.

05

Excessively High TTL Before DNS Migration

Attempting to migrate mail hosts with TTLs set to 86400 (24 hours) leaves half of global inbound email routing to obsolete decommissioned servers for days. Always lower TTL to 300 seconds 48 hours prior to migration.

06

Missing Forward-Confirmed Reverse DNS (FCrDNS)

If your sending IP lacks a PTR record matching the forward A record hostname announced in the SMTP HELO / EHLO handshake, major spam filters (Spamhaus, Barracuda) immediately drop connections.

Authentication Protocols Compared: SPF vs DKIM vs DMARC

A common misconception is that SPF alone is sufficient for deliverability. Modern email security operates as a three-legged stool: all three standards must pass and align.

Evaluation Criterion SPF (Sender Policy Framework) DKIM (DomainKeys Identified Mail) DMARC (Domain Alignment & Reporting)
Primary Protection Validates authorized sending server IP addresses Verifies message contents were not modified in transit Enforces domain alignment and mandates reject/quarantine actions
Verification Mechanism DNS TXT record lookup against SMTP Return-Path RSA public/private key cryptographic signature in headers Verifies From: header domain matches SPF or DKIM
Behavior on Email Forwarding Fails (forwarding server IP is not in original SPF) Passes (cryptographic header signature remains valid) Passes via DKIM survival
2024+ Mandate Status Mandatory for all senders Mandatory for all senders Strictly mandatory (> 5,000 emails/day)

4-Phase Mail Infrastructure Hardening Playbook

Execute this systematic checklist to ensure 100% DNS propagation and bulletproof email inbox placement.

Phase 1: DNS Zone Cleanliness & Pre-Migration
  • ✓ Audit zone for duplicate or conflicting MX records from previous hosting providers.
  • ✓ Drop TTL values on MX, A, and TXT records to 300 seconds 48 hours prior to mail server migration.
  • ✓ Eliminate multiple SPF records into a single consolidated v=spf1 ... string.
Phase 2: Mail Exchange Redundancy
  • ✓ Publish at least 2 distinct MX servers with distinct numeric priorities for failover resilience.
  • ✓ Verify MX targets point directly to fully qualified domain names (FQDNs), never naked IP addresses.
  • ✓ Ensure destination hostnames resolve to active A / AAAA records with valid reverse DNS (PTR).
Phase 3: Cryptographic Alignment
  • ✓ Configure 2048-bit RSA DKIM keys for every active sending service (Google, Stripe, Customer.io).
  • ✓ Set up custom return-path subdomains (e.g., em.example.com) to achieve SPF domain alignment.
  • ✓ Verify total DNS mechanism lookups remain at 10 or fewer across all includes.
Phase 4: DMARC Enforcement & Monitoring
  • ✓ Deploy DMARC on monitoring mode (v=DMARC1; p=none; rua=mailto:dmarc@...).
  • ✓ Analyze XML aggregate reports for 2 to 4 weeks to identify legitimate third-party sending services.
  • ✓ Graduate policy to p=quarantine and finally p=reject to eliminate domain spoofing entirely.

Best Practices for Managing DNS and Mail Deliverability

Treat DNS zone files as production code rather than passive settings. Every entry in your DNS zone file impacts server reachability, security posture, and customer communication channels. Establish strict change management protocols: never alter MX or nameserver records without first backing up your existing zone file and communicating maintenance windows to team stakeholders, and always use version-controlled Infrastructure-as-Code (such as Terraform or OctoDNS) when managing enterprise DNS architectures.

Master the strategic timing of Time-to-Live (TTL) adjustments before executing any server migration. Leaving TTLs at standard 24-hour durations (86400s) forces your domain into a multi-day propagation purgatory where some global users connect to the new mail provider while others deliver to the old, generating split-brain inbox states. Lowering TTLs to 300 seconds two full days ahead of a planned migration guarantees that changes will take effect worldwide within five minutes of record substitution.

Finally, actively monitor your domain's sending reputation and DMARC aggregate reports rather than waiting for customer support complaints about missing emails. Connect automated tools like Google Postmaster Tools, Microsoft SNDS, and dedicated DMARC report parsers to catch sudden spikes in spam complaints, SPF lookup overflow errors, or blacklist listings. Early intervention prevents domain-level reputation degradation that can take months of painful remediation to reverse.

From the Blog

Explore in-depth technical guides, conversion optimization strategies, and infrastructure playbooks to scale your business.

How to Optimize Your Mobile Checkout and Lead Forms

Over 65% of web traffic is mobile, but mobile conversion rates routinely lag desktop by half. Learn how to fix keyboards, input fields, and mobile layouts so shoppers finish what they started.

Read article

How to Use Website Heatmaps and Screen Recordings to Spot Friction

Analytics tell you what visitors do, but qualitative tools show you why they do it. Learn how to review session recordings in 20 minutes a week to uncover dead clicks, rage clicks, and hidden layout bugs.

Read article

The Beginner's Guide to Running A/B Tests Without Wasting Time

A/B testing can feel overwhelming if you don't have millions of visitors. Here is a practical, grounded guide to forming testable hypotheses, knowing when your test is done, and avoiding common testing mistakes.

Read article

How to Write Call-to-Action Buttons That People Actually Click

Stop using generic buttons like "Submit" or "Click Here." Learn the psychology behind high-converting CTAs, how to communicate instant value, and what colors and placements really matter.

Read article

7 Simple Landing Page Tweaks That Can Lift Conversions

You don't need a costly, risky website redesign to improve your results. Small, deliberate adjustments to your headlines, form fields, and visual hierarchy often deliver the biggest conversion gains.

Read article

Why Most Visitors Leave Your Website Without Buying

If 97% of your website visitors leave without taking action, the problem isn't always your product or pricing. Here is an in-depth breakdown of what actually causes shoppers to bounce and how to fix each friction point.

Read article

Frequently Asked Questions

Why do DNS changes take up to 24–48 hours to propagate worldwide? ▼

DNS propagation latency is determined by the TTL (Time-to-Live) of your previous DNS records and the caching policies of hundreds of thousands of independent internet service providers (ISPs) worldwide.

When an ISP resolver caches your domain's old record, it will not query your authoritative nameserver again until that cached TTL expires. While major public DNS nodes (Google, Cloudflare) update within minutes, smaller regional ISPs often enforce arbitrary 24-hour minimum cache windows.

What does the priority number on an MX record mean? ▼

The priority number dictates the delivery sequence for inbound mail transfer agents (MTAs). Lower numbers represent higher priority. A record with priority 1 or 10 will always receive incoming emails before a record with priority 20 or 50.

If the primary mail server fails to respond to connection requests, the sending MTA automatically fails over to the next lowest numerical priority. Records with equal priority will have connections distributed between them randomly for basic load balancing.

Can I have more than one SPF record on my domain? ▼

No. Having more than one TXT record starting with v=spf1 is a strict RFC violation. Receiving mail servers that encounter multiple SPF records will return a PermError and treat SPF authentication as completely failed.

To authorize multiple sending services (e.g. Google Workspace, SendGrid, and Zendesk), consolidate them into a single TXT entry: v=spf1 include:_spf.google.com include:sendgrid.net include:mail.zendesk.com ~all.

What is the difference between an A record and a CNAME record? ▼

An A record maps a hostname directly to an IPv4 address (e.g., example.com -> 192.0.2.1). It represents the definitive numerical endpoint of a server.

A CNAME (Canonical Name) record maps an alias hostname to another hostname (e.g., www.example.com -> example.com). CNAMEs cannot coexist with other records on the exact same name, which is why RFC standards traditionally forbid CNAME records at the root apex domain (though modern DNS providers offer CNAME flattening or ALIAS records).

How do I check if my DMARC policy is properly protecting my domain? ▼

Query your domain's TXT record at the subdomain _dmarc.yourdomain.com. Ensure it contains a valid policy tag: p=reject or p=quarantine. If your tag is set to p=none, you are only in monitoring mode and receiving servers will not block spoofed emails.

Additionally, confirm that you have defined an aggregate reporting mailbox using the rua=mailto:[email protected] tag so you receive daily diagnostic summaries of who is sending email using your domain.

Ready to turn your website visitors into buyers with a 24/7 AI salesman?

ConvertPill embeds interactive AI Advisors, recommendation quizzes, and conversion widgets that guide shoppers in real time, eliminate purchase hesitation, and skyrocket sales.

Free plan available · No credit card required · 2-minute setup