DMARC Reports
Get DMARC Report Status
Configure DMARC Reports
ModelsExpand Collapse
DMARCReportGetResponse object { approved_sources, created, created_at, 9 more } Response for GET/PATCH /dmarc-reports
Response for GET/PATCH /dmarc-reports
approved_sources: optional array of object { created, created_at, domain, 6 more } List of approved sending sources (omitted when empty)
List of approved sending sources (omitted when empty)
Use modified_at instead.
Deprecated, use modified_at
records: optional object { bimi_records, cname_dkim_records, cname_dmarc_records, 5 more } Live DNS records for the zone, grouped by type
Live DNS records for the zone, grouped by type
cname_dmarc_records: optional array of object { id, content, name, 2 more } CNAME records at _dmarc. When such a CNAME resolves to a DMARC TXT record, the API returns that record in resolved_dmarc_records.
CNAME records at _dmarc. When such a CNAME resolves to a DMARC TXT record, the API returns that record in resolved_dmarc_records.
status: optional "missing-dmarc-report" or "multiple-dmarc-reports" or "missing-dmarc-rua" or "cname-on-dmarc-record"DMARC configuration status. The API omits this field when DMARC is correctly configured. If the zone lacks a DMARC TXT record of its own, the API resolves _dmarc.{zone} recursively and evaluates whatever that lookup returns. A CNAME at _dmarc.{zone} that points to a valid DMARC record is therefore healthy; the cname-on-dmarc-record value means the CNAME resolves to no DMARC record at all.
DMARC configuration status. The API omits this field when DMARC is correctly configured. If the zone lacks a DMARC TXT record of its own, the API resolves _dmarc.{zone} recursively and evaluates whatever that lookup returns. A CNAME at _dmarc.{zone} that points to a valid DMARC record is therefore healthy; the cname-on-dmarc-record value means the CNAME resolves to no DMARC record at all.
DMARCReportEditResponse object { approved_sources, created, created_at, 9 more } Response for GET/PATCH /dmarc-reports
Response for GET/PATCH /dmarc-reports
approved_sources: optional array of object { created, created_at, domain, 6 more } List of approved sending sources (omitted when empty)
List of approved sending sources (omitted when empty)
Use modified_at instead.
Deprecated, use modified_at
records: optional object { bimi_records, cname_dkim_records, cname_dmarc_records, 5 more } Live DNS records for the zone, grouped by type
Live DNS records for the zone, grouped by type
cname_dmarc_records: optional array of object { id, content, name, 2 more } CNAME records at _dmarc. When such a CNAME resolves to a DMARC TXT record, the API returns that record in resolved_dmarc_records.
CNAME records at _dmarc. When such a CNAME resolves to a DMARC TXT record, the API returns that record in resolved_dmarc_records.
status: optional "missing-dmarc-report" or "multiple-dmarc-reports" or "missing-dmarc-rua" or "cname-on-dmarc-record"DMARC configuration status. The API omits this field when DMARC is correctly configured. If the zone lacks a DMARC TXT record of its own, the API resolves _dmarc.{zone} recursively and evaluates whatever that lookup returns. A CNAME at _dmarc.{zone} that points to a valid DMARC record is therefore healthy; the cname-on-dmarc-record value means the CNAME resolves to no DMARC record at all.
DMARC configuration status. The API omits this field when DMARC is correctly configured. If the zone lacks a DMARC TXT record of its own, the API resolves _dmarc.{zone} recursively and evaluates whatever that lookup returns. A CNAME at _dmarc.{zone} that points to a valid DMARC record is therefore healthy; the cname-on-dmarc-record value means the CNAME resolves to no DMARC record at all.