Skip to Main Content
MTA-STS & TLS

Hosted MTA-STS, with every mail server's certificate checked daily

Hosted MTA-STS is Palisade serving your MTA-STS policy and receiving your TLS reports, so that once you enforce the policy, senders that honour MTA-STS deliver to your domain only over a verified, encrypted connection. Palisade also checks the certificate on every mail server in your MX records each day and opens a ticket when one is expired or invalid.

What Hosted MTA-STS & Mail Server Certificate Checks helps you accomplish

Encryption senders can't skip

Without MTA-STS, a sender that can't set up TLS with your mail server falls back to plaintext, and an attacker in the path can force that. An enforced policy tells senders that honour it to refuse instead.

Evidence before you enforce

TLS reports from Google, Microsoft and the other senders that deliver to you show how many sessions were encrypted and why the rest failed, so switching to Enforce is a decision you can check.

A bad certificate becomes a ticket

An expired or invalid certificate on one of your mail servers shows up as a ticket naming the host, instead of as bounces from the senders that enforce encryption.

Trusted by leading brands worldwide

Partner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner Logo
How it works

From a hosted policy to verified delivery

Two CNAMEs and one TXT record host the policy and collect the reports. The certificate check needs none of them.

1

Delegate the policy

Publish two CNAMEs, for mta-sts and _mta-sts, and Palisade serves the policy file and the record that announces it. Add the TLS reporting TXT record at _smtp._tls. Smart DNS Deployment can publish all three for you.

2

Start in Testing

In Testing mode senders still deliver when TLS fails, but they report every session. Reports reach the TLS Reports page within 24 to 48 hours: sessions, success rate, and why each failure happened.

3

Enforce when it's clean

Once the success rate holds at or near 100% for a week or more, switch the policy to Enforce. Senders that honour MTA-STS then refuse to deliver over a connection they can't verify.

4

Certificates checked daily

Palisade connects to each mail server in your MX records over STARTTLS and checks the certificate it presents. An expired or invalid one opens a ticket naming the host; a later passing check closes it.

At a glance

Hosted MTA-STS and certificate checks at a glance

What Palisade hostsThe MTA-STS policy file at mta-sts.<your domain> and the _mta-sts record that announces it, both by CNAME delegation. Palisade also gives you the TLS reporting TXT record for _smtp._tls.<your domain> and receives the reports it points to.
Policy modesTesting (report only), Enforce, or None.
Policy max age1 day, 1 week, 30 days or 1 year.
Mail servers in the policyFilled from your MX records, and refreshed when Palisade's monitoring sees them change.
TLS reportsDaily reports from the senders that deliver to you, shown as sessions, success rate, failures by reason and one row per reporter, for any range in the last 61 days.
Certificate checksEvery day, on every mail server in your MX records, over STARTTLS on port 25.
What a check verifiesExpiry, a chain to a public root, self-signed certificates, and whether the certificate names the host.
What opens a ticketAn expired or invalid certificate. A certificate for the wrong name counts only when your MTA-STS policy is in Enforce mode.
What never opens oneA server Palisade could not reach, one that offers no STARTTLS, or a handshake that failed. Palisade does not report a certificate it did not see.
What Palisade can't doRenew or replace a certificate. That happens at your mail host or hosting provider.
Comparison

Website certificate monitors don't see your mail servers

Most certificate monitors check the HTTPS certificate on your website. A mail server presents its certificate on port 25, after STARTTLS.

DimensionWebsite certificate monitorsPalisade
What gets checkedThe certificate your website serves over HTTPS on port 443.The certificate each mail server presents over STARTTLS on port 25.
Which hostsThe hostnames you enter.Every host in your MX records, read again on each check, so a new mail host is covered without setup.
A certificate for another nameAn error, because browsers reject it.A ticket only when your MTA-STS policy enforces, because only then does a sender refuse delivery. Shared mail platforms often serve one certificate for many customers.
What happens nextAn alert.A ticket on the domain, beside its MTA-STS policy and TLS reports, that closes itself when a later check passes.
What's included

What hosted MTA-STS gives you

Two CNAMEs, and a clean way out

Delegate mta-sts and _mta-sts once and Palisade serves the policy. To stop, move the policy to Testing and wait out its max age, since senders keep a cached policy that long, then turn hosting off and delete the MTA-STS and TLS reporting records at your DNS provider.

