DKIM record still shows "not verified" after 24 hours

DNS propagation is usually the culprit, but 24 hours is long enough that I'd bet on something else — almost always it's how the host field got entered. GoDaddy's DNS panel automatically appends your domain to whatever you type in the “Host” field, so if you literally typed default._domainkey.mycompany.com, GoDaddy likely saved it as:

default._domainkey.mycompany.com.mycompany.com

which won't match what we look up. For GoDaddy specifically, you only want to enter default._domainkey in the Host field (no domain at the end) — GoDaddy appends .mycompany.com for you automatically.

You can check what's actually published by running this from a terminal:

dig TXT default._domainkey.mycompany.com

If that comes back empty or shows a double domain, that confirms it. Can you check your GoDaddy record and let me know what you see?

Glad that was it! Just re-ran the check and dig TXT default._domainkey.mycompany.com now returns your key correctly, and your domain shows as verified on our end too.

On SPF: yes, you want both. DKIM proves the message wasn't tampered with in transit, but SPF tells receiving mail servers which IPs/domains are allowed to send mail as you — without it, spoofed mail claiming to be from your domain is harder for inboxes to reject, which drags down your own deliverability. If you don't already have an SPF record, add a TXT record on the root of your domain (host @) with:

v=spf1 include:_spf.subsimail.com ~all

(or merge include:_spf.subsimail.com into an existing SPF record if you already send mail from this domain elsewhere — you can only have one SPF record per domain). Once SPF and DKIM both pass, setting up DMARC is the natural next step for the best inbox placement, but that's optional to start.

ikllklkl