SSL-Tools

SSL check results of tichy.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tichy.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, 22 Oct 2024 12:00:10 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.tichy.de
2a0a:51c0::6dd
 10
supported
mail.tichy.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
smtp.tichy.de
94.199.214.196
 10
supported
mail.tichy.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.tichy.de

Certificate chain
  • mail.tichy.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)
  • mail.tichy.de
Alternative Names
  • imap.tichy.de
  • mail.tichy.de
  • smtp.tichy.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-25
Not valid after
2024-12-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1C:B4:6A:6C:AE:8D:22:2B:EB:7A:FA:4F:FD:AA:E0:79:55:30:D3:93:AA:A1:71:27:81:48:CA:E9:89:2C:DF:AE
SHA1
E1:89:3D:B9:E3:D8:BE:A2:DC:3B:95:40:68:41:F9:F0:1D:7B:DE:F3
X509v3 extensions
subjectKeyIdentifier
  • 8E:69:6F:6B:B9:6B:AE:3F:46:34:AD:D8:81:42:5B:BC:E3:51:12:06
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 25 23:01:03.026 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C3:F6:6C:8F:B8:FA:F5:3C:E0:0B:F5:
  • 5D:B7:9A:B9:F3:0F:B4:8F:2C:30:FC:0A:A1:18:3B:00:
  • 87:61:D1:C1:31:02:21:00:DC:10:66:E8:94:44:52:6F:
  • 2C:10:ED:0D:0A:3F:AB:6A:71:A1:9A:9B:51:4A:1B:2D:
  • 8A:0D:5F:99:70:B5:5D:A0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Sep 25 23:01:03.059 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AD:E9:6E:8B:03:D5:36:EB:A8:7B:59:
  • E8:4E:02:D4:04:0D:EA:DD:1E:FC:6F:E8:8C:9B:3D:8F:
  • F5:93:55:12:E8:02:21:00:AB:AF:83:12:EE:F0:59:C9:
  • C1:6A:28:12:96:23:4B:ED:87:30:C0:0A:C9:45:2E:E2:
  • 50:36:80:0A:FB:D8:9B:78