SSL check results of zelx.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for zelx.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 Tue, 14 Jul 2020 15:08:49 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
zelx.de
2a01:238:4348:6700:1bfb:bd3a:410c:6cb7
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
zelx.de
81.169.200.227
10
supported
zelx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
17 s
zelx.de
2a01:238:4348:6700:1bfb:bd3a:410c:6cb7
Results incomplete
20 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
zelx.de
81.169.200.227
20
supported
zelx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
17 s

Outgoing Mails

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

Host TLS Version & Cipher
server.zelx.de (81.169.200.227)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=zelx.de

Certificate chain
  • zelx.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

Subject
Common Name (CN)
  • zelx.de
Alternative Names
  • www.zelx.de
  • zelx.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-06-22
Not valid after
2020-09-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C3:CE:63:EB:08:8C:20:2C:26:AA:5B:6B:BE:BB:1E:EF:FF:C3:00:9E:05:61:9A:C7:A5:02:E4:30:90:24:75:E5
SHA1
E0:FA:75:CD:FE:83:5F:49:23:94:1D:D6:17:AE:A9:51:5E:FA:6E:0D
X509v3 extensions
subjectKeyIdentifier
  • 9B:69:36:9B:36:FC:5D:23:6D:DF:0C:69:7A:C7:4D:E6:FE:5D:FF:71
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 : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Jun 22 13:33:42.725 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E2:E7:CB:D4:4C:BB:C2:79:D8:BB:00:
  • A1:7E:24:96:7D:32:F3:28:3F:EE:F2:F1:95:34:3E:7D:
  • 0D:E6:3A:01:AD:02:20:23:67:C6:5A:BF:06:76:35:B7:
  • FF:D1:DA:14:B6:98:4B:2F:96:9F:75:82:98:81:7A:0B:
  • D9:98:B7:9B:CD:C2:BC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jun 22 13:33:42.780 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:51:53:F9:18:45:50:11:ED:35:71:BB:0A:
  • 9F:36:55:79:BC:57:9D:F3:6E:A6:84:96:A2:DB:73:6C:
  • C6:4F:A9:D8:02:20:5A:59:5B:72:33:06:B2:23:ED:17:
  • 14:41:B2:2A:CF:4C:BE:DD:87:8B:7E:83:ED:6C:83:FA:
  • 2C:E8:70:17:52:07