MTA-STS Policy Fetch Failed: Fix mta-sts.txt Not Found
The short answer (what's causing it)
The _mta-sts TXT record exists, but senders can't retrieve https://mta-sts.yourdomain/.well-known/mta-sts.txt — missing DNS for the subdomain, an invalid certificate, a redirect, or wrong content type.
Step-by-step fix
- Ensure
mta-sts.yourdomainresolves (A/CNAME). - Serve it over HTTPS with a valid certificate for that exact hostname.
- Place the file at
/.well-known/mta-sts.txt, served astext/plain, without redirects. - Fetch it with curl to confirm, then scan.
Record examples (replace example.co.uk with your domain)
curl -sv https://mta-sts.example.co.uk/.well-known/mta-sts.txt
version: STSv1
mode: testing
mx: mail.example.co.uk
max_age: 86400
Examples are illustrative templates, not values for your domain. Test changes at
p=none/ staging first.
Check yours free in seconds
Run the free 20-check SuperTool on your domain: no signup, no install, public DNS only. Relevant checks: MTA-STS.
Scan my domain free (20-check SuperTool) → £24 Sovereign DMARC (T0 RUA), SPF, MTA-STS & PHP2Shell Remediation Pack → £5 Website Launch Special Quick-Fix Pack →One-off download via PayPal guest checkout, no subscription. Packs contain DNS/config templates and scripts you run yourself.
Frequently Asked Questions
Can I host it on GitHub Pages/Cloudflare?
Yes, as long as the hostname, certificate and path are correct.
Do redirects work?
RFC 8461 says senders must not follow redirects.
Related FaultyPacket guides & tools
- Free 20-check SuperTool
- Zero-downtime DMARC p=reject, SPF & MTA-STS rollout
- Website hosting & MX records DNS setup 101
Authorised use: only scan domains you own or are authorised to inspect. Results are point-in-time public DNS observations.