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 Sat, 17 Jul 2021 14:51:57 +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
10
supported
zelx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
17 s
zelx.de
81.169.137.219
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

      • R3
        • 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)
  • R3
validity period
Not valid before
2021-05-17
Not valid after
2021-08-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AD:97:A6:49:52:33:27:D7:E3:3D:A5:67:56:7E:05:BA:84:73:6C:ED:E3:F0:6A:F1:6C:30:CB:3C:09:5C:9B:B8
SHA1
E1:A9:5D:70:AC:9C:21:15:5B:8A:97:9F:66:DD:28:8F:CF:96:E0:96
X509v3 extensions
subjectKeyIdentifier
  • D7:EE:6F:6F:81:5D:C9:20:21:CD:15:40:AB:55:F8:FE:47:99:C2:D3
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : May 17 08:52:56.017 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:46:8D:1E:09:EB:74:9F:0B:44:EB:70:6A:
  • 4E:0A:92:09:52:2A:EE:F6:A8:CD:B2:C8:30:96:26:4A:
  • 73:92:0C:6B:02:21:00:A8:3B:77:05:76:66:43:A1:28:
  • AD:8E:7D:7F:A6:7F:20:C7:FF:FA:87:34:25:29:B6:60:
  • 7E:E3:2E:D4:D4:DD:AE
  • 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 : May 17 08:52:56.080 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9A:3B:07:CC:96:A6:A8:11:1A:02:7E:
  • 27:9E:62:58:FE:B7:A5:B1:4D:39:7E:23:8F:BE:65:5B:
  • EF:5D:83:79:19:02:21:00:9E:34:1F:0A:B5:53:83:FB:
  • 63:F2:B6:CA:6E:63:4B:2E:10:8A:ED:B0:98:03:8B:FA:
  • CE:F5:70:FD:B5:BE:AF:60