Skip to main content

​
Overview

Verifying a domain involves these steps:
  1. Add your domain to Migma
  2. Copy the DNS records from Migma
  3. Add these records to your DNS provider
  4. Click Verify in Migma
When completed correctly, your domain typically verifies within 15 minutes. If your domain isn’t verifying, this guide will help you troubleshoot.

​
Quick Checks

Before diving into detailed troubleshooting, verify these basics:
1

All Records Added

Confirm you’ve added all 7 DNS records:
  • 3 DKIM CNAME records
  • 1 SPF TXT record (on root domain)
  • 1 DMARC TXT record
  • 1 MAIL FROM MX record
  • 1 MAIL FROM TXT record
2

Correct Location

Records must be added to the correct subdomain:
  • DKIM: [token]._domainkey.yourdomain.com
  • SPF: yourdomain.com (root)
  • DMARC: _dmarc.yourdomain.com
  • MAIL FROM: send.yourdomain.com
3

Values Match Exactly

Copy and paste values directly from Migma. Don’t type them manually.
4

Wait for Propagation

DNS changes take 5-60 minutes typically. DKIM can take up to 72 hours in rare cases.

​
Common Verification Issues

​
DKIM Records Not Verifying

DKIM verification can take the longest. Here’s what to check:
Problem: Extra spaces, quotes, or trailing dots in the CNAME value.How to check:
dig CNAME [token]._domainkey.yourdomain.com
Solution:
  • Delete the record
  • Copy the value directly from Migma
  • Paste without any modifications
  • Save the record
Problem: You accidentally created a TXT record instead of CNAME.Solution:
  • Delete the incorrect TXT record
  • Create a new CNAME record with the correct type
Problem: Cloudflare proxy is enabled (orange cloud) for CNAME records.Solution:
  • Go to Cloudflare DNS settings
  • Find your DKIM CNAME records
  • Click the orange cloud to turn it gray (DNS only)
Email authentication records cannot be proxied.
Problem: DKIM verification hasn’t completed after 48 hours.Steps:
  1. Verify the CNAME records are publicly visible: 
    dig CNAME [token]._domainkey.yourdomain.com
  2. If records aren’t visible, check with your DNS provider
  3. Delete and re-add the domain in Migma
  4. Add fresh DNS records

​
SPF Record Not Verifying

Problem: You have more than one TXT record starting with v=spf1.How to check:
dig TXT yourdomain.com | grep spf
If you see multiple v=spf1 records, you have duplicates.Solution:
  • Keep only ONE SPF record
  • Combine all includes into a single record: 
    v=spf1 include:_spf.google.com include:spf.migma.ai ~all
Problem: include:spf.migma.ai is in the wrong position or has typos.Correct format:
v=spf1 include:spf.migma.ai ~all
With existing includes:
v=spf1 include:_spf.google.com include:spf.migma.ai ~all
Common mistakes:
  • v=spf1 ~all include:spf.migma.ai ❌ (include must be before ~all)
  • v=spf1 include:spf.migma.ai ❌ (missing ~all or -all at end)
  • v=spf1 include: spf.migma.ai ~all ❌ (extra space)
Problem: SPF record added to a subdomain instead of root domain.Check: SPF for sending authorization should be on yourdomain.com, not send.yourdomain.com or another subdomain.Note: You also need a separate SPF record on send.yourdomain.com for MAIL FROM.

​
MAIL FROM Not Verifying

Problem: The MX record for send.yourdomain.com is missing or has wrong value.How to check:
dig MX send.yourdomain.com
Solution:
  • Add the MX record with priority 10
  • Copy the value exactly from Migma
  • Ensure the subdomain is send, not mail
Problem: The SPF TXT record for send.yourdomain.com is missing.How to check:
dig TXT send.yourdomain.com
Solution: Add a TXT record:
  • Name: send
  • Value: v=spf1 include:spf.migma.ai ~all
Problem: Another service already uses priority 10 on send.yourdomain.com.Solution: Use a different priority number (e.g., 5 or 20).See MX Record Conflicts for details.

​
DMARC Not Verifying

Problem: DMARC record created with incorrect name.Correct: _dmarc.yourdomain.comCommon mistakes:
  • dmarc.yourdomain.com ❌ (missing underscore)
  • _dmarc without domain ❌ (depends on DNS provider)
Solution: Create a TXT record with name _dmarc (some providers append the domain automatically).
Problem: DMARC value has syntax errors.Correct format:
v=DMARC1; p=quarantine; rua=mailto:[email protected]
Common mistakes:
  • Extra spaces or missing semicolons
  • Wrong policy value (should be quarantine or reject)
  • Typo in DMARC1

​
DNS Provider Issues

​
Auto-Appending Domain Names

Some DNS providers automatically append your domain to record values. Problem: Your MX record becomes: 
feedback-smtp.us-east-1.amazonses.com.yourdomain.com
Instead of: 
feedback-smtp.us-east-1.amazonses.com
Solution: Add a trailing period (dot) at the end: 
feedback-smtp.us-east-1.amazonses.com.

​
Records in Wrong DNS Provider

If your domain uses multiple DNS services (registrar, Cloudflare, Vercel, etc.), you might be adding records to the wrong one. How to check: 
dig NS yourdomain.com
This shows which nameservers control your domain. Add Migma’s DNS records at that provider.

​
Checking Your DNS Records

​
Using Web Tools

​
Using Terminal Commands

Check DKIM CNAME records: 
dig CNAME [token]._domainkey.yourdomain.com
Check SPF record: 
dig TXT yourdomain.com | grep spf
Check DMARC record: 
dig TXT _dmarc.yourdomain.com
Check MAIL FROM MX: 
dig MX send.yourdomain.com
Check MAIL FROM SPF: 
dig TXT send.yourdomain.com

​
DNS Propagation Times

Record TypeTypical TimeMaximum Time
TXT (SPF, DMARC)5-15 minutes24 hours
CNAME (DKIM)15-60 minutes72 hours
MX (MAIL FROM)5-15 minutes24 hours
If records aren’t visible after the maximum time, the issue is with your DNS configuration, not propagation.

​
Still Not Working?

If you’ve tried everything above and your domain still won’t verify:
1

Delete and Re-add

In Migma, delete the domain and add it fresh. This generates new DNS records.
2

Screenshot Your DNS

Take screenshots of all DNS records you’ve added.
3

Contact Support

Reach out with:
  • Your domain name
  • Screenshots of your DNS configuration
  • Output from the dig commands above

​
Next Steps

MX Record Conflicts

Understand MX record conflicts

Cloudflare Setup

One-click DNS with Cloudflare