SMTP TLS & Mail Server Inspector
Check inbound mail routing and whether publicly reachable MX servers advertise STARTTLS.
Run a diagnostic
The analysis script has not loaded. If the button stays disabled, reload the page and check JavaScript or caching settings.
Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.
How to use and interpret this tool
Inspect the domain's MX hosts and available TLS-related controls, including MTA-STS and TLS reporting. When the server permits it, a network check may inspect SMTP STARTTLS on port 25.
How to read the findings
Successful STARTTLS negotiation proves only that a particular server offered TLS at the test time. MTA-STS policy discovery and certificate validation add separate assurances for supporting senders.
Limitations and next steps
Hosting providers may block port 25 or remote servers may rate-limit probes. A timeout is not proof that the target lacks TLS, and one test cannot establish end-to-end encryption for every message.
Need continuous authentication protection?
Method and limitations
Inspect MX hosts, public address records, MTA-STS and TLS reporting DNS. Optionally test STARTTLS on port 25. Public DNS checks cannot prove inbox delivery or message-level authentication.
Frequently asked questions
Is SMTP TLS guaranteed for all messages?
No. A point-in-time handshake does not prove policy enforcement or successful delivery from every sending network.
Does STARTTLS support mean email is always encrypted?
No. Delivery depends on the sending and receiving servers' negotiated behavior and policy enforcement.
Educational diagnostics, not a guarantee of deliverability or provider approval.