GoDaddy Email email configuration guide

GoDaddy Professional Email: Message is not DKIM signed

Publishing DKIM CNAMEs makes keys discoverable, but only a new message proves that GoDaddy signed it. Check both DNS and the DKIM-Signature header.

Problem description

A provider configuration symptom may look like:

Provider DKIM signing after a provider configuration change.

Verify signing

  1. Confirm that both GoDaddy-provided DKIM CNAMEs resolve publicly.
  2. Send a new message from the affected mailbox.
  3. View the raw headers and find DKIM-Signature.
  4. Confirm that d= is your sending domain and the receiver reports dkim=pass.

Safe correction sequence

If a CNAME is missing or wrong, restore the exact dashboard value and wait for DNS. If both records resolve but new mail has no signature, contact GoDaddy with the domain, mailbox, timestamp, and message ID; DNS cannot enable a provider-side signer.

MailFixIt boundary

MailFixIt can inspect the supplied selector and headers. It cannot enable signing in GoDaddy.

Frequently asked questions

What does MailFixIt check for GoDaddy Email?

It helps compare public DNS evidence with the provider setup path. It does not access the provider account or claim that a DNS result alone proves sending or receiving.

Should I replace all existing DNS records with provider values?

No. Confirm the exact record owner and type, preserve unrelated legitimate services, and change only the record required for the intended mail route.

Related email diagnostics

Primary sources: GoDaddy: Add SPF, DKIM and DMARC to Professional Email.