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 Thu, 02 Oct 2025 13:01:53 +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
4 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
      • R10
        • 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)
  • R10
validity period
Not valid before
2025-08-12
Not valid after
2025-11-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
20:A6:F7:CE:F2:27:47:02:BE:3D:AC:86:38:B9:AF:7A:39:02:FF:D1:21:B4:12:3C:9B:01:B4:54:8B:59:93:5B
SHA1
23:43:4E:24:6D:B8:C1:32:8E:CB:07:18:54:71:D5:C3:39:68:AA:DB
X509v3 extensions
subjectKeyIdentifier
  • E3:D3:34:6E:DD:52:1B:50:D9:27:3D:CD:9D:D8:C7:38:1F:2F:79:50
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/76.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Aug 12 20:00:13.845 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:09:93:E4:A5:AF:6E:26:86:C9:67:8F:3D:
  • B5:8D:3E:20:3A:F3:32:E8:97:E0:47:4A:D9:FC:35:95:
  • 2A:99:A2:2D:02:20:5A:1A:01:56:EE:A5:85:E8:80:06:
  • C8:0F:09:A6:26:95:BF:9D:F5:CB:AB:92:E8:72:34:B9:
  • 6A:78:D7:3D:D3:B4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Aug 12 20:00:17.861 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D1:78:5E:A2:B6:14:D0:98:9E:D6:4F:
  • 2C:15:95:4E:50:78:F3:8C:A2:00:05:0C:E9:C1:95:FA:
  • E6:49:57:EA:00:02:21:00:FD:6B:52:52:DA:97:26:6E:
  • 90:D9:41:03:4C:6A:B0:1D:80:B6:3F:4C:78:2F:DE:B3:
  • 3D:DB:1C:2C:52:EE:04:B5