SSL-Tools

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

JSON Refresh

Report created Thu, 01 Oct 2020 19:36:11 +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-08-21
Not valid after
2020-11-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FC:53:05:14:5C:11:80:E6:0E:FB:F6:9B:43:25:E5:12:DA:EE:35:BA:7E:96:2E:A6:67:E2:E6:BA:97:67:F4:CB
SHA1
60:E6:EB:A9:AB:55:B9:39:EB:EE:F3:B9:CB:71:A8:46:F0:48:9E:0D
X509v3 extensions
subjectKeyIdentifier
  • 18:40:22:33:97:AB:36:02:12:19:DF:C7:B0:B7:4B:A2:1D:EE:0E:7B
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 : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
  • 7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
  • Timestamp : Aug 21 13:33:23.531 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BA:40:CB:FF:BD:DD:C1:F9:55:DA:C3:
  • 6A:27:5D:CD:AC:8A:45:EC:EB:CF:CD:7D:B7:9F:D2:EE:
  • 36:30:B9:B7:C0:02:21:00:80:AC:DF:59:27:2B:E0:70:
  • 41:EA:69:48:7C:8A:F9:EE:64:45:94:C8:C5:35:BA:02:
  • 66:74:1D:C3:04:67:25:03
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : Aug 21 13:33:23.610 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9F:7B:48:11:BC:33:AF:34:E6:72:67:
  • 3B:48:C2:FD:B4:75:2D:79:35:69:19:83:60:A5:9F:AA:
  • A8:A0:5C:F1:C1:02:21:00:D5:A3:03:CD:64:A1:EB:57:
  • 44:70:E2:75:FB:3C:0D:0A:98:2D:86:E7:C5:EA:98:EE:
  • 88:07:23:6B:52:41:D4:E2