SSL-Tools

SSL check results of georg-schulz-galabau.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for georg-schulz-galabau.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, 14 Feb 2026 16:08:44 +0000

The mailservers of georg-schulz-galabau.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @georg-schulz-galabau.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.georg-schulz-galabau.de
217.92.190.38
 10
supported
mail.georg-schulz-galabau.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 received emails from these servers with @georg-schulz-galabau.de sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (217.92.190.38)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mail.georg-schulz-galabau.de

Certificate chain
  • mail.georg-schulz-galabau.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.georg-schulz-galabau.de
Alternative Names
  • mail.georg-schulz-galabau.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-01-05
Not valid after
2026-04-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A4:01:C8:0C:F0:0B:C2:ED:CD:4D:08:69:35:80:F7:B0:31:63:43:5E:7B:3E:E1:9D:DE:7F:84:FD:8F:3F:04:4E
SHA1
DD:DE:99:30:1D:A9:44:A3:C7:B1:69:91:A0:10:D8:61:98:A5:54:85
X509v3 extensions
subjectKeyIdentifier
  • 8D:92:71:AA:9F:AD:AD:A5:A0:B7:F7:31:E8:4B:2A:22:3D:BF:81:57
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/11.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 71:7E:95:F3:C2:38:8A:6D:B1:E3:84:49:3D:31:E1:5A:
  • A9:62:08:76:2D:42:00:E0:05:0C:D0:67:B5:A6:61:E2
  • Timestamp : Jan 5 15:08:30.908 2026 GMT
  • Extensions: 00:00:05:00:06:13:BA:D4
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CE:AC:9B:C2:DE:50:49:39:12:1D:A5:
  • A4:9F:30:C2:78:C7:F8:CD:41:CB:D7:45:13:5B:60:E9:
  • AE:86:7F:94:3E:02:21:00:E1:B3:0B:FA:1C:89:41:4E:
  • C8:1A:70:27:15:55:22:38:D8:58:47:EA:39:2D:98:92:
  • 0B:39:FA:1C:75:CB:42:7E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D1:6E:A9:A5:68:07:7E:66:35:A0:3F:37:A5:DD:BC:03:
  • A5:3C:41:12:14:D4:88:18:F5:E9:31:B3:23:CB:95:04
  • Timestamp : Jan 5 15:08:30.927 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F6:63:28:9D:4C:71:0A:1B:69:9F:32:
  • 67:F1:66:0E:7D:A0:BE:F9:6B:42:EE:21:3E:54:4E:E5:
  • 0F:89:6F:C6:61:02:20:51:FC:BE:7C:41:BE:7C:5E:E2:
  • E5:3D:FD:9D:CB:5B:C5:1D:45:BF:96:52:30:D6:1D:8F:
  • 94:2D:38:1E:FE:7A:11