SSL-Tools

SSL check results of christof-krueger.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for christof-krueger.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 Wed, 24 Apr 2024 17:51:14 +0000

The mailservers of christof-krueger.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @christof-krueger.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.localhost.li
2a01:238:4294:f500:c6f4:eae6:c9d4:ca6f
 10
supported
mail.localhost.li
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.localhost.li
81.169.165.62
 10
supported
mail.localhost.li
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.localhost.li

Certificate chain
  • mail.localhost.li
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.localhost.li
Alternative Names
  • mail.localhost.li
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-15
Not valid after
2024-06-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D8:79:4A:D8:79:C5:AB:91:90:E8:6F:3B:2F:47:08:2E:CF:44:09:6F:5E:0E:D8:92:E7:15:E8:C1:E8:A1:33:69
SHA1
A2:AC:B4:E8:13:E3:0B:A3:65:FC:EA:8D:31:9D:CA:BB:B6:85:B9:14
X509v3 extensions
subjectKeyIdentifier
  • 1E:AF:0E:07:1B:DA:69:8C:A8:56:1D:9F:EB:CA:E9:50:10:43:CE:C8
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 15 11:22:32.010 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BA:5C:8A:61:26:B5:AA:8C:E3:A2:EC:
  • BE:20:BC:EF:AD:B3:A1:AE:40:5A:C5:A7:D3:73:9D:D2:
  • 9D:ED:E5:2A:DA:02:21:00:9A:2A:5A:54:40:A4:43:0D:
  • D6:E0:A2:30:CC:05:90:97:0E:D4:3F:A3:AA:68:42:73:
  • 34:4E:0B:BB:15:C5:DE:34
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 15 11:22:32.057 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:03:43:FE:31:02:BA:59:7E:D5:14:55:09:
  • EF:B9:14:7A:8E:D9:D4:57:E0:EC:48:A6:0C:3A:8A:99:
  • 49:9A:B9:AD:02:20:64:1F:26:75:FB:D6:17:0E:3A:63:
  • 5F:FC:38:D6:59:4C:2A:D0:E2:04:DF:AF:E7:11:6A:70:
  • 74:9C:67:E9:D7:28