fcc.gov

Checked 5/14/2026, 10:53:04 PM · 3ms

Solid: p=reject is enforced.

DMARC record

v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]

Policy (p): reject
Subdomain policy (sp): inherits p=reject
Enforcement % (pct): 100%
DKIM alignment (adkim): unset · defaults to r (relaxed)
SPF alignment (aspf): unset · defaults to r (relaxed)
Aggregate reports (rua): mailto:[email protected], mailto:[email protected], mailto:[email protected]
Failure reports (ruf): mailto:[email protected]

All tags (4)

vDMARC1DMARC version
prejectPolicy for the domain
ruamailto:[email protected],mailto:[email protected],mailto:[email protected]Aggregate report URIs
rufmailto:[email protected]Forensic (failure) report URIs

SPF record

Found on the apex domain.

v=spf1 ip4:192.104.54.97 ip4:192.104.54.91 ip4:192.133.125.38 ip4:192.133.125.39 ip4:192.104.54.93 ip4:149.96.193.2 ip4:149.96.192.2 include:mail.zendesk.com include:spf.protection.outlook.com -all

Recommendations

DKIM alignment (adkim) is unset, so it defaults to r (relaxed). That is fine for most deployments. Set adkim=s explicitly only if your DKIM d= header matches the From: domain exactly.
SPF alignment (aspf) is unset, so it defaults to r (relaxed). That is fine for most deployments. Set aspf=s explicitly only if your Return-Path aligns with the From: domain exactly.

AI-assisted remediation

Want a tailored fix plan in plain English?

Wiredepth Pro sends this report to our AI engine and streams back a 30-day rollout plan tailored to fcc.gov, with provider-specific tips when we can infer them from the data. 10 playbooks per month on Pro, 100 on MSP.

ProSee Pro plans→

Check another domain

Or share this URL with the team that owns the records.