Mailgun domain not verified / 'Domain not found': DNS records (SPF, DKIM, MX, tracking CNAME) missing
Mailgun can't send or marks the domain unverified because required DNS records aren't published.
Domain not found MailgunMailgun domain unverified DNSdomain mg.example.com is not verifiedMailgun DNS records not verifiedMailgun domain state unverified Meaning
Add the TXT (SPF), DKIM TXT (k1._domainkey or similar), MX (for receiving) and CNAME (tracking) records exactly as shown in the dashboard, remove duplicate SPF records, avoid Cloudflare proxy for CNAMEs, wait for propagation and click "Verify DNS settings".
Common causes
- Records not added or typos
- Duplicate SPF record
- Cloudflare proxying on CNAME
- DNS propagation delay
- Wrong domain/subdomain used
⚡ Quick fix
- Copy records exactly from the dashboard
- Merge SPF includes into a single record
- Disable proxy on tracking CNAME and verify
Detailed fix by platform
Shell
- bash
dig +short TXT mg.example.com dig +short TXT k1._domainkey.mg.example.com
How to diagnose
- TXT/DKIM — Published?
- SPF — Single record?
- Proxy — Off?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 5.4.310 Exchange Online: 550 5.4.310 DNS domain does not exist (DNS domain name could not be resolved)
- 550 5.1.8 550 5.1.8 Sender address rejected: Domain not found (sender domain has no DNS A/MX)
- 550 5.7.25 PTR record required SMTP: 550-5.7.25 The IP address sending this message does not have a PTR record setup, or the corresponding forward DNS entry does not point to the sending IP
Most viewed in Email / SMTP
- 550 5.7.1 550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
- Laravel: Connection could not be established with host Laravel: Symfony\Component\Mailer\Exception\TransportException: Connection could not be established with host "smtp.mailtrap.io:2525": stream_socket_client(): Unable to connect
- self-signed certificate (SMTP TLS) Nodemailer: Error: self signed certificate in certificate chain (code: 'ESOCKET') / unable to verify the first certificate
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026