SSL-Tools

SSL check results of hashbaby.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for hashbaby.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 Sat, 27 Jul 2024 00:30:57 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.hashbaby.de
2a03:4000:2c:500:16:4502::30
 10
supported
hashbaby.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.hashbaby.de
185.243.11.129
 10
supported
hashbaby.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
rw0b81.webhosting.systems
185.243.11.129
Results incomplete
50
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=hashbaby.de

Certificate chain
  • hashbaby.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • hashbaby.de
Alternative Names
  • *.hashbaby.de
  • hashbaby.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-06-13
Not valid after
2024-09-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6F:1C:B2:70:1B:FA:7F:31:90:60:6C:0C:72:84:21:48:B9:75:7E:0C:D0:E1:51:4D:5C:70:94:48:8F:66:0E:CE
SHA1
57:21:6C:3B:BA:42:11:7C:AC:81:54:F0:DA:63:37:DE:0D:84:F9:BB
X509v3 extensions
subjectKeyIdentifier
  • D8:B0:AF:29:0C:F3:AB:B7:EB:73:64:79:A8:BE:E3:C0:0D:EE:E6:BC
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.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 : Jun 13 23:23:43.128 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:13:F0:2F:AF:83:0A:0D:21:93:82:FF:1A:
  • 87:E1:48:59:4B:5F:5B:6D:7A:A8:2F:A6:6B:23:52:A0:
  • 10:FB:7C:CD:02:20:31:68:71:26:1D:57:3A:61:02:7E:
  • 13:ED:AF:5D:0B:22:C6:1E:61:F7:80:6E:2B:C8:ED:A2:
  • C7:4D:56:00:59:62
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Jun 13 23:23:43.329 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:56:71:2B:57:61:47:66:29:22:EB:71:86:
  • AB:82:E1:3C:6A:5F:C0:50:61:E2:22:40:29:2B:B8:A0:
  • 88:EF:5A:2C:02:21:00:8D:41:11:B0:0D:2C:25:5D:79:
  • 28:71:97:B0:FB:C3:28:9C:EC:8B:14:67:0B:FF:99:6C:
  • 72:C9:FE:AB:A2:55:4F