MTA-STS policy
A DNS record telling sending servers to insist on TLS with a valid certificate for mail to this domain. Optional — without it, mail can be downgraded to plain text on the way.
SMTP between mail servers encrypts opportunistically: if anything on the path strips the STARTTLS offer or presents a bogus certificate, the sending server falls back to plain text and delivers anyway. MTA-STS (RFC 8461) closes that gap. It tells sending servers that your domain always accepts mail over TLS with a valid certificate, and that they should refuse to deliver otherwise.
How SiteScan checks
This row appears only if the domain has MX records. The scan looks for a TXT record at _mta-sts.example.com starting with v=STSv1. It is optional, so "Missing" is shown as a neutral fact. Note that the TXT record is only half of the setup: SiteScan does not fetch the policy file itself.
How to set it up
- Publish the policy at
https://mta-sts.example.com/.well-known/mta-sts.txtwith a valid certificate. It containsversion: STSv1,mode: testing(laterenforce), onemx:line per mail host andmax_age: 604800. - Add the TXT record
_mta-sts.example.com TXT "v=STSv1; id=20260101", and change theidwhenever the policy changes. - Start in testing mode and add TLS-RPT so you see failures before enforcing.
Many mail providers document the exact MX values; see also 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