SSL-Tools

SSL check results of simonwunderlich.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for simonwunderlich.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, 20 Jan 2025 13:14:57 +0000

The mailservers of simonwunderlich.de can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.simonwunderlich.de
2a01:4f8:c17:e8c0::1
 10
supported
simonwunderlich.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.simonwunderlich.de
23.88.38.48
 10
supported
simonwunderlich.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=simonwunderlich.de

Certificate chain
  • simonwunderlich.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • simonwunderlich.de
Alternative Names
  • mail.simonwunderlich.de
  • simonwunderlich.de
  • www.simonwunderlich.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-20
Not valid after
2025-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
BC:22:EA:7A:71:CB:1C:76:F9:17:2A:B1:07:34:0D:E0:94:43:17:7A:99:7B:DE:78:82:F5:95:1D:9E:8A:50:A2
SHA1
A9:F3:C3:CF:E7:EB:54:F4:E8:49:92:96:BB:B8:BA:5A:31:7B:0D:8A
X509v3 extensions
subjectKeyIdentifier
  • 2F:A1:5C:06:54:7C:95:96:FE:60:10:79:6D:4E:61:B1:27:98:BA:D6
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Jan 20 13:10:10.907 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DE:53:5D:16:A9:6D:70:A4:D3:A9:0B:
  • 72:0B:AC:97:0E:CD:ED:16:39:3F:DC:11:2D:B5:D8:A9:
  • 38:96:2A:93:8B:02:20:7B:95:44:22:F4:E3:56:74:08:
  • 59:34:26:68:DE:7E:33:13:93:1A:9D:B7:7B:F0:03:B4:
  • CD:5A:D0:90:55:1D:75
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DE:85:81:D7:50:24:7C:6B:CD:CB:AF:56:37:C5:E7:81:
  • C6:4C:E4:6E:D6:17:63:9F:8F:34:A7:26:C9:E2:BD:37
  • Timestamp : Jan 20 13:10:10.906 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3A:D7:9B:97:89:62:46:18:7F:4F:3D:B2:
  • 0F:97:C1:E0:CA:ED:E7:2E:34:FB:E4:0F:CB:FE:39:62:
  • 03:B3:4D:80:02:20:02:1E:89:71:16:BE:22:FF:90:AC:
  • F9:5A:DC:47:2E:F6:94:29:3C:FD:DF:13:D6:53:7D:54:
  • 40:34:48:A4:CC:A1