SSL-Tools

SSL check results of schulz.9pc.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for schulz.9pc.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, 21 Oct 2025 00:30:25 +0000

We can not guarantee a secure connection to the mailservers of schulz.9pc.de!

Please contact the operator of schulz.9pc.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/schulz.9pc.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @schulz.9pc.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
schulz.9pc.de
92.205.228.48
 -
supported
9pc.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
schulz.9pc.de
fe80::5054:e0ff:feba:aa1f
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

We have not received any emails from a @schulz.9pc.de address so far. Test mail delivery

Certificates

First seen at:

CN=9pc.de

Certificate chain
  • 9pc.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • 9pc.de
Alternative Names
  • *.9pc.de
  • 9pc.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2025-10-17
Not valid after
2026-01-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D0:46:E3:44:98:11:5D:17:DF:F7:E0:0F:BD:7F:0F:5D:94:E2:52:51:4B:AB:24:28:3E:63:17:AE:A1:44:EA:69
SHA1
14:6E:E3:C2:10:EC:CD:35:AD:80:B5:03:93:B1:65:83:9D:C1:D8:1B
X509v3 extensions
subjectKeyIdentifier
  • 79:6C:BA:34:A0:9E:16:86:3C:0B:6A:07:9B:19:30:4C:07:7E:0E:FD
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/11.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0E:57:94:BC:F3:AE:A9:3E:33:1B:2C:99:07:B3:F7:90:
  • DF:9B:C2:3D:71:32:25:DD:21:A9:25:AC:61:C5:4E:21
  • Timestamp : Oct 17 10:08:17.802 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FD:B8:42:7A:9D:99:E3:CD:2D:09:A1:
  • 24:DE:BD:9E:B6:BC:2D:D9:6F:A1:87:5D:DF:CB:01:4D:
  • 47:D6:9A:FE:78:02:21:00:D5:59:28:01:26:8B:D5:79:
  • F1:A8:C0:FE:C1:75:75:59:1F:E4:CC:BC:08:67:03:E4:
  • 7F:6A:64:68:E3:86:28:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:86:D4:C7:28:AA:6F:FE:BA:03:6F:78:2A:4D:01:91:
  • AA:CE:2D:72:31:0F:AE:CE:5D:70:41:2D:25:4C:C7:D4
  • Timestamp : Oct 17 10:08:19.822 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EB:2D:83:85:75:43:AC:E9:99:41:BC:
  • 7E:31:8C:45:68:21:54:57:A0:D4:A6:3B:B4:C9:74:7C:
  • 8C:74:57:C6:1D:02:20:2E:7D:3F:9D:0E:36:67:6F:A5:
  • 95:F9:02:5E:8B:BE:9D:C7:29:8A:DA:0A:C6:C4:D4:EF:
  • 90:6D:95:81:67:53:18