To improve the deliverability of your emails and reduce the chance of them being marked as spam, it’s important to configure DKIM, SPF, and DMARC records properly.
selector1
.example.com
.._domainkey.
, and then the domain (e.g., selector1._domainkey.example.com
).v=DKIM1; k=rsa; p=[public_key]
.ip4:203.0.113.0/24
or include:anotherdomain.com
).@
to apply to the entire domain.Purpose: Sets a policy for how emails that fail DKIM/SPF should be treated.
What to Enter:
none
, quarantine
, or reject
.s
for strict or r
for relaxed alignment of DKIM signatures.s
for strict or r
for relaxed alignment of SPF checks.mailto:
and typically uses a reports@
address for the domain.Adding to DNS:
_dmarc.
followed by the domain (e.g., _dmarc.example.com
).v=DMARC1; p=[policy]; adkim=[adkim]; aspf=[aspf]; rua=mailto:[reports@example.com]
Policy Settings:
p=none
only monitors failing emails without taking any action.p=quarantine
marks failing emails as suspicious.p=reject
prevents failing emails from reaching the recipient’s inbox.Alignment Modes:
adkim=s
: Strict alignment for DKIM requires the signing domain to match the From domain.aspf=s
: Strict alignment for SPF requires the Return-Path domain to match the From domain.Reporting Address (rua):
-all
for strict enforcement or ~all
for soft enforcement.p=none
to monitor the impact, and then adjust to quarantine
or reject
as needed.Add these records to your DNS provider’s control panel under the appropriate TXT record type for each specification.