Batch Output Formats
Batch test output depends on the Batch TestType being run:
Receiver
Receiver: text
The results file shows the Confidence Factor for each target, one per line, for example:
100 onetest@checktls.com
100 twotest@checktls.com
Receiver: csv
The results file is a two column csv file, one target per row. Columns are the Confidence Factor and Target, for example:
100,"onetest@checktls.com"
100,"twotest@checktls.com"
Receiver: pager
The results file is a terse form of the interactive Matrix, for example:
Addr,CF,Ans,Con,HELO,TLS,Cert,Sec,From,To
onetest@checktls.com,100,100,100,100,100,100,100,100,0
twotest@checktls.com,100,100,100,100,100,100,100,100,0
Receiver: pager-html
The results file is the same as "pager" above but in an HTML table, for example:
| Addr | CF | Ans | Con | HELO | TLS | Cert | Sec | From | To |
|---|---|---|---|---|---|---|---|---|---|
| onetest@checktls.com | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 0 |
| twotest@checktls.com | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 0 |
Receiver: xml
The results file returns in XML the Confidence Factor and the target address, for example:
<CheckTLS test="BatchTestReceiver">
<Results>
<Result>
<Score>100</Score>
<Target>onetest@checktls.com</Target>
</Result>
<Result>
<Score>100</Score>
<Target>twotest@checktls.com</Target>
</Result>
</Results>
</CheckTLS>
Receiver: xml-score
The results file returns in XML the Score level results of the interactive test, for example:
<CheckTLS test="BatchTestReceiver">
<Results>
<Result>
<eMailAddress>testone@checktls.com</eMailAddress>
<ConfidenceFactor>100</ConfidenceFactor>
<MXConfidenceFactor>100</MXConfidenceFactor>
<MXCount>1</MXCount>
</Result>
<Result>
<eMailAddress>testtwo@checktls.com</eMailAddress>
<ConfidenceFactor>75</ConfidenceFactor>
<MXConfidenceFactor>100</MXConfidenceFactor>
<MXCount>1</MXCount>
</Result>
</Results>
</CheckTLS>
Receiver: xml-matrix
The results file returns in XML the Matrix level results of the interactive test, for example:
<CheckTLS test="BatchTestReceiver">
<Results>
<Result>
<eMailAddress>test@checktls.com</eMailAddress>
<ConfidenceFactor>100</ConfidenceFactor>
<Connected>100</Connected>
<Allowed>100</Allowed>
<SignedOn>100</SignedOn>
<TLSAvailable>100</TLSAvailable>
<NegotiatedTLS>100</NegotiatedTLS>
<CertOK>100</CertOK>
<SenderOK>100</SenderOK>
<ProofedAddress>100</ProofedAddress>
<MXCount>1</MXCount>
<MX exchange="www.checktls.com" preference="20">
<Connected>0.020458</Connected>
<Allowed>2.00779</Allowed>
<SignedOn>2.012302</SignedOn>
<TLSAvailable>2.017546</TLSAvailable>
<NegotiatedTLS>4.275149</NegotiatedTLS>
<CertOK>4.258508</CertOK>
<SenderOK>4.328082</SenderOK>
<ProofedAddress>4.334522</ProofedAddress>
</MX>
</Result>
</Results>
</CheckTLS>
Receiver: xml-detail
The results file returns in XML the Detail level results of the interactive test, for example:
(see just below for the full Detail from )
<CheckTLS test="BatchTestReceiver">
<eMailAddress>test@checktls.com</eMailAddress>
<ConfidenceFactor>100</ConfidenceFactor>
<Connected>100</Connected>
<Allowed>100</Allowed>
<SignedOn>100</SignedOn>
<TLSAvailable>100</TLSAvailable>
<NegotiatedTLS>100</NegotiatedTLS>
<CertOK>100</CertOK>
<SenderOK>100</SenderOK>
<ProofedAddress>100</ProofedAddress>
<MXCount>1</MXCount>
<MX exchange="www.checktls.com" preference="20">
<Connected>0.023249</Connected>
<Allowed>0.102055</Allowed>
<SignedOn>0.103797</SignedOn>
<TLSAvailable>0.105284</TLSAvailable>
<NegotiatedTLS>0.517981</NegotiatedTLS>
<CertOK>0.503749</CertOK>
<SenderOK>0.557888</SenderOK>
<ProofedAddress>0.562938</ProofedAddress>
</MX>
</CheckTLS>
Receiver: xml-certdetail
The results file returns in XML the CertDetail level results of the interactive test (similar to xml-detail above but with more info about the certificates used).
Receiver: xml-ssldetail
The results file returns in XML the SSLDetail level results of the interactive test (similar to xml-certdetail above but with details of the SSL "conversation" unencrypted).
Receiver: xml-detail with SMTP Detail XML
The results file is the output shown above but also includes the full SMTP "conversation" between the client and the server, for example:
<CheckTLS test="BatchTestReceiver">
<eMailAddress>test@checktls.com</eMailAddress>
<ConfidenceFactor>100</ConfidenceFactor>
<Connected>100</Connected>
<Allowed>100</Allowed>
<SignedOn>100</SignedOn>
<TLSAvailable>100</TLSAvailable>
<NegotiatedTLS>100</NegotiatedTLS>
<CertOK>100</CertOK>
<SenderOK>100</SenderOK>
<ProofedAddress>100</ProofedAddress>
<MXCount>1</MXCount>
<MX exchange="www.checktls.com" preference="20">
<Connected>0.023249</Connected>
<Allowed>0.102055</Allowed>
<SignedOn>0.103797</SignedOn>
<TLSAvailable>0.105284</TLSAvailable>
<NegotiatedTLS>0.517981</NegotiatedTLS>
<CertOK>0.503749</CertOK>
<SenderOK>0.557888</SenderOK>
<ProofedAddress>0.562938</ProofedAddress>
<detail>
<![CDATA[
[000.023] Connected to server
[000.102]<--220 www.checktls.com ESMTP Sendmail 8.14.4/8.14.4; Fri, 12 Nov 2010 13:46:30 -0500
[000.102] We are allowed to connect
[000.102]-->EHLO checktls.com
[000.104]<--250-www.checktls.com Hello www.checktls.com [192.168.1.165], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH DIGEST-MD5 CRAM-MD5
250-STARTTLS
250-DELIVERBY
250 HELP
[000.104] We can use this server
[000.104] TLS is an option on this server
[000.104]-->STARTTLS
[000.105]<--220 2.0.0 Ready to start TLS
[000.105] STARTTLS command works on this server
[000.505] Cipher in use: DHE-RSA-AES256-SHA
[000.505] Cert Authority: /C=US/ST=Arizona /L=Scottsdale/O=GoDaddy.com, Inc. /OU=http://certificates.godaddy.com/repository /CN=Go Daddy Secure Certification Authority /serialNumber=07969287
[000.506] Cert Owner: /O=www.checktls.com /OU=Domain Control Validated/CN=www.checktls.com
[000.506] Cert CommonName: www.checktls.com
[000.506] Cert SubjectAltName: 2/checktls.com
[000.507] Cert Hostname VERIFIED (www.checktls.com)
[000.507] Cert chain VERIFIED (0 (ok))
[000.507] Connection converted to SSL
[000.507]~~>EHLO checktls.com
[000.518]<~~250-www.checktls.com Hello www.checktls.com [192.168.1.165], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN
250-DELIVERBY
250 HELP
[000.518] TLS successfully started on this server
[000.519]~~>MAIL FROM: <test@checktls.com>
[000.558]<~~250 2.1.0 <test@checktls.com>... Sender ok
[000.558] Sender is OK
[000.558]~~>RCPT TO: <test@checktls.com>
[000.563]<~~250 2.1.5 <test@checktls.com>... Recipient ok
[000.563] Recipient OK, E-mail address proofed
[000.563]~~>QUIT
[000.569]<~~221 2.0.0 www.checktls.com closing connection
]]>
</detail>
</MX>
</CheckTLS>
Receiver: xml-certdetail and xml-ssldetail with SMTP Detail XML
These show the same parsed fields as the results above but also including the full SMTP "conversation".
ReceiverAssureTLS
ReceiverAssureTLS: text
The results file shows the Assurredness Factor for each target, one per line, for example:
0 checktls.com
100 mandatorytls.checktls.com
ReceiverAssureTLS: csv
The results file is a two column csv file, one target per row. Columns are the Assuredness Factor and Target, for example:
0,"checktls.com"
100,"mandatorytls.checktls.com"
ReceiverAssureTLS: pager
The results file is a terse form of the interactive Matrix, for example:
Addr,AF,Ans,Con,HELO,TLS,ATLS
checktls.com,0,100,100,100,100,0
mandatorytls.checktls.com,100,100,100,100,100,100
ReceiverAssureTLS: pager-html
The results file is the same as "pager" above but in an HTML table, for example:
| Addr | AF | Ans | Con | HELO | TLS | ATLS |
|---|---|---|---|---|---|---|
| checktls.com | 0 | 100 | 100 | 100 | 100 | 0 |
| mandatorytls.checktls.com | 100 | 100 | 100 | 100 | 100 | 100 |
ReceiverAssureTLS: xml
The results file shows the Assuredness Factor and the target address, for example:
<CheckTLS test="BatchTestreceiverassuretls" version="V03.07.01">
<Results format="xml">
<Result>
<Score>0</Score>
<Target>checktls.com</Target>
</Result>
<Result>
<Score>100</Score>
<Target>mandatorytls.checktls.com</Target>
</Result>
</Results>
</CheckTLS>
ReceiverAssureTLS: xml-score
The results file returns in XML the Score level results of the interactive test, for example:
<CheckTLS test="BatchTestreceiverassuretls" version="V03.07.01">
<Results format="xml-score">
<Result>
<eMailAddress>checktls.com</eMailAddress>
<AssurednessFactor>0</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
</Result>
<Result>
<eMailAddress>mandatorytls.checktls.com</eMailAddress>
<AssurednessFactor>100</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
</Result>
</Results>
</CheckTLS>
ReceiverAssureTLS: xml-matrix
The results file returns in XML the Score level results of the interactive test, for example:
<CheckTLS test="BatchTestreceiverassuretls" version="V03.07.01">
<Results format="xml-matrix">
<Result>
<eMailAddress>checktls.com</eMailAddress>
<AssurednessFactor>0</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
<Answer>100</Answer>
<Connect>100</Connect>
<HELO>100</HELO>
<TLS>100</TLS>
<AssureTLS>0</AssureTLS>
<MX exchange="mail6.checktls.com[159.89.187.50]" preference="20">
<Answer>0.012104</Answer>
<Connect>0.186976</Connect>
<HELO>0.188209</HELO>
<TLS>0.188241</TLS>
<AssureTLS>0</AssureTLS>
<MXStep name="HELO">2</MXStep>
</MX>
</Result>
<Result>
<eMailAddress>mandatorytls.checktls.com</eMailAddress>
<AssurednessFactor>100</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
<Answer>100</Answer>
<Connect>100</Connect>
<HELO>100</HELO>
<TLS>100</TLS>
<AssureTLS>100</AssureTLS>
<MX exchange="mandatorytls.checktls.com[10.132.36.231]" preference="0">
<Answer>0.091495</Answer>
<Connect>0.129975</Connect>
<HELO>0.131331</HELO>
<TLS>0.132579</TLS>
<AssureTLS>0.07711</AssureTLS>
<MXStep name="AssureTLS">10</MXStep>
</MX>
</Result>
</Results>
</CheckTLS>
ReceiverAssureTLS: xml-detail
The results file shows parsed fields from the Detail level results of the interactive test, for example:
(see just below for the full Detail from ReceiverAssureTLS)
<CheckTLS test="BatchTestreceiverassuretls" version="V03.07.01">
<Results format="xml-detail">
<Result>
<eMailAddress>checktls.com</eMailAddress>
<AssurednessFactor>0</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
<Answer>100</Answer>
<Connect>100</Connect>
<HELO>100</HELO>
<TLS>100</TLS>
<AssureTLS>0</AssureTLS>
<MX exchange="mail6.checktls.com[159.89.187.50]" preference="20">
<Answer>0.004366</Answer>
<Connect>0.234804</Connect>
<HELO>0.236594</HELO>
<TLS>0.236646</TLS>
<AssureTLS>0</AssureTLS>
<MXStep name="HELO">2</MXStep>
<SSL>
<SSLVersion></SSLVersion>
<Cipher>n/a</Cipher>
<SSLDeprecated>n/a</SSLDeprecated>
<Certs count="0">
</Certs>
</SSL>
</MX>
</Result>
<Result>
<eMailAddress>mandatorytls.checktls.com</eMailAddress>
<AssurednessFactor>100</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
<Answer>100</Answer>
<Connect>100</Connect>
<HELO>100</HELO>
<TLS>100</TLS>
<AssureTLS>100</AssureTLS>
<MX exchange="mandatorytls.checktls.com[10.132.36.231]" preference="0">
<Answer>0.034515</Answer>
<Connect>0.096095</Connect>
<HELO>0.100014</HELO>
<TLS>0.101473</TLS>
<AssureTLS>0.024042</AssureTLS>
<MXStep name="AssureTLS">10</MXStep>
<SSL>
<SSLVersion>TLSv1_2</SSLVersion>
<Cipher>ECDHE-RSA-CHACHA20-POLY1305</Cipher>
<SSLDeprecated>0</SSLDeprecated>
<Certs count="3">
</Certs>
</SSL>
</MX>
</Result>
</Results>
</CheckTLS>
ReceiverAssureTLS: xml-certdetail
The results file shows the CertDetail level results of the interactive test (similar to xml-detail above but with more info about the certificates used).
ReceiverAssureTLS: xml-ssldetail
The results file shows the SSLDetail level results of the interactive test (similar to xml-certdetail above but with details of the SSL "conversation" unencrypted).
ReceiverAssureTLS: xml-detail with SMTP Detail XML
The results file is the output shown above but also includes the full SMTP "conversation" between the client and the server, for example:
<CheckTLS test="BatchTestreceiverassuretls" version="V03.07.01">
<Results format="xml-detail">
<Result>
<eMailAddress>checktls.com</eMailAddress>
<AssurednessFactor>0</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
<Answer>100</Answer>
<Connect>100</Connect>
<HELO>100</HELO>
<TLS>100</TLS>
<AssureTLS>0</AssureTLS>
<MX exchange="mail6.checktls.com[159.89.187.50]" preference="20">
<Answer>0.004366</Answer>
<Connect>0.234804</Connect>
<HELO>0.236594</HELO>
<TLS>0.236646</TLS>
<AssureTLS>0</AssureTLS>
<MXStep name="HELO">2</MXStep>
<SSL>
<SSLVersion></SSLVersion>
<Cipher>n/a</Cipher>
<SSLDeprecated>n/a</SSLDeprecated>
<Certs count="0">
</Certs>
</SSL>
<detail><![CDATA[
[000.004] Connected to server
[000.235]<-- 220 www6.CheckTLS.com ESMTP Sendmail 8.14.7/8.14.7; Sun, 12 Aug 2018 13:41:58 -0400
[000.235] We are allowed to connect
[000.235] -->EHLO www6.CheckTLS.com
[000.237]<-- 250-www6.CheckTLS.com Hello www6.checktls.com [159.89.187.50], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5
250-STARTTLS
250-DELIVERBY
250 HELP
[000.237] We can use this server
[000.237] TLS is an option on this server
[000.237] -->MAIL FROM:<test@checktls.com>
[000.277]<-- 250 2.1.0 <test@checktls.com>... Sender ok
[000.277] Sender is OK
[000.277] It looks like we can send without TLS
[000.277] -->QUIT
[000.281]<-- 221 2.0.0 www6.CheckTLS.com closing connection
]]>
</detail>
</MX>
</Result>
<Result>
<eMailAddress>mandatorytls.checktls.com</eMailAddress>
<AssurednessFactor>100</AssurednessFactor>
<MXConfidenceFactor></MXConfidenceFactor>
<MXCount>1</MXCount>
<MXAddrCount>1</MXAddrCount>
<Answer>100</Answer>
<Connect>100</Connect>
<HELO>100</HELO>
<TLS>100</TLS>
<AssureTLS>100</AssureTLS>
<MX exchange="mandatorytls.checktls.com[10.132.36.231]" preference="0">
<Answer>0.034515</Answer>
<Connect>0.096095</Connect>
<HELO>0.100014</HELO>
<TLS>0.101473</TLS>
<AssureTLS>0.024042</AssureTLS>
<MXStep name="AssureTLS">10</MXStep>
<SSL>
<SSLVersion>TLSv1_2</SSLVersion>
<Cipher>ECDHE-RSA-CHACHA20-POLY1305</Cipher>
<SSLDeprecated>0</SSLDeprecated>
<Certs count="3">
</Certs>
</SSL>
<detail><![CDATA[
[000.002] Connected to server
[000.021]<-- 220 ts6.checktls.com ESMTP TestSender Sun, 12 Aug 2018 13:41:59 -0400
[000.022] We are allowed to connect
[000.022] -->EHLO www6.CheckTLS.com
[000.023]<-- 250-ts6.checktls.com Hello [10.132.109.248], pleased to meet you
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 HELP
[000.023] We can use this server
[000.023] TLS is an option on this server
[000.023] -->MAIL FROM:<test@checktls.com>
[000.024]<-- 500 MandatoryTLS requires STARTTLS
[000.024] -->QUIT
[000.025]<-- 221 ts6.checktls.com closing connection
[000.035] Connected to server
[000.096]<-- 220 ts6.checktls.com ESMTP TestSender Sun, 12 Aug 2018 13:41:59 -0400
[000.096] We are allowed to connect
[000.096] -->EHLO www6.CheckTLS.com
[000.100]<-- 250-ts6.checktls.com Hello [10.132.109.248], pleased to meet you
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 HELP
[000.100] We can use this server
[000.100] TLS is an option on this server
[000.100] -->STARTTLS
[000.101]<-- 220 Ready to start TLS
[000.101] STARTTLS command works on this server
[000.204] Connection converted to SSL
SSLVersion in use: TLSv1_2
Cipher in use: ECDHE-RSA-CHACHA20-POLY1305
Certificate 1 of 3 in chain: Cert VALIDATED: ok
Cert Hostname VERIFIED (mandatorytls.checktls.com = *.checktls.com | DNS:*.checktls.com | DNS:checktls.com)
cert not revoked by CRL
cert not revoked by OCSP
serialNumber=c9:fa:14:5e:b4:99:e5:d4
subject= /OU=Domain Control Validated/CN=*.checktls.com
issuer= /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
Certificate 2 of 3 in chain: Cert VALIDATED: ok
cert not revoked by CRL
cert not revoked by OCSP
serialNumber=07
subject= /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
issuer= /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2
Certificate 3 of 3 in chain: Cert VALIDATED: ok
cert not revoked by CRL
cert not revoked by OCSP
serialNumber=00
subject= /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2
issuer= /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2
[000.485] ~~>EHLO www6.CheckTLS.com
[000.496]<~~ 250-ts6.checktls.com Hello [10.132.109.248], pleased to meet you
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 HELP
[000.496] TLS successfully started on this server
[000.496] ~~>MAIL FROM:<test@checktls.com>
[000.498]<~~ 250 Ok - mail from test@checktls.com
[000.498] Sender is OK
[000.498] ~~>QUIT
[000.509]<~~ 221 ts6.checktls.com closing connection
]]>
</detail>
</MX>
</Result>
</Results>
</CheckTLS>
ReceiverAssureTLS: xml-certdetail and xml-ssldetail with SMTP Detail XML
These show the same parsed fields as the results above but also including the full SMTP "conversation".
TestThru
Thru tests report two pieces of information: a Thru Score and a set of Durations.
The Thru Score shows how secure the entire process of receiving an email and sending it back is. It can have 5 values:
| 0 | We could not send the message (so we didn't get anything back either). |
| 25 | We sent the message without TLS and we didn't get anything back. |
| 50 |
We sent the message without TLS and we received it back without TLS, or we sent the message with TLS but we didn't get anything back. |
| 75 |
We sent the message with TLS but received it back without TLS, or we sent the message without TLS but received it back with TLS. |
| 100 | We sent the message with TLS and received it back with TLS. |
You can tell which of the "or" options occurred by looking at the detail, but ultimately anything less than 100 means the email system is not doing TLS correctly.
There are three Durations:
- SendToSeconds
- How long it took for us to send the message to the remote email system. The timer starts when we first try to connect to the server and it ends when we close the connection after we finish sending the email.
- TurnAroundSeconds
- How long it took for the remote email system to process the incoming email and turn it around and start sending it back. The timer starts when we close the connection after sending the email and it ends when we first get a connection back from the remote email system.
- ReceiptFromSeconds
- How long it took for the remove email system to send the email to us. The timer starts when we get a connection from the remote email system and ends when we finish receiving the email.
TestThru: text
The results file shows the Thru Score for each target, one per line, for example:
100 CheckTLS-Reply@checktls.com
TestThru: csv
The results file is a two column csv file, one target per row. Columns are Thru Score and Target, for example:
100,"CheckTLS-Reply@checktls.com"
TestThru: pager
The results file is a terse form of the TestThru: text format (just above), for example:
Addr:CF
CheckTLS-Reply@checktls.com:100
TestThru: pager-html
The results file is the same as "pager" above but in an HTML table, for example:
| Addr | CF |
|---|---|
| CheckTLS-Reply@checktls.com | 100 |
TestThru: xml
The results file shows the Thru Score and 3 Durations for the target address, for example:
<CheckTLS test="G_99999_99999_20180813150355" version="V03.02.01">
<Results>
<Result>
<Score>100</Score>
<Target>CheckTLS-Reply@checktls.com</Target>
<SendToSeconds>2</SendToSeconds>
<TurnAroundSeconds>60</TurnAroundSeconds>
<ReceiptFromSeconds>1</ReceiptFromSeconds>
</Result>
</Results>
</CheckTLS>
TestThru: xml-detail
The results file shows the Thru Score and 3 Durations for the target address, along the transcripts for the send and the receive of the test message, for example:
<CheckTLS test="G_99999_99999_20180813153302" version="V03.02.01">
<Results>
<Result>
<Score>100</Score>
<Target>CheckTLS-Reply@checktls.com</Target>
<SendToSeconds>2</SendToSeconds>
<TurnAroundSeconds>60</TurnAroundSeconds>
<ReceiptFromSeconds>0</ReceiptFromSeconds>
<SentToTarget><![CDATA[
=== Trying mail6.checktls.com:25...
=== Connected to mail6.checktls.com.
<- 220 www6.CheckTLS.com ESMTP Sendmail 8.14.7/8.14.7; Mon, 13 Aug 2018 15:33:03 -0400
-> EHLO www6.CheckTLS.com
<- 250-www6.CheckTLS.com Hello www6.checktls.com [159.89.187.50], pleased to meet you
<- 250-ENHANCEDSTATUSCODES
<- 250-PIPELINING
<- 250-8BITMIME
<- 250-SIZE
<- 250-DSN
<- 250-ETRN
<- 250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5
<- 250-STARTTLS
<- 250-DELIVERBY
<- 250 HELP
-> STARTTLS
<- 220 2.0.0 Ready to start TLS
=== TLS started with cipher TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256
=== TLS no local certificate set
=== TLS peer DN="/OU=Domain Control Validated/CN=*.checktls.com"
~> EHLO www6.CheckTLS.com
<~ 250-www6.CheckTLS.com Hello www6.checktls.com [159.89.187.50], pleased to meet you
<~ 250-ENHANCEDSTATUSCODES
<~ 250-PIPELINING
<~ 250-8BITMIME
<~ 250-SIZE
<~ 250-DSN
<~ 250-ETRN
<~ 250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN
<~ 250-DELIVERBY
<~ 250 HELP
~> MAIL FROM:<ReturnAddress@TestThru.CheckTLS.com>
<~ 250 2.1.0 <ReturnAddress@TestThru.CheckTLS.com>... Sender ok
~> RCPT TO:<CheckTLS-Reply@checktls.com>
<~ 250 2.1.5 <CheckTLS-Reply@checktls.com>... Recipient ok
~> DATA
<~ 354 Enter mail, end with "." on a line by itself
~> From: ReturnAddress@TestThru.CheckTLS.com
~> To: CheckTLS-Reply@checktls.com
~> Date: Mon, 13 Aug 2018 15:33:02 -0400
~> Subject: CheckTLS TestThru (G_99999_99999_20180813153302_1)
~>
~> This is a test message from CheckTLS. Your email system should be configured to automatically forward it to ReplyAddress@TestThru.CheckTLS.com.
~>
~> .
<~ 250 2.0.0 w7DJX3Ud030197 Message accepted for delivery
~> QUIT
<~ 221 2.0.0 www6.CheckTLS.com closing connection
=== Connection closed with remote host.
]]></SentToTarget>
<ReceiptFromTarget><![CDATA[
<-- 220 ts6.checktls.com ESMTP TestSender Mon, 13 Aug 2018 15:34:04 -0400
--> EHLO www6.CheckTLS.com
<-- 250-ts6.checktls.com Hello www6.checktls.com [159.89.187.50], pleased to meet you
<-- 250-ENHANCEDSTATUSCODES
<-- 250-8BITMIME
<-- 250-STARTTLS
<-- 250 HELP
--> STARTTLS
<-- 220 Ready to start TLS
====tls negotiation successful (cypher: ECDHE-RSA-AES128-GCM-SHA256)
client cert:
Subject Name: /OU=Domain Control Validated/CN=*.checktls.com
Issuer Name: /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
~~> EHLO www6.CheckTLS.com
<~~ 250-ts6.checktls.com Hello www6.checktls.com [159.89.187.50], pleased to meet you
<~~ 250-ENHANCEDSTATUSCODES
<~~ 250-8BITMIME
<~~ 250 HELP
~~> MAIL From:<ReturnAddress@TestThru.CheckTLS.com>
<~~ 250 Ok - mail from ReturnAddress@TestThru.CheckTLS.com
~~> RCPT To:<ReplyAddress@TestThru.CheckTLS.com>
<~~ 250 Ok - recipient ReplyAddress@TestThru.CheckTLS.com
~~> DATA
<~~ 354 Send data. End with CRLF.CRLF
~~> Received: from www6.CheckTLS.com (www6.checktls.com [159.89.187.50])
~~> by www6.CheckTLS.com (8.14.7/8.14.7) with ESMTP id w7DJX3Ud030197
~~> (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
~~> for <CheckTLS-Reply@checktls.com>; Mon, 13 Aug 2018 15:33:04 -0400
~~> DKIM-Filter: OpenDKIM Filter v2.11.0 www6.CheckTLS.com w7DJX3Ud030197
~~> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=checktls.com;
~~> s=default; t=1534188784;
~~> bh=Wle7pvnqw+cMTEAtdv2hGTElSOBWIXhguikUiHrbbcs=;
~~> h=From:To:Date:Subject:From;
~~> b=EkLC4VPT2Wp4lu/HhvRqT6c+pQHmgksCuWt5j8+7V9wnwKazcvPtUD2Hs4AvhCunD
~~> MUumV91GpQQMJ/ajvyZGtPC984JbRZS0VcnVKAN+IgrW77vxGPOeFPJG22dP1u7VuN
~~> OWHnU6fjCIXMHpPmReQQ4Dz9FDz5R2jSAeOybjwo=
~~> Message-Id: <201808131933.w7DJX3Ud030197@www6.CheckTLS.com>
~~> From: ReturnAddress@TestThru.CheckTLS.com
~~> To: CheckTLS-Reply@checktls.com
~~> Date: Mon, 13 Aug 2018 15:33:02 -0400
~~> Subject: CheckTLS TestThru (G_99999_99999_20180813153302_1)
~~>
~~> This is a test message from CheckTLS. Your email system should be configured to automatically forward it to ReplyAddress@TestThru.CheckTLS.com.
~~>
~~> .
<~~ 250 Ok
~~> QUIT
<~~ 221 ts6.checktls.com closing connection
]]></ReceiptFromTarget>
</Result>
</Results>
</CheckTLS>