Sending domain and authentication
Prove each message is yours with SPF, DKIM and DMARC on aligned domains, and send it over checked TLS, or large inboxes reject it.
- Required 5
- Optional 3
Required
Publish an SPF record
RequiredPublish one SPF record for every domain that sends mail, listing every server and service that sends for it.
Sign every message with DKIM
RequiredSign every message with DKIM, using at least a 2048-bit RSA key on your own domain, and replace keys on a schedule.
Enforce DMARC
RequiredPublish a DMARC record, read its reports, and move from
p=nonetop=quarantineand thenp=rejectonce all mail passes.Give sending servers matching DNS names
RequiredGive every sending IP address a reverse DNS name that points back to the same address, and use that name in the SMTP greeting.
Send and receive over TLS
RequiredOffer STARTTLS with a valid certificate on every MX host, and send outgoing mail over TLS.
Optional
Pin mail TLS with DANE
OptionalIf your domain is signed with DNSSEC, publish TLSA records for your MX hosts, so sending servers check the certificate through DNS.
Keep authentication through forwarders with ARC
OptionalIf you run a mailing list or forwarding service, add ARC seals, so receivers can trust results that the forwarding broke.
Show your logo with BIMI
OptionalOnce DMARC is enforced, publish a BIMI record, so supporting inboxes show your verified logo next to your mail.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers email playbook: https://agentwranglers.se/playbook/email/sending-domain-and-authentication.