SSL check results of binarymail.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for binarymail.de can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

Report created Fri, 07 Dec 2018 00:05:46 +0000

The mailservers of binarymail.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @binarymail.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
binarymail.de
2a03:4000:6:e0d2::1
10
supported
binarymail.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
binarymail.de
188.68.52.54
10
supported
binarymail.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @binarymail.de sender addresses. Test mail delivery

Host TLS Version & Cipher
binarymail.de (188.68.52.54)
Insecure - not encrypted!

Certificates

First seen at:

CN=binarymail.de

Certificate chain
Subject
Common Name (CN)
  • binarymail.de
Alternative Names
  • binarymail.de
  • dk5ra.de
  • imap.binarymail.de
  • mail.binarymail.de
  • seafile.binarymail.de
  • smtp.binarymail.de
  • www.binarymail.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2018-12-06
Not valid after
2019-03-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EB:66:44:F7:21:BB:42:0E:05:D1:F3:DF:7E:7A:44:8D:61:FC:8C:17:FB:39:7B:73:25:68:88:B3:F9:68:31:E1
SHA1
9A:E2:E8:54:AD:C8:59:18:EA:AF:BC:E3:D3:86:9D:14:88:1F:61:3E
X509v3 extensions
subjectKeyIdentifier
  • 08:6E:B6:DD:35:DD:A2:38:2A:A1:71:49:73:13:02:E2:2D:AC:F3:05
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
  • C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
  • Timestamp : Dec 6 18:25:01.337 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D2:FC:FD:5D:8D:AB:D5:C3:64:24:B0:
  • 2A:6C:41:BB:DC:33:B5:DD:9D:A3:51:AA:6C:BA:50:79:
  • B1:B9:D4:87:48:02:21:00:FF:3F:83:06:A2:DE:3D:57:
  • 8F:54:EA:B2:68:50:E4:DB:6D:AA:CF:56:13:97:79:B4:
  • 20:FD:B1:B8:1F:A1:E6:3A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 63:F2:DB:CD:E8:3B:CC:2C:CF:0B:72:84:27:57:6B:33:
  • A4:8D:61:77:8F:BD:75:A6:38:B1:C7:68:54:4B:D8:8D
  • Timestamp : Dec 6 18:25:01.006 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9E:F6:AF:8E:07:0C:77:EF:4C:54:7C:
  • CD:51:96:91:43:C8:4C:38:61:0A:2B:23:FE:6E:34:EA:
  • F8:EE:4A:EA:F9:02:20:32:09:E5:D8:32:6C:11:5A:82:
  • 91:5B:76:62:8A:30:15:A5:03:47:8A:C9:53:4C:80:85:
  • 01:C1:3A:01:36:B8:29