SSL-Tools

SSL check results of hahncastell.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for hahncastell.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 Thu, 25 Nov 2021 10:55:22 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
gary.hahncastell.de
78.46.228.10
 10
supported
mail.hahncastell.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.hahncastell.de

Certificate chain
  • mail.hahncastell.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)
  • mail.hahncastell.de
Alternative Names
  • cloud.hahncastell.de
  • fahrdienst-rothe.de
  • gary.hahncastell.de
  • lab.fahrdienst-rothe.de
  • mail.hahncastell.de
  • mail.victor-hahn.de
  • password.hahncastell.de
  • password.victor-hahn.de
  • woelkchen.hahncastell.de
  • www.fahrdienst-rothe.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-11-22
Not valid after
2022-02-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
54:BE:88:63:BE:72:56:28:C6:FE:30:94:79:DD:CE:C8:B7:1B:AA:9B:1E:58:95:8F:10:CC:2D:C2:17:04:3B:89
SHA1
82:50:50:67:FA:5B:64:85:21:D2:46:3E:BA:61:3E:CE:90:87:DC:79
X509v3 extensions
subjectKeyIdentifier
  • 16:B5:FC:F9:25:70:42:05:3B:EF:49:4A:9E:05:36:B6:30:BE:56:43
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Nov 22 14:42:14.072 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A9:FE:A9:11:32:A9:6C:7D:35:C7:AE:
  • C4:B6:3F:47:89:10:ED:BB:3E:D4:30:54:60:1F:87:55:
  • BF:B6:B1:E5:B4:02:21:00:E0:2C:4A:9D:3A:F5:EF:31:
  • AF:91:91:2A:D7:3F:19:B3:E8:3E:06:60:29:28:0F:79:
  • 35:B4:3F:5D:11:30:98:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Nov 22 14:42:14.546 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7E:BD:A9:E4:4D:B0:D8:E0:F7:E0:71:9A:
  • 90:37:D0:BD:B6:48:7A:0F:D5:37:13:84:10:0E:AC:C7:
  • 2C:94:C2:E9:02:21:00:F5:1A:56:D5:BF:4E:57:21:01:
  • 8A:DF:41:7F:B5:65:5C:0F:D9:30:94:7F:A5:4A:94:26:
  • A3:9F:69:4D:56:3D:D4