SSL check results of leibnitz.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for leibnitz.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 Wed, 13 Jan 2021 22:06:47 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.leibnitz.de
2a01:488:66:1000:53a9:22c1::1
50
supported
mail.leibnitz.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mail.leibnitz.de
83.169.34.193
50
supported
mail.leibnitz.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mx-in-1.synserver.de
217.119.50.244
Results incomplete
100 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx-in-1.synserver.de
217.119.50.249
Results incomplete
100 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx-in-2.synserver.de
217.119.50.249
Results incomplete
100 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx-in-2.synserver.de
217.119.50.244
Results incomplete
100 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

We have not received any emails from a @leibnitz.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.leibnitz.de

Certificate chain
Subject
Common Name (CN)
  • mail.leibnitz.de
Alternative Names
  • mail.leibnitz.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-11-29
Not valid after
2021-02-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FD:A7:17:72:74:42:B7:56:C0:6B:76:90:3E:A7:99:4C:4A:14:17:72:63:90:CC:17:18:51:B7:8A:23:13:5D:58
SHA1
57:65:85:4F:4E:30:D8:9D:DA:B0:4D:74:74:9C:16:12:F1:E0:4C:08
X509v3 extensions
subjectKeyIdentifier
  • 71:1A:7B:9A:12:72:80:49:2D:E7:C7:59:80:1C:9D:0E:B7:C4:56:63
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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Nov 29 12:34:59.416 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EC:9F:4F:BC:B0:6A:28:98:A4:B2:CF:
  • DE:30:AF:5A:4A:30:C9:6B:D2:B9:8E:5F:99:A1:E6:B0:
  • 6D:50:B5:52:DB:02:21:00:8F:C6:06:E6:05:EC:BF:13:
  • 12:D6:8B:86:09:CE:D4:18:0F:52:4F:77:34:FD:93:73:
  • BB:4D:70:68:A3:0F:66:E0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Nov 29 12:34:59.479 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E8:E7:8B:7D:93:36:7B:4F:DA:3A:05:
  • CB:35:F3:CB:82:ED:EA:8D:8C:98:E4:27:2B:4C:43:13:
  • 19:4C:97:37:64:02:20:09:93:C8:72:8E:C6:49:F1:07:
  • 72:C2:31:21:E6:AD:ED:42:76:F1:0D:1A:80:E1:27:9A:
  • DD:BE:30:A6:5B:0D:1F