SSL-Tools

SSL check results of haus-zauberberg.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for haus-zauberberg.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 Tue, 16 Sep 2025 17:24:24 +0000

The mailservers of haus-zauberberg.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @haus-zauberberg.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mailout.kolping.de
84.245.141.137
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail3.kolping.de
62.112.72.54
 50
supported
mail3.kolping.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail3.kolping.de

Certificate chain
  • mail3.kolping.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail3.kolping.de
Alternative Names
  • mail3.kolping.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-07-27
Not valid after
2025-10-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
66:C0:62:56:7C:1D:8D:89:67:8D:A0:A1:12:04:B3:47:57:92:C2:34:35:62:BF:58:83:64:5B:1A:D0:0D:18:81
SHA1
C6:5A:F0:BA:7D:B0:4A:8D:6F:0F:0E:2E:F3:D4:11:55:CB:18:FD:4C
X509v3 extensions
subjectKeyIdentifier
  • B0:37:83:37:ED:8E:47:3B:A4:22:EB:5A:AC:FF:D0:BE:71:DE:96:66
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/79.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jul 27 02:41:12.875 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:38:F3:A0:46:35:50:0B:DC:8F:E2:D4:44:
  • 24:5B:E1:5E:1D:5E:88:03:3C:99:68:16:FA:00:93:1C:
  • B5:BA:F0:A7:02:21:00:F2:8B:25:3C:D5:A1:78:A6:3D:
  • 5E:48:21:E0:17:E8:10:E8:79:E3:4C:06:46:BF:77:A6:
  • 86:3D:40:1A:4B:01:0C
  • 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 : Jul 27 02:41:12.889 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A9:E0:8A:DB:DC:26:11:3B:86:3D:7F:
  • 79:3C:44:3C:68:1D:02:D4:81:D7:C7:6A:A8:0A:FD:8F:
  • 52:96:79:29:93:02:21:00:A4:83:D7:AC:4E:B5:6B:48:
  • 04:D5:1B:E4:11:09:36:2A:BE:A5:D7:AB:53:7D:E6:02:
  • 66:93:D7:18:35:8B:59:27