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 Wed, 05 Feb 2025 10:59:13 +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
  • 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
      • 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
2024-12-11
Not valid after
2025-03-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
95:DE:8A:86:BC:02:29:7C:1B:DB:26:D4:7C:9D:64:0D:22:A6:75:07:04:DA:33:18:14:9F:65:55:5D:71:B4:65
SHA1
0F:D7:0C:57:26:DB:9F:D0:BE:0B:85:22:CA:A7:E3:8A:5A:E8:B4:BC
X509v3 extensions
subjectKeyIdentifier
  • E2:37:C1:35:51:1B:13:D0:67:04:9D:7A:65:5A:BD:12:EE:77:65:50
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Dec 11 21:00:30.495 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FB:DE:70:2C:55:EC:A1:09:93:DD:5B:
  • 7F:CF:11:0D:EF:2A:BC:1F:7A:BB:9C:BE:4E:68:1F:1B:
  • 1B:77:6D:BC:6C:02:21:00:FF:5A:EF:69:52:4C:A5:08:
  • 2A:AE:25:0F:E9:FB:A0:49:1A:23:CE:12:04:47:45:A5:
  • F4:90:FA:2E:62:56:15:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Dec 11 21:00:30.499 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4F:FC:EB:27:A0:2C:75:26:A9:CA:2E:B3:
  • 54:4D:A4:D7:C2:D2:E2:B5:04:E0:07:D6:AC:1E:E6:5C:
  • B0:74:30:CE:02:20:53:94:9C:2F:62:3C:FC:C4:E4:90:
  • 96:C6:54:DB:8F:CA:8B:29:2A:D2:9B:CF:F8:A4:C7:00:
  • F2:6F:A4:68:E0:8B