SSL-Tools

SSL check results of samprex.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for samprex.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 Sun, 15 Jun 2025 00:32:01 +0000

We can not guarantee a secure connection to the mailservers of samprex.de!

Please contact the operator of samprex.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/samprex.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @samprex.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.worldserver.net
217.13.200.138
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 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
2 s

Outgoing Mails

We have not received any emails from a @samprex.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
      • E5
        • 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)
  • E5
validity period
Not valid before
2025-05-09
Not valid after
2025-08-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6D:4B:0A:2A:98:38:DC:E1:A7:AF:21:2E:C7:42:09:84:AA:37:5D:E8:A9:AF:83:61:62:8E:20:A3:F6:CE:F9:C8
SHA1
91:A6:60:11:57:38:8E:01:9C:13:68:57:32:0C:B0:9E:AA:92:47:F2
X509v3 extensions
subjectKeyIdentifier
  • 4B:24:96:E1:CC:C5:47:10:CD:CD:47:9F:DE:79:F6:37:08:14:37:C4
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/43.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : May 9 10:15:56.273 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:66:83:17:F1:E2:DC:C7:9E:1D:43:8D:B0:
  • 6C:99:95:64:FE:D5:82:53:30:75:65:58:4E:E6:1F:F8:
  • 5B:DB:02:83:02:21:00:DA:44:A0:68:D4:F4:B0:F2:99:
  • 35:96:C4:58:E3:56:C4:B0:FE:12:52:A2:A5:F4:57:92:
  • FE:11:01:B0:5E:60:43
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : May 9 10:15:57.095 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FE:83:C2:4D:62:6C:1B:D0:EC:27:C2:
  • D8:4E:29:68:0A:63:2B:E8:23:C8:C6:C4:20:08:4A:86:
  • A7:FE:9A:BE:EC:02:20:59:22:7E:8D:0E:8B:6C:D6:A9:
  • 30:66:60:F4:AD:AB:72:97:BD:53:7F:36:C0:23:87:F8:
  • EC:9F:0F:C4:09:DA:6F