DMARC record and policy
The record at _dmarc telling receiving servers what to do with mail that fails SPF or DKIM, and where to report it. p=none only watches; p=quarantine and p=reject act on it.
DMARC ties SPF and DKIM to the address people actually see in the From line, and tells receiving servers what to do when a message claiming to be from your domain fails both checks. It also asks them to send you aggregate reports, so you can see who is sending mail in your name — including services you forgot about.
The record lives in DNS as a TXT record at _dmarc.example.com and starts with v=DMARC1. Its key tag is the policy:
p=none— only monitor and report; failing mail is delivered as usual.p=quarantine— send failing mail to spam.p=reject— refuse it outright.
How SiteScan grades it
The scan reads the _dmarc record of the registrable domain. Any published policy is green and the row shows it, p=none included: monitoring is the normal first stage of a rollout, not a misconfiguration. A missing record is a warning, because without it the domain is easy to spoof.
How to roll it out
Start with v=DMARC1; p=none; rua=mailto:dmarc@example.com, read the reports for a few weeks, fix the senders that fail SPF or DKIM, then move to p=quarantine and finally p=reject. Enforcement is also a prerequisite for BIMI. More in email authentication.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “DNS & email”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data