MX record checker. Mail flow mapped.
Type a domain. The tool queries Cloudflare 1.1.1.1 DoH for the MX records, lists each by priority, and resolves each mail-server hostname's A record so you see the full chain. CORS-allowed, no API key, no log.
Type a domain. The tool queries Cloudflare's DoH endpoint for MX records, lists each by priority (lower = preferred), and resolves the mail-server hostname's A record so you see the full delivery chain. CORS-allowed, no API key, no Digital Heroes log.
Press Look up — the tool fetches MX records via Cloudflare DoH (no API key required).
// no query yet
Sources used by this checker
- Cloudflare DoH JSON API
- RFC 1035 — DNS specification · RFC 8484 — DNS-over-HTTPS
- Lower MX priority = preferred. Sending servers always try the lowest priority first.
Privacy: query goes to Cloudflare DoH; Digital Heroes doesn't log.
Six questions users ask.
What is an MX record?
MX (Mail Exchanger) records tell sending email servers where to deliver mail for your domain. Each has a priority (lower = preferred) and a hostname. Domains without MX records can't receive email.
Why does priority order matter?
Sending email servers always try the lowest-priority MX first. Priority 10 beats 20. Same-priority creates round-robin for load distribution.
What does 'no MX record' mean?
No MX = sending servers fall back to the A record but most mail servers reject this as spam prevention. To receive email, you need explicit MX records.
Why resolve each MX hostname?
Catches broken setups where the MX hostname doesn't resolve — a silent email-delivery failure that's hard to spot. Common cause: MX points at a hostname deleted from DNS.
Where does the data come from?
Cloudflare's DNS-over-HTTPS endpoint at 1.1.1.1 (cloudflare-dns.com/dns-query). CORS-allowed, no API key. Same data as `dig MX yourdomain.com`.
Does this tool log my queries?
Digital Heroes doesn't log. Cloudflare's DoH endpoint logs queries per their resolver privacy policy (anonymized, retained <24 hours).