//email/testTo:

See the //email/testTo: ("TestReceiver") Full Documentation for complete information.

Type in the email address of someone that you send email to.

Leave the Output Level set to "Detail".

Click the Run Test button.

When you click Run Test, //email/testTo: ("TestReceiver") performs all the steps that Internet email systems go through to send email. It records every command and byte of data it sends and every answer and byte of data that the other email system sends. TestReceiver never actually sends an email, it just gets as close as possible, learning as much about the remote system as it can.

Because CheckTLS focuses on security, TestReceiver tries to establish a secure (TLS) connection with the recipient's system. Along with recording everything, it looks at the security of the recipient's system for things like: certificate contents and signers, encryption algorithms, key lengths, hostname mis-matches, incorrect wild-card usage, weak cyphers, etc.

⊟What it shows

Confidence Factor

For all Output Levels, the first thing TestReceiver shows is our unique Confidence Factor. This is our "grade" (zero to 100) for the recipient's email system. It takes into account all the security information gathered while it was connected with the recipient's email system. For domains with multiple email servers (MX hosts), it weighs how many there are and their priority. It computes a single number for the given email address that is our opinion on how securely it will receive email.

We suggest that a Confidence Factor of 90 or above indicates that the email address is "secure".

MX Matrix

The next level of output is the MX Matrix. TestReceiver groups the steps of sending an email into 8 stages. The MX Matrix shows, for each MX host, how long each stage took and whether it was successful or not. Use the MX Matrix to look deeper into an email system, both down the matrix (by MX Host) and across the matrix (by stage), to show where strengths and weaknesses are in the system.

See the TestReceiver Full Documentation for more information about the MX Matrix stages.

Detail

The next levels of output are all Detail. Detail is the log of TestReceiver's interaction with the recipient's email system. Depending on the Output Level chosen it also shows what is inside the remote system's SSL Certificates and the details of the SSL connection established with the remote system.

See the TestReceiver Full Documentation for more information about what the Detail levels show.

⊞FULL Version fields

The FULL Version has these additional input fields:

Quick Test

Just do a quick "yes" or "no" test. This invalidates the Confidence Factor so should only be used in special cases. It sets IGNORENOCONNECT=on, CHECKOCSP=off, MXCOUNT=1, STOPAFTER=EHLO2, TIMEOUT=12. These can be overridden by setting them explicitly.

Ignore No Connects

Remove all MX hosts that do not allow us to connect, as if they were not in the DNS MX lookup in the first place. Used to prevent hosts that are off-line from reducing the Confidence Factor. This invalidates the Confidence Factor as we cannot know if the off-line host will have TLS if/when it comes on-line.

Show Test Progress

Show MX tests in real-time. A MX test is displayed live in the browser as it happens. All MXs are tested one after the other instead of at once, so we recommend using this option for just one specific MX.

SMTP Detail XML

For XML Output Formats only, turn this on to include the SMTP log as CDATA in the XML output. See the TestReceiver Full Documentation for more information.

MX Host

A specific MX host to test. Use this to focus on a single MX host, or when DNS does not return the right MX hosts.

MX Port

The TCP port to use to talk to the email server, almost always 25 (SMTP) but can be 465 or 587. Leave blank to use 25.

IPv4

Test IPv4 MX hosts.

IPv6

Test IPv6 MX hosts. Currently our hosting company Digital Ocean blocks this.

MX Count

Limit the number of MX Hosts to test. Can be either a number or a percent (put % after digits). Leave blank to test all MXs. MX Count limits Hosts; MX Priority limits Entries (one Entry can have multiple Hosts/Addresses)

MX Priority

Limit the number of MX Entries (in priority order) to test. Can be either a number or a percent (put % after digits). Leave blank to test all MX records.

Stop After

Stop the SMTP conversation after this step, one of (ANSWER,CONNECT,EHLO1,STARTTLS,EHLO2,MAILFROM,RCPTTO,DATA). Leave blank to run all.

Direct TLS

Start TLS immediately after connecting to server and before sending or receiving any commands or data (typically used with port 465).

Compel TLS

Try starting TLS even if server does not offer it, i.e. send a STARTTLS command even if server did not offer 250 STARTTLS.

Relax "*" match

Allow wild-card certs to match multiple levels of server name (see rfc-2818 section 3.1 paragraph 4).

Check CRL

Check if certificate is revoked on its Certificate Revocation List (CRL). Note: this can be slow.

