How to Verify Business Email DNS on Namecheap, Cloudflare & GoDaddy

MailShrine shows the records; your registrar or DNS host is where you paste them. This guide covers the three panels founders hit most — without touching website A/CNAME rows (domain vs hosting).

Real-life example: Patio Supply

Ife’s domain was at Namecheap but DNS pointed at Cloudflare. Editing Namecheap Advanced DNS did nothing. She switched to Cloudflare DNS and verification went green.

Always edit DNS where nameservers point.

Universal checklist

1. Copy records from MailShrine Domains.
2. Remove conflicting old MX / duplicate SPF.
3. Save → start MailShrine verification.
4. Wait for TTL (timing).
5. Round-trip test.

Deep theory: MX · SPF · DKIM · DMARC.

Cloudflare

Namecheap

GoDaddy

What you need

MailShrine values + login to the DNS host that is authoritative + 20–40 minutes.

Step 1: Confirm where DNS lives

Who owns nameservers? Edit there only.

Step 2: Publish MX first

Inbound path (MX).

Step 3: Publish auth TXT

SPF (one) + DKIM + DMARC.

Step 4: Verify in MailShrine

Don’t thrash records every five minutes.

Step 5: Test

External send/receive.

Checklist

• Editing correct DNS hostCompleted
• MX cleanCompleted
• Auth TXT completeCompleted
• Cloudflare grey-cloudCompleted
• Verified + testedCompleted

Common mistakes

1. Editing the wrong DNS panel.
2. Orange-cloud MX.
3. Leaving Google Workspace MX after a trial.
4. Two SPF TXT rows.

Next steps

• Setup walkthrough · Spam fixes · PTR guide

Citations & References

• Reference: Google: Email sender guidelines
• Reference: Cloudflare Learning Center: DNS records
• Reference: ICANN: What is DNS?

Written by Samira O., Email Authentication Specialist. Samira keeps registrar-specific DNS checklists for MailShrine onboarding.