Topic · Transport Security

MTA-STS MX pattern

An MTA-STS mx line lists acceptable mail exchanger hostnames or supported wildcard patterns for a protected domain.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

A sender compares discovered MX names against allowed patterns while validating transport encryption.

02 / What can go wrong

What can go wrong

A new MX not listed in policy can cause enforced delivery failures during a provider migration.

03 / What to check or do

What to check or do

Compare live MX records with the HTTPS policy file before every mail infrastructure cutover.

Practical scenario

Practical scenario

An organization switches inbound filtering vendors and updates MX records immediately. Its existing MTA-STS enforce policy still lists only the old vendor, causing compliant senders to defer delivery to the new MX.

Verification checklist

  1. Resolve the live MX targets from public DNS.
  2. Fetch the exact HTTPS MTA-STS policy and enumerate its mx lines.
  3. Validate each new MX TLS name and certificate chain.
  4. Stage policy changes and monitor transport reports before and after cutover.
Practical diagnosis

How to investigate MTA-STS MX pattern

Signal to investigate
A policy lists only primary MX while backup MX has a distinct hostname.
Evidence to collect
List all actual MX hostnames and evaluate each against the policy's mx patterns.
Common wrong conclusion
A functioning backup server can still be excluded from a strict transport policy.
Illustrative diagnostic — substitute your authorized domain or host
dig +short MX example.com
curl -s https://mta-sts.example.com/.well-known/mta-sts.txt
Educational example; not validated against your live infrastructure.
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