SSL-Tools

SSL check results of s02.klinkhammer-server.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for s02.klinkhammer-server.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 Tue, 23 Apr 2024 12:55:13 +0000

The mailservers of s02.klinkhammer-server.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @s02.klinkhammer-server.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
s02.klinkhammer-server.de
5.44.100.205
 -
supported
s02.klinkhammer-server.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 @s02.klinkhammer-server.de address so far. Test mail delivery

Certificates

First seen at:

CN=s02.klinkhammer-server.de

Certificate chain
  • s02.klinkhammer-server.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)
  • s02.klinkhammer-server.de
Alternative Names
  • s02.klinkhammer-server.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-26
Not valid after
2024-06-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D3:12:8D:5D:D2:87:90:7E:D5:AC:F3:0A:A3:55:FF:BD:05:63:C8:3A:C8:AA:A0:E7:BD:0F:E1:2E:B4:EE:B8:B9
SHA1
13:B3:23:62:CF:0D:98:DC:58:43:E1:51:F9:0C:03:1A:87:9D:67:DF
X509v3 extensions
subjectKeyIdentifier
  • 52:9C:B7:99:BE:1C:F5:24:66:C4:74:E3:F5:E5:29:D7:8D:1F:31:76
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 26 17:57:11.288 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E3:8D:BD:2C:94:5E:7D:24:2E:86:75:
  • 3F:80:6C:62:7C:C9:43:15:37:79:6C:FC:C1:DD:1C:D0:
  • 93:F4:F2:09:86:02:21:00:B5:51:F7:12:A0:C5:4C:9D:
  • CB:00:75:04:6D:A7:DA:EB:AB:6C:D6:CD:A9:68:7D:9A:
  • 90:38:3D:31:C5:DF:63:4A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 26 17:57:13.276 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:10:2D:AC:39:D9:D5:68:C6:2D:18:FD:72:
  • 32:FD:39:51:88:EE:24:6F:18:88:2C:1B:11:AE:80:39:
  • 90:BA:0D:CD:02:20:70:15:3A:88:71:2C:24:0B:BA:3B:
  • 14:9F:FD:07:52:62:07:E2:66:1F:5D:4D:D9:2C:8F:05:
  • 5A:24:92:45:D8:12