DMARC monitoring
Put a domain under DMARC monitoring from your own code: enroll it, publish the DNS record we hand back, and check when reports start flowing.
| Method | Path | Purpose |
|---|---|---|
POST |
/v1/dmarc/domains |
Enroll a domain and get the DNS records to publish. |
POST |
/v1/dmarc/domains/{id}/verify |
Re-read live DNS and move the domain’s status. |
GET |
/v1/dmarc/domains/{id}/dns |
Preview the DNS records again without creating anything. |
GET |
/v1/dmarc/domains |
List monitored domains. |
GET |
/v1/dmarc/domains/{id} |
Retrieve one domain. |
PATCH |
/v1/dmarc/domains/{id} |
Update a domain’s settings. |
DELETE |
/v1/dmarc/domains/{id} |
Delete a domain and revoke its reporting addresses. |
Every endpoint takes a secret key in the Authorization header — see
Authentication.
The flow
Section titled “The flow”Three steps, and the first one gives you everything you need for the second:
- Enroll the domain with
POST /v1/dmarc/domains. The response includes the exact TXT records to publish. - Publish those records in the domain’s DNS.
- Verify with
POST /v1/dmarc/domains/{id}/verifyto confirm we can see them. Reports begin arriving at the next reporting interval — mailbox providers send aggregate reports roughly daily, so allow up to 24–48 hours before the first one lands.
See also
Section titled “See also”- DMARC monitoring in the dashboard
- Authentication
- Errors