GoDaddy DNS email setup checker
Check the public DNS records that matter when email for a domain registered or hosted at GoDaddy is not working.
GoDaddy is a registrar and DNS host. Mailboxes usually come from Microsoft 365 sold through GoDaddy, a direct Microsoft 365 or Google Workspace subscription, or another provider.
Use this page to confirm where DNS is really served and which provider's values belong in it, because GoDaddy's DNS Management page only applies while GoDaddy nameservers are active.
DNS records to check first
| Record | What to check | Safe note |
|---|---|---|
| Nameservers | Confirm whether the domain still uses GoDaddy nameservers or points to Cloudflare, a web host, or another DNS service. | If nameservers point elsewhere, edits in GoDaddy DNS Management are ignored - make email DNS changes at the active DNS host. |
| MX | Confirm the MX records match the actual mailbox provider. Microsoft 365 bought through GoDaddy uses Microsoft MX values that GoDaddy's setup flow normally adds automatically. | Microsoft 365 MX targets are tenant-specific. Copy them from the Microsoft admin center or the GoDaddy email setup screen rather than from another domain or tutorial. |
| SPF | Publish one SPF record for the domain's real senders, such as spf.protection.outlook.com when Microsoft 365 sends the mail. | Merge all senders into a single SPF record; duplicate SPF records cause authentication failures. |
| DKIM | Generate DKIM in the mailbox provider's admin console - for Microsoft 365, the selector1 and selector2 CNAME records - and publish the exact values. | Do not invent tenant-specific DKIM CNAME targets. They are generated per tenant and must be copied from the provider dashboard. |
| DMARC | Add a DMARC record once MX, SPF, and DKIM are settled so receivers know how to treat failing mail. | Begin with p=none and review reports before moving to quarantine or reject. |
Common mistakes
- Editing GoDaddy DNS Management while the domain's nameservers point to Cloudflare or a web host, so nothing changes publicly.
- Copying Microsoft 365 MX or DKIM values from a tutorial instead of the tenant-specific values for this domain.
- Leaving old web-host or email-forwarding MX records behind after moving to Microsoft 365 or Google Workspace.
- Publishing a second SPF record instead of merging the new provider into the existing one.
Boundaries
Domain Email Doctor checks public DNS records only and does not access a GoDaddy or Microsoft account.
Nameserver changes, GoDaddy email subscriptions, and automatic setup records stay inside the GoDaddy dashboard.
Tenant-specific Microsoft 365 values must come from Microsoft or GoDaddy's setup flow, and a passing DNS check does not guarantee inbox placement.