Proton Mail custom domain
Proton's custom-domain support asks the owner to add MX, SPF, and DKIM records Proton shows in account settings. Proton hosts the MX when the domain receives mail at Proton.
The exact record values depend on the plan and domain. Proton's support article walks through verifying ownership before mail flows through Proton's infrastructure.
Verification
Proton's setup flow verifies the domain before MX cutover. Copy MX, SPF, and DKIM exactly as shown for that domain; another Proton user's table is not valid for yours.
If a second service also sends mail for the domain, RFC 7208 still allows only one SPF version record on the name used in the SPF check. Merge includes rather than adding a second apex TXT.
Plan-specific values
Record values come from Proton's setup wizard. Copy the set Proton shows for the domain; do not reuse another domain's table.
RFC 7208 still applies: only one SPF TXT that starts with v=spf1 may remain on a name. If Proton and another sender both mail for the domain, merge includes into that single record.
Proton's wizard also publishes DKIM selectors for outbound mail. DMARC at _dmarc remains the domain owner's separate policy record under RFC 7489.