SSL check results of harperscheidt.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for harperscheidt.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 Sat, 03 Oct 2026 15:34:54 +0000

The mailservers of harperscheidt.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @harperscheidt.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail01.harperscheidt.de
2a02:c207:3020:5038::1
10
supported
*.harperscheidt.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail01.harperscheidt.de
5.189.166.89
10
supported
*.harperscheidt.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 @harperscheidt.de address so far. Test mail delivery

Certificates

First seen at:

CN=*.harperscheidt.de

Certificate chain
  • *.harperscheidt.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384

          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384

              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384

Subject
Common Name (CN)
  • *.harperscheidt.de
Alternative Names
  • *.harperscheidt.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-09-07
Not valid after
2026-12-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
BC:16:7A:DD:04:FF:EE:A5:8A:72:69:64:B7:DC:9E:0F:BA:5C:56:2F:73:43:9F:12:22:91:5D:28:F2:AC:A2:76
SHA1
F0:B5:82:C5:30:1C:E4:E1:9C:FF:63:09:A8:E1:B8:0C:79:D8:7B:03
X509v3 extensions
subjectKeyIdentifier
  • 28:57:4B:3B:72:0F:8B:2C:9A:01:F9:A3:E2:D9:E4:C2:BD:71:F6:BA
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/22.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:4E:43:87:FA:EC:C1:EF:81:F3:19:24:26:A8:18:65:
  • 01:C7:D3:5F:38:02:01:3F:72:67:7D:55:37:2E:19:D8
  • Timestamp : Sep 7 10:59:21.125 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D8:C8:97:E4:F1:3F:DC:C3:00:94:D0:
  • BA:06:08:61:A5:21:B3:44:71:3B:83:28:FE:57:B0:14:
  • 0C:09:31:A4:86:02:21:00:D3:D2:F8:7B:C5:BB:89:A4:
  • CA:DD:46:B4:BB:A5:31:95:9C:AC:A1:C3:8C:33:48:C4:
  • 8C:F8:29:9F:A0:16:77:C3
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Sep 7 10:59:21.662 2026 GMT
  • Extensions: 00:00:05:00:2F:66:60:C6
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2D:3B:BF:9B:E7:59:1B:72:74:A1:00:54:
  • 3B:5B:12:7E:5C:91:29:8B:6F:F2:56:22:D5:A3:22:DA:
  • 0C:32:50:8D:02:21:00:89:21:39:F8:70:35:21:BE:CC:
  • D2:7D:4C:44:FB:02:5C:15:5C:81:7E:16:31:54:A2:F0:
  • 39:1B:94:2C:BB:69:D0