SSL-Tools

SSL check results of sv-oberlenningen.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for sv-oberlenningen.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 Mon, 13 Apr 2026 00:30:51 +0000

The mailservers of sv-oberlenningen.de can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @sv-oberlenningen.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.worldserver.net
217.13.200.138
 10
supported
worldserver.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mx.20.worldserver.net
217.13.200.138
 20
supported
worldserver.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @sv-oberlenningen.de address so far. Test mail delivery

Certificates

First seen at:

CN=worldserver.net

Certificate chain
  • worldserver.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
    • Hostname Mismatch
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • worldserver.net
Alternative Names
  • *.worldserver.net
  • worldserver.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2026-03-28
Not valid after
2026-06-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
51:06:5F:31:AF:A7:30:3B:A0:A2:7A:1F:0D:6B:51:88:F7:8E:04:66:A0:5E:21:1C:E7:D1:77:6E:E6:99:14:D2
SHA1
A4:FA:2A:CD:AB:8D:17:E1:30:C7:0D:48:57:A9:7C:FB:97:00:D9:85
X509v3 extensions
subjectKeyIdentifier
  • BD:A4:3A:42:E6:E3:6A:49:EA:AD:A4:07:38:0E:F5:9F:20:45:76:EF
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/63.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 16:83:2D:AB:F0:A9:25:0F:0F:F0:3A:A5:45:FF:C8:BF:
  • C8:23:D0:87:4B:F6:04:29:27:F8:E7:1F:33:13:F5:FA
  • Timestamp : Mar 28 11:05:09.172 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D8:8E:2F:8F:BF:03:7E:88:C5:5E:49:
  • 79:6A:92:30:C2:18:34:2C:B9:27:05:30:1F:B9:4A:D7:
  • 90:F9:F6:9D:21:02:20:70:66:EF:F0:C5:21:65:25:4E:
  • 4B:06:4C:C0:AE:99:E3:AB:EE:8E:51:A8:C9:74:2A:8E:
  • 37:D4:9D:2B:7A:CE:23
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:69:4A:57:98:C8:99:A0:CA:88:BD:F4:8F:C0:
  • B4:56:60:CC:C3:60:0D:1F:71:F4:69:FF:C7:D1:AC:A3
  • Timestamp : Mar 28 11:05:09.284 2026 GMT
  • Extensions: 00:00:05:00:59:1A:3F:B4
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DE:29:98:15:17:61:46:1B:77:33:99:
  • 9D:F0:EE:7F:91:E5:CA:C6:AB:04:E8:56:4C:E7:02:FF:
  • C4:4F:D5:6A:11:02:20:56:FB:71:8C:6A:0E:11:CC:E5:
  • 50:0B:5D:1A:AC:07:2A:93:E2:CA:E9:38:A0:89:CD:8B:
  • 1F:32:43:0C:C8:5B:34