Domain verification
DMARC policy
PostFrame generates a starter DMARC record for your domain, p=none with aggregate reports sent to an address on your domain, and checks it alongside SPF and DKIM. Tighten the policy once the reports look clean.
Policy and reporting
Start by watching
The generated record uses p=none, so nothing legitimate is dropped while you review reports. You can move to quarantine and then reject yourself later.
Reports go to a mailbox you own
Receiving servers send aggregate XML reports to the address in the rua tag, which is on your own domain.
Recommended, not required
DMARC is listed as recommended. The check still reports it as found, missing or mismatch, but verification does not wait on it.
SPF stays aligned
PostFrame sets a custom bounce domain, bounce.yourdomain.com, with its own MX and SPF record, so the envelope sender is on your domain.
DMARC record
- Record type
- TXT
- Host
- _dmarc.yourdomain.com
- Generated value
- v=DMARC1; p=none; rua=mailto:dmarc@<yourdomain.com>
- Required to verify?
- No. It is recommended. The check still reports found, missing or mismatch.
PostFrame, answered
Is DMARC required to verify a domain?
No. Verification requires the ownership TXT record, the three DKIM CNAMEs, the SPF record, and the MX and SPF records on the bounce subdomain. DMARC is listed as recommended and checked the same way.
Which policy should I start with?
p=none. It changes nothing about delivery and gets you the aggregate reports. Move to quarantine, and then reject, once the reports show only senders you recognise.
Where do the DMARC reports go?
To the mailbox named in the rua tag of your record, an address on your own domain. PostFrame generates the record; the reports come from the receiving mail servers.
Run your business from one place.
Five plans, 25 launch apps, one dashboard. Change tiers any time.
From $0 · Basic $9.95/mo · Upgrade or downgrade any time