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, 19 Aug 2025 06:37:19 +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
81.169.137.219
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

      • R11
        • 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)
  • R11
validity period
Not valid before
2025-08-19
Not valid after
2025-11-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CE:39:BA:4A:A1:C3:FA:77:12:81:7F:EF:15:10:62:E3:CA:02:33:C4:CA:2F:5F:46:AF:39:DA:A9:5C:E6:DD:67
SHA1
91:06:16:FA:03:8B:78:5F:E0:94:CB:31:06:A8:54:04:8F:B5:A0:E7
X509v3 extensions
subjectKeyIdentifier
  • 24:1C:A6:8A:11:07:75:CC:70:65:3D:E2:0A:08:91:D5:9D:F4:5F:4A
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/30.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Aug 19 06:36:01.581 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6A:03:57:75:07:B6:F8:47:F7:3C:26:91:
  • 68:98:D6:E0:FF:78:E8:1B:B6:35:EF:89:C2:69:D5:B2:
  • 9E:36:80:0C:02:21:00:F7:D3:27:C1:C7:58:91:6A:AC:
  • 56:E3:7F:C5:00:5B:65:80:B7:2B:70:4E:40:B1:5B:07:
  • A4:36:FA:AD:21:B9:E3
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Aug 19 06:36:07.582 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EE:91:96:9C:8C:C1:D4:09:8E:E1:DF:
  • 35:A3:B4:11:56:7E:97:5D:31:2C:40:FC:F1:90:C8:A1:
  • ED:64:92:E9:22:02:21:00:8B:BE:45:99:C7:46:D6:9E:
  • 1B:3D:8E:D6:75:E2:6A:EF:5F:90:79:D7:E4:52:CC:6D:
  • BC:E1:F0:7B:15:E6:2A:8B