Your domain, checked and fixed.

Help · Email and spam

MTA-STS "policy fetch failed": the policy file can't be read

DNSFix™ help, reviewed 2026-11-12

Direct answer
  1. 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.
  2. What it means:

    MTA-STS (RFC 8461) has two parts: a TXT record at _mta-sts.yourbusiness.com and a policy file at https://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.

  3. Fix it:

    Check your domain first: the report shows the exact fix for your own setup. The steps are inside Fix this.

    Got a record from a chatbot or your web person? Check it before you paste it.

    Fix this
    1. Open https://mta-sts.yourbusiness.com/.well-known/mta-sts.txt in a browser. It should show a short text file with no warnings.
    2. Fix the DNS record, certificate or file path for that name.
    3. Run the free check, which reads both the record and the file.
Common causes
    • 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
  1. 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.
  2. What to do:

    Check your domain

Questions
  1. Does a failed fetch stop my email?

    No. Senders fall back to their normal behavior, so mail still arrives, just without MTA-STS protection.

DNSFix™ Help
Hi, this is DNSFix™ Help. Ask anything about your domain or account. Answers come from our help library, and some are drafted by AI and say so. After any change, check your domain again: the report tests every record against the standard rules. Need more help? We'll follow up by email.