SSL check results of herzenswald-schmitten.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for herzenswald-schmitten.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

Report created Fri, 29 Nov 2024 22:31:49 +0000

The mailservers of herzenswald-schmitten.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @herzenswald-schmitten.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
herzenswald-schmitten.de
194.164.196.73
10
supported
herzenswald-schmitten.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=herzenswald-schmitten.de

Certificate chain
  • herzenswald-schmitten.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)
  • herzenswald-schmitten.de
Alternative Names
  • *.herzenswald-schmitten.de
  • bildungswald-schmitten.de
  • bildungswald.de
  • herzenswald-schmitten.de
  • herzenswald.de
  • www.bildungswald-schmitten.de
  • www.bildungswald.de
  • www.herzenswald.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-20
Not valid after
2025-01-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A7:22:54:FB:FF:4A:1D:CB:8B:F8:81:3F:70:4D:9D:43:F7:39:BD:06:64:68:BA:CC:CC:0A:78:6D:4F:0B:E1:21
SHA1
B1:C8:DE:F0:EA:84:EF:32:8B:54:09:2F:AD:D6:3B:7C:03:8D:BB:15
X509v3 extensions
subjectKeyIdentifier
  • 18:5C:A8:D2:A6:E0:A6:7D:8E:23:AB:02:C3:83:19:D4:AF:35:EB:82
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Oct 20 19:38:39.178 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:33:AB:82:0E:A3:AE:46:09:95:E4:D9:D6:
  • C0:F2:EB:9F:50:E4:AB:C5:70:21:97:C0:5F:A3:78:8C:
  • F6:14:E0:BC:02:20:0E:AD:46:1A:5F:A8:61:B5:2C:B0:
  • CE:4C:01:8C:F8:C7:1E:FE:22:27:AA:6C:A5:06:23:01:
  • E2:91:7C:D1:92:45
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 20 19:38:39.229 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:17:5D:8F:7B:BD:0B:37:6C:05:5F:F0:75:
  • C9:84:B3:5D:54:DA:C9:39:69:A6:FB:E1:DE:57:21:CF:
  • 95:45:F8:33:02:20:2F:9E:0B:B4:2C:67:CE:86:0F:AE:
  • BF:C1:30:DB:D5:DF:01:16:72:2B:20:BD:4C:C5:69:02:
  • 0F:24:99:83:C2:0F