Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Email & DNS

MTA-STS setup: publish and test an HTTPS mail transport policy

Published August 2026 · 2 min read · Updated 2026-09-05

MTA-STS lets a domain publish a policy telling supporting senders to require TLS and expect specific MX hostnames after the policy has been fetched over HTTPS. It strengthens SMTP transport policy, but it depends on DNS, HTTPS hosting, valid certificates, and mail routing all remaining coordinated.

Start with stable MX and TLS

Before enforcing MTA-STS, verify the MX hosts are intentional, publicly reachable on SMTP, and present certificates valid for the names the policy will authorize. Enforcement on top of broken TLS can delay legitimate mail.

Inventory backup MX hosts too; they must be represented if senders may use them.

Publish the policy at the required HTTPS hostname

The policy is served from the standardized mta-sts hostname and path over HTTPS. It includes version, mode, allowed mx patterns, and max_age. The web certificate for the policy host must itself validate normally.

Use testing mode first so policy problems can be observed without immediate enforcement behavior.

Use the DNS TXT record to signal policy changes

The _mta-sts TXT record carries a policy id that senders can use to notice updates. Change the id when the policy meaning changes so cached senders have a reason to refetch.

DNSSEC is helpful for DNS integrity but MTA-STS is designed around its HTTPS policy fetch and certificate validation model.

Monitor before moving to enforce

Combine TLS-RPT reports, SMTP logs, and external tests to identify mismatched MX names or TLS failures. Only move to enforce when legitimate inbound routing consistently satisfies the policy.

  • Stabilize MX/TLS first.
  • Serve the policy over valid HTTPS.
  • Increment policy id on changes.
  • Test before enforce.

Next step

Configure the MTA-STS DNS record, HTTPS policy file and certificate, then test policy mode and MX coverage before relying on strict transport enforcement.

Explore DotMoose web hosting

Keep reading

Related guides.

Change email hosting without downtime: migrate mail without losing messages

Change email hosting without downtime by preparing destination mailboxes first, copying historical mail, preserving aliases and authentication, switching MX carefully, and synchronizing messages delivered during the transition.

Read the guide

BIMI readiness: what has to be in place before a brand logo can appear

Check DMARC enforcement, logo format, certificate requirements and mailbox-provider support before spending time on BIMI records that cannot be used yet.

Read the guide

TLS-RPT setup: receive reports about mail transport security failures

Publish a TLS reporting record, choose a report destination and interpret failures alongside MTA-STS or DANE so transport problems are visible.

Read the guide

More email & deliverability guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move