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 Tue, 20 Jan 2026 16:21:25 +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
mail.zelx.de
2a01:238:42c6:1800:aa55:fdb:8fd8:81aa
 20
supported
zelx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.zelx.de
81.169.174.16
 20
supported
zelx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 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.137.219)
TLSv1.3 TLS_AES_256_GCM_SHA384
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
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • zelx.de
Alternative Names
  • *.zelx.de
  • zelx.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-01-20
Not valid after
2026-04-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C8:59:56:28:EA:BC:82:DB:43:D5:F9:3B:ED:80:F9:1A:74:0A:08:8A:F8:FA:EA:0D:2A:58:CC:DC:0E:2E:39:9B
SHA1
6F:DD:F0:DC:6F:2F:05:DC:AD:ED:1A:B4:6A:46:D3:47:81:2B:4E:CC
X509v3 extensions
subjectKeyIdentifier
  • 0F:DF:89:A9:FD:F5:D3:7D:C6:95:1C:EE:11:CF:2E:47:9B:29:8D:25
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/27.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Jan 20 16:13:34.894 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4D:71:C7:FB:E5:BB:DD:03:A4:A7:06:74:
  • 18:41:58:A6:57:80:44:FF:22:24:04:8C:F1:EB:75:0D:
  • 2C:B2:54:98:02:21:00:AE:24:E4:FA:D5:E6:F8:01:1C:
  • 82:AA:3B:81:F5:A6:07:DC:0D:D4:3F:98:4D:B0:94:5A:
  • 01:68:FA:C9:05:04:24
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A5:C9:78:92:5D:57:46:17:82:87:0D:D8:89:66:0B:5C:
  • 55:64:8B:7D:00:40:F2:EC:07:68:51:D1:88:69:19:F7
  • Timestamp : Jan 20 16:13:35.831 2026 GMT
  • Extensions: 00:00:05:00:2F:93:39:D7
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:91:FD:41:CE:9B:AD:D2:E8:E0:44:4B:
  • EC:1B:EA:7E:18:80:EC:8C:72:E2:36:9A:A5:0A:CD:A2:
  • E7:5A:11:64:50:02:20:38:13:DA:AE:59:C7:AC:84:B0:
  • 1E:4B:F7:4A:9D:2E:5C:A9:77:AE:26:02:01:2D:08:14:
  • 22:30:31:24:DD:1D:D5