Policy MX list kept current

The policy names the servers allowed to receive your mail. Palisade fills it from your MX records and refreshes it when its monitoring sees them change, so the policy follows you when you move mail hosts.

Testing, then Enforce

Start in Testing, read the reports, and move to Enforce when delivery is clean. Max age runs from 1 day to 1 year.

TLS reports on one page

Sessions, success rate, failures grouped by reason, and a row per reporting sender such as Google and Microsoft, for any range in the last 61 days.

Daily mail-server certificate checks

Every host in your MX records is checked over STARTTLS each day for expiry, a trusted chain, self-signed certificates and the right name.

Mismatches judged against your policy

A certificate for the wrong name opens a ticket only when your policy is in Enforce mode, because that is when senders refuse delivery.

From your AI assistant, too

Over the full MCP connection, an assistant can read the policy with get_mta_sts and switch hosting on or off with enable_mta_sts and disable_mta_sts.

Proof from teams managing authentication at scale.Less manual work. More domains protected.

Read more

5.0 out of 5 on G2Trusted by over 10,000 domains

Built for MSPs: A no-brainer. Why Integris chose Palisade after evaluating the field.

Built for MSPs

A no-brainer.Why Integris chose Palisade after evaluating the field.

“We evaluated many DMARC providers before choosing Palisade. The quality of their product, the responsiveness and friendliness of their team and their rapid progress on their product roadmap made it a no-brainer for us to move forward.”

Integris

Read the case study
A glass-fronted office building with people walking towards the entrance, under a halftone texture, with the Integris wordmark across the centre.
Questions

Hosted MTA-STS & Mail Server Certificate Checks: FAQ

What is hosted MTA-STS?

Hosted MTA-STS is Palisade serving your domain's MTA-STS policy for you. You publish two CNAME records, for mta-sts and _mta-sts, and Palisade hosts the policy file and the record that announces it. Senders that honour MTA-STS then know your mail servers support TLS and, once you enforce the policy, refuse to deliver over a connection they can't verify.

Why do I need MTA-STS if my mail server already supports TLS?

Because TLS between mail servers is opportunistic by default. If the encrypted handshake fails, or an attacker in the path strips the offer, most senders fall back to plaintext and deliver anyway. An enforced MTA-STS policy tells senders to refuse instead, and TLS reports tell you whenever that happens.

Does Palisade monitor the TLS certificate on my mail servers?

Yes. Every day Palisade connects to each mail server in your MX records over STARTTLS and checks the certificate it presents for expiry, a chain to a public root, self-signed certificates and the host name. An expired or invalid certificate opens a ticket naming the host, and a later passing check closes it. Palisade cannot renew a certificate for you; that happens at your mail host or hosting provider.

Does the certificate check need hosted MTA-STS?

No. Palisade checks the certificate on the mail servers of every domain it monitors, whether or not it hosts that domain's MTA-STS policy. What a policy changes is the name check: once an MTA-STS policy is enforced, hosted by Palisade or not, a certificate for the wrong name opens a ticket too.

Why didn't Palisade flag a certificate that names a different host?

A name mismatch only stops mail when your MTA-STS policy is in Enforce mode, because only then do senders that honour MTA-STS check the name and refuse delivery. Shared mail platforms often serve one certificate for many customers, so without enforcement a mismatch breaks nothing, and Palisade does not open a ticket for it.

Should I start my MTA-STS policy in Enforce mode?

No. Start the policy in Testing, which reports failures without blocking mail, and read the TLS reports for at least a week. Switch to Enforce once the success rate is at or near 100% and every failure reason is explained.

Do I need DMARC set up before hosted MTA-STS?

Yes. Hosted MTA-STS is switched on for a domain Palisade already monitors for DMARC. Set that up first, then turn on MTA-STS from the domain's page.

Do I have to move my DNS to use hosted MTA-STS?

No. You publish two CNAME records and one TXT record at your existing DNS provider, and your registrar and nameservers stay where they are.

Which plans include hosted MTA-STS?

Hosted records, MTA-STS included, are part of the IT teams plan and up.

Make encrypted delivery to your domain the rule

Audit any domain free, no card needed. A card starts the 15-day trial.