Help · Email and spam
MTA-STS "policy fetch failed": the policy file can't be read
DNSFix™ help, reviewed 2026-11-12
Direct answer
The answer in one or two sentences, then why it happens and how to fix it. How we write and check these pages- Direct answer: Sending servers couldn't download your MTA-STS policy file over HTTPS. Mail still arrives, but without the protection you meant to switch on.
- What it means:
MTA-STS (RFC 8461) has two parts: a TXT record at
_mta-sts.yourbusiness.comand a policy file athttps://mta-sts.yourbusiness.com/.well-known/mta-sts.txt. TLS reports say "policy fetch failed" (sts-policy-fetch-error) when the file can't be fetched. - Fix it:
Check your domain first: the report shows the exact fix for your own setup. The steps are inside Fix this.
Fix this
- Open https://mta-sts.yourbusiness.com/.well-known/mta-sts.txt in a browser. It should show a short text file with no warnings.
- Fix the DNS record, certificate or file path for that name.
- Run the free check, which reads both the record and the file.
Common causes
This part of the page in plain words. How we write our pages- No website is set up at the mta-sts name, or it has no DNS record.
- The HTTPS certificate doesn't cover mta-sts.yourbusiness.com, or has expired.
- The file is at the wrong path, redirects, or isn't plain text.
Stop it happening again
DNSFix™ can check your domain on a schedule and email you when something changes.- What we found: Every DNSFix™ feature is free right now, including the watch that emails you the step-by-step fix soon after we spot a problem.
- What to do:
Questions
This part of the page in plain words. How we write our pagesDoes a failed fetch stop my email?
No. Senders fall back to their normal behavior, so mail still arrives, just without MTA-STS protection.