SSL-Tools

SSL check results of gerabad.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for gerabad.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 Mon, 31 Aug 2026 11:27:11 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.gerabad.de
2a01:4f8:2190:1fdf::2
 10
supported
mail.gerabad.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.gerabad.de
162.55.25.134
 10
supported
mail.gerabad.de
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 @gerabad.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.gerabad.de

Certificate chain
  • mail.gerabad.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE2
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.gerabad.de
Alternative Names
  • mail.gerabad.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE2
validity period
Not valid before
2026-08-25
Not valid after
2026-11-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
86:C4:0D:BB:DB:29:01:20:D0:09:26:92:E8:A2:41:8C:2E:CA:26:68:8A:DF:C2:1C:DC:4C:F8:C4:BD:9C:53:D3
SHA1
8D:5F:8E:3C:C1:8D:A9:9E:46:0B:50:91:B3:68:D2:C9:BA:31:32:48
X509v3 extensions
subjectKeyIdentifier
  • F7:1B:14:61:E7:B9:DA:41:19:0B:3E:C3:3D:B9:8C:AF:BF:05:48:71
authorityKeyIdentifier
  • keyid:B9:59:F2:8E:CF:22:F0:86:D3:37:48:FF:76:14:18:BA:82:D8:55:87
authorityInfoAccess
  • CA Issuers - URI:http://ye2.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye2.c.lencr.org/36.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : C8:A3:C4:7F:C7:B3:AD:B9:35:6B:01:3F:6A:7A:12:6D:
  • E3:3A:4E:43:A5:C6:46:F9:97:AD:39:75:99:1D:CF:9A
  • Timestamp : Aug 25 04:30:50.377 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AA:CA:FE:35:A8:EC:62:2D:9C:E4:5C:
  • ED:2C:10:24:5C:51:A0:EB:1B:5C:74:35:E3:50:AD:8B:
  • DF:04:F2:63:AE:02:21:00:F4:3A:C1:3E:13:3B:1A:E4:
  • D7:77:D8:4A:FD:58:2C:47:71:CC:1A:78:94:42:FB:D6:
  • 56:2E:38:20:B3:E7:6E:5A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Aug 25 04:30:50.992 2026 GMT
  • Extensions: 00:00:05:00:26:0A:BF:D7
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:68:AA:86:86:9D:6C:C0:2E:66:5C:91:34:
  • A0:5B:F1:9A:9C:CF:F6:BB:CC:C2:EF:B5:2F:D1:63:9F:
  • 55:37:4D:70:02:21:00:95:69:E6:F8:3D:47:37:BB:B1:
  • 1D:F7:A3:9D:2A:93:92:23:A7:DA:D8:9B:FD:F2:24:42:
  • A2:CD:15:B7:89:19:6F