SKYSNAG COMPLY

Email Authentication Setup Wizard

Choose your sending provider and discover which DNS records to configure and verify.

Comply / Run a diagnostic

Run a diagnostic

Free · no sign-up

Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.

How to use and interpret this tool

Select the sending provider and review the expected SPF, DKIM and DMARC configuration workflow. Obtain account-specific selectors, verification tokens and signing keys from that provider's own admin console.

How to read the findings

Use public DNS checks to confirm published records, then send a real test message and inspect its Authentication-Results to verify alignment. A DNS record existing does not prove the mail platform is signing with it.

Limitations and next steps

Provider requirements and tenant-specific values change. Never copy an example DKIM selector or verification token into production without confirming it in your account.

SKYSNAG COMPLY

Need continuous authentication protection?

Explore Skysnag Comply ↗

Method and limitations

Plan SPF, DKIM and DMARC setup for Google Workspace, Microsoft 365, SendGrid, SES, HubSpot, Mailchimp and Customer.io. Public DNS checks cannot prove inbox delivery or message-level authentication.

Technical reference ↗

Frequently asked questions

Can Skysnag generate my account-specific DKIM keys?

No. Selectors and keys must be obtained from your sending provider account before publication.

Can the wizard automatically generate a Google or Microsoft DKIM key?

No. Account-specific DKIM keys and selectors must be issued or configured by the relevant provider.

Educational diagnostics, not a guarantee of deliverability or provider approval.