The DKIM records for Proton Mail
Proton requires three CNAME records for DKIM: protonmail._domainkey, protonmail2._domainkey and protonmail3._domainkey. The targets are specific to each domain and are shown on the “DKIM” tab of the domain wizard.
By its own account Proton generates a new 2048-bit key every six months. Because your records only point to Proton, this change happens automatically; three selectors make sure the old and the new key can be valid side by side. There is nothing to switch on: Proton detects the records and starts signing.
How to set up DKIM for Proton Mail
The steps in the Proton Mail admin interface and at the DNS host:
- In the Proton settings open “All settings”, “Organization” and “Domain names” and choose “Review” for the domain.
- Copy the three CNAME records with their targets from the “DKIM” tab.
- Create all three CNAMEs at the DNS host; at Cloudflare with the proxy status “DNS only”.
- Wait until Proton detects the records and check in the DKIM checker with the selector protonmail.
Publishing at the DNS host
DKIM records always live at selector._domainkey. Most DNS editors append the domain themselves, so you only enter the part before it. CNAME records for DKIM must not sit behind a proxy. The guides per host below show where the record is created in the respective DNS editor.
Verify and keep an eye on it
The DKIM checker below queries the key under the selector and checks structure and length. You see whether the records for Proton Mail are publicly visible. DomainWarn keeps checking them afterwards and alerts you when a key disappears or changes.