Check OCSP

Check if certificate is revoked by its Online Certificate Status Protocol (OCSP).

SSL Version

Sets the version(s) of the SSL protocol that can be used. From the OpenSSL documentation:

'SSLv23' uses a handshake compatible with SSL2.0, SSL3.0 and TLS1.x, while 'SSLv2', 'SSLv3', 'TLSv1', 'TLSv1_1' or 'TLSv1_2' restrict handshake and protocol to the specified version. All values are case-insensitive. Instead of 'TLSv1_1' and 'TLSv1_2' one can also use 'TLSv11' and 'TLSv12'. Support for 'TLSv1_1' and 'TLSv1_2' requires recent versions of Net::SSLeay and openssl.

Independent from the handshake format you can limit to set of accepted SSL versions by adding !version separated by ':' (colon).

The CheckTLS default SSL Version is 'SSLv23' which allows any handshake version for testing purposes. CheckTLS issues a warning if the handshake negotiated is SSL2.0 and SSL3.0 which have serious security issues and should not be used anymore.

Most production systems use the default SSL Version 'SSLv23:!SSLv3:!SSLv2' which means that the handshake format is compatible to SSL2.0 and higher, but that the successful handshake is limited to TLS1.0 and higher, that is no SSL2.0 or SSL3.0 because both of these versions have serious security issues and should not be used anymore. You can also use !TLSv1_1 and !TLSv1_2 to disable TLS versions 1.1 and 1.2 while still allowing TLS version 1.0.

Setting the version instead to 'TLSv1' might break interaction with older clients, which need and SSL2.0 compatible handshake. On the other side some clients just close the connection when they receive a TLS version 1.1 request. In this case setting the version to 'SSLv23:!SSLv2:!SSLv3:!TLSv1_1:!TLSv1_2' might help.

SSL Cipher List

A list of Ciphers that can be used. From the OpenSSL documentation:

If this option is set the cipher list for the connection will be set to the given value, e.g. something like 'ALL:!LOW:!EXP:!aNULL'. Look into the OpenSSL documentation for more details.

Unless you fail to contact your peer because of no shared ciphers it is recommended to leave this option at the default setting. The default setting prefers ciphers with forward secrecy, disables anonymous authentication and disables known insecure ciphers like MD5, DES etc. This gives a grade A result at the tests of SSL Labs. To use the less secure OpenSSL builtin default (whatever this is) set SSL_cipher_list to ''.

XSL URL

This adds the specified XSL stylesheet URL to the XML output. It is up to whatever system receives the XML to apply the stylesheet. See TestReceiver XSL for more information.

XSL to Run

This applys the specified XSL to the XML. The translated XML is output in place of the original. You can enter the XSL itself or a URL from which to retrieve the XSL. See TestReceiver XSL for more information.

SMTP Auth

To help minimize unauthorized use, some email systems require authentication (i.e. login/password) to access email. The "AUTH" fields allow you to connect to these systems. SMTP Auth specifies which AUTH mechanism to use (plain, login, CRAM-MD5, NTLM)

AUTH User

The userid for authentication.

AUTH Pass

The password for authentication.

SMTP TimeOut

How long (in seconds, default 30) to wait for the SMTP server to respond to a command. Use this if you are getting time-out errors on a slow connection or while testing a slow/busy server. While this allows you to test a slow system, needing more than 30 seconds indicates a problem and regular email will frequently fail.

CA Certs

A PEM encoded Certificate or Certificate Chain of trusted Certificate Authorities to use to determine if the server's certificate is properly signed. Use Show Our CA List to see the Chain used by CheckTLS.

Client Cert

The Client Certificate to send.

Client Key

The Client Certificate Key to send.

The following options are restricted. They can only be used on systems that you directly control and that will not report CheckTLS as a threat. Improper use will harm CheckTLS.com and we will block your access and cancel your subscription without refund.

These options are not useful for testing the security of an email server. They do not affect the Confidence Factor and have no bearing on the security of emails.

RCPT TO

Send an SMTP "RCPT TO" command.

Note that this option can be seen as a "sender callout" (See Calllback Verification). Sender callouts are a controversial subject with strong opinions both ways. (Google "sender callout" to see various opinions.)

Send Email

Actually send a test email message.

Note that this will send one email per MX, which on a large email system could be many emails to the same address. Use either the Quick or the eMail MX Host options above to target just one MX host.