Authenticate sending domain

Authenticate our sending domain so messages show as from marketing@lumenstudio.com and pass SPF and DKIM checks. Add the DKIM public key and the SPF include at our DNS host, run the verification in our account, and confirm both show as authenticated before the Tuesday product launch.

Before I hand this to the sysadmin, make the authentication request reviewer-friendly: show the exact TXT record strings to paste for DKIM and SPF, explain in one sentence why both are required, and flag any existing SPF TXT that will need merging to avoid breaking other services.

I asked Raj to add DKIM and SPF but the dashboard says DKIM not found while SPF looks okay. I'm the email owner and worried the campaign will be marked suspicious. I don't know if the DKIM selector is wrong, if there's a DNS propagation delay, or if the key was truncated. What three checks will quickly pinpoint the issue and what fix is most likely?

We routinely scramble because DKIM/SPF weren't validated before sends. Are we failing to request keys early, giving ops ambiguous strings, or lacking a follow-up verification step? Recommend a single change to our workflow and one line to add to the campaign kickoff that would prevent last-minute authentication failures.