MTA-STS checker icon

MTA-STS Checker

Check your domain's MTA-STS configuration. Ensure your emails are transmitted securely with TLS encryption and protect against downgrade attacks and message interception.

MTA-STS checker icon

How Skysnag Simplifies MTA-STS

Skysnag automates the implementation and management of MTA-STS for your domain, ensuring your emails are always transmitted securely.

Automated Setup

Generate and deploy MTA-STS policies with zero manual configuration

DNS Record Management

Create and maintain the required DNS records for MTA-STS

Policy Hosting

Host your MTA-STS policy file on secure, high-availability servers

TLS-RPT Integration

Seamlessly integrate with TLS-RPT for comprehensive reporting

Gradual Deployment

Safely progress from testing to enforcement mode without disrupting email

Continuous Monitoring

Monitor your MTA-STS policy effectiveness and detect issues

What is MTA-STS?

MTA-STS (Mail Transfer Agent Strict Transport Security) is an email security standard that enables domain owners to enforce TLS encryption for all incoming emails. It prevents attackers from intercepting email through downgrade attacks or man-in-the-middle techniques.

Enforce TLS Encryption

Require that all mail servers connecting to your domain use TLS encryption, preventing plaintext email transmission.

Prevent Downgrade Attacks

Stop attackers from forcing email delivery over unencrypted connections where they could intercept messages.

Certificate Validation

Verify the validity of TLS certificates presented by mail servers to prevent man-in-the-middle attacks.

Failure Handling

Define how mail servers should handle delivery failures when TLS requirements cannot be met.

MTA-STS Policy Modes

MTA-STS policies can be deployed in different modes depending on your security requirements:

Start here for visibility

Testing Mode

Monitor mode - report failures but deliver messages anyway

Maximum protection

Enforce Mode

Strict mode - reject delivery if TLS requirements aren't met

For policy removal only

None Mode

No policy enforcement - used to remove an existing policy

MTA-STS Implementation Results

See the impact of implementing MTA-STS with Skysnag

100%

TLS-encrypted email delivery

98%

reduction in downgrade attacks

24/7

policy monitoring and alerts

99.9%

secure email delivery rate

Talk to an expert to review your authentication gaps.

Meet with one of our experts to review your report. We'll walk you through the issues, explain the security gaps, and show you exactly how Skysnag resolves them - automatically.

Discuss my results

See everything Skysnag has to offer

Skysnag gives you everything you need to enforce DMARC, automate SPF and DKIM, deploy MTA-STS and TLS-RPT, and activate BIMI - so your emails are secure, compliant, and trusted.

Monitor Icon

Monitor

Identify email compromise attempts and troubleshoot email delivery issues

Comply Icon

Comply

Comply with Microsoft, Google and Yahoo requirements and visualize sending data in real-time

Protect Icon

Protect

Automate DMARC enforcement for unparalleled email security

Certify Icon

Certify

Certify your brand with the highest identity standard globally

Start for free

MTA-STS guide

What is a MTA-STS record?

MTA-STS (Mail Transfer Agent Strict Transport Security) is a standard that forces other mail servers to deliver email to you over an encrypted TLS connection. It has two parts: a DNS TXT record at _mta-sts.yourdomain.com and a policy file hosted at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt.

What is MTA-STS?

MTA-STS, defined in RFC 8461, closes a gap in email encryption. Normally STARTTLS is opportunistic — an attacker can strip it and force plaintext. MTA-STS lets you publish a policy that says “only deliver to me over valid TLS,” and compliant senders will refuse to downgrade.

It works in two pieces. A small DNS TXT record (v=STSv1; id=...) signals that a policy exists and when it last changed. The actual policy file, served over HTTPS at a fixed .well-known path, lists your mail servers, the enforcement mode, and how long senders should cache it.

Pair MTA-STS with TLS-RPT: MTA-STS enforces encryption, TLS-RPT reports when it fails. Roll out in testing mode first (which reports but does not block) before switching to enforce.

How to check MTA-STS

MTA-STS has two components, so a complete check looks at both the DNS record and the policy file.

  1. 1

    Check the DNS record

    Query the _mta-sts subdomain:

    $ dig TXT _mta-sts.example.com +short
  2. 2

    Fetch the policy file

    Retrieve the policy over HTTPS from the fixed well-known path:

    $ curl https://mta-sts.example.com/.well-known/mta-sts.txt
  3. 3

    Verify the mode and MX

    The policy must list your real mx hosts and a mode. enforce blocks non-TLS delivery; testing only reports. The checker above validates both parts together.

MTA-STS record example

Host_mta-sts.example.com
v=STSv1; id=20261107T000000Z

The MTA-STS DNS record. The policy file it signals (at /.well-known/mta-sts.txt) contains: version STSv1, mode: enforce, the mx hosts, and max_age.

MTA-STS tag reference

The DNS record has two tags; the policy file has its own fields.

Tag Type Meaning
v Required (DNS) Version. Must be STSv1.
id Required (DNS) A unique policy ID; change it whenever you update the policy file so senders refresh.
mode Required (policy) enforce (block non-TLS), testing (report only), or none.
mx Required (policy) Your authorized mail server hostnames.
max_age Required (policy) How long (seconds) senders should cache the policy.

How to read your MTA-STS result

Common MTA-STS results.

Result What it means & what to do
DNS record missingPublish the _mta-sts TXT record and the policy file together — both are required.
DNS record present but policy file 404sSenders cannot apply the policy. Host mta-sts.txt at the exact .well-known path over valid HTTPS.
mode: testingYou are reporting but not enforcing. Move to enforce once TLS-RPT shows no legitimate failures.
mx list is wrongDelivery can break. The policy mx entries must match your real MX records.

Frequently asked questions

What is MTA-STS?

MTA-STS (Mail Transfer Agent Strict Transport Security) is a standard that requires other mail servers to deliver email to you over a valid TLS connection, preventing downgrade and interception attacks. It uses a DNS record plus a hosted policy file.

How do I check my MTA-STS setup?

Check two things: the DNS record (dig TXT _mta-sts.yourdomain.com +short) and the policy file (https://mta-sts.yourdomain.com/.well-known/mta-sts.txt). Both must be present and valid — the checker above does both.

What is the difference between enforce and testing mode?

testing mode reports TLS problems (via TLS-RPT) without blocking delivery; enforce mode refuses non-TLS delivery. Start in testing, confirm no legitimate mail fails, then switch to enforce.

Do I need both MTA-STS and TLS-RPT?

They complement each other. MTA-STS enforces encrypted delivery; TLS-RPT gives you daily reports of failures. Deploy both so you can move to enforcement safely and keep visibility.

MTA-STS is defined in IETF RFC 8461.

Reviewed by the Skysnag Security Team. Last updated .

Add this free MTA-STS checker to your site

Copy this snippet to embed the live checker on your own website, docs, or client portal. It runs the real-time lookup and links back here for the full report.

<iframe src="https://www.skysnag.com/?scb_widget=mtasts" title="Free MTA-STS Checker by Skysnag" style="width:100%;max-width:560px;height:320px;border:0" loading="lazy"></iframe>
Live preview