Please note that only specially configured Internet email systems should pass this test; most systems should fail it. See Mandatory TLS for why this is so.⊞Instructions/Info
For systems that are specially configured to require TLS, this is a very useful test because it is a controlled "other end" for your system to send to.
Start("TestSenderAssureTLS") by sending us an email.
See below for how and where to send the email.
Before usingyou may want to list CheckTLS.com in your list of allowed domains (whitelist us) so the report returns to you is not sent to your spam folder.
We cannot respond to Challenge-response email filters (e.g. SpamArrest, Support Sentry SpamBlock, iPermitMail) so you MUST manually allow mail from CheckTLS.com.
This passcode only works once. You can refresh this page to receive another one.
Note: Atest may take 30 minutes to complete, and you should not have more than one test in progress at any given time. may have your email system try to send the test email more than once, so having more than one test in queue can confuse it.
When you send an email to the special address listed below, Mandatory TLS is working. It does not invite your sender to use TLS and will not accept a STARTTLS command from your end. It instead tries to get your system to send the email as plain text.makes sure that
If your system is correctly setup to require TLS, it must give up trying to send the email since we will not do TLS. Your system may then queue the mail to try again later.does accept the retry to clear the message from your queue, but the second try is not part of the test.
replies to your email with its results.
The reply email looks like:
Your email server would not fall-back to insecure mode.
More information will show here when a Listener is Started.