Topic · Email Infrastructure
SMTP TLS certificate SNI
Server Name Indication allows a TLS client to signal the intended hostname during negotiation when supported by the service.
How it works
A TLS server may choose among configured certificates based on the supplied hostname.
What can go wrong
Probing without the right name can show a default certificate and produce misleading mismatch reports.
What to check or do
Test the same hostname and connection behavior used by real SMTP clients; document unsupported SNI conditions.
How to investigate SMTP TLS certificate SNI
- Signal to investigate
- An SMTP service presents the wrong certificate on a multi-tenant gateway.
- Evidence to collect
- Inspect the TLS ClientHello SNI value, server configuration and presented certificate for each destination hostname.
- Common wrong conclusion
- Not every SMTP client sends SNI; a service relying on SNI alone may fail some interoperable clients.
How to interpret the evidence
Shared hosting may choose certificates using SNI, but SMTP compatibility differs across servers. MTA-STS validation still requires an appropriate certificate for the MX identity.
What to change and how to verify it
Configure a safe default certificate and test with both SNI and non-SNI clients under the intended transport policies.
Put this into practice
Run a focused check, then explore protection if your domain needs it.