SSL-Tools

SSL check results of sloashdot.ipv64.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for sloashdot.ipv64.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, 26 Aug 2025 09:54:43 +0000

We can not guarantee a secure connection to the mailservers of sloashdot.ipv64.de!

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

/mailservers/sloashdot.ipv64.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
sloashdot.ipv64.de
144.76.85.238
 -
supported
mail.schroederdennis.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s
sloashdot.ipv64.de
2a01:4f8:192:1326::bad:c0de
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 @sloashdot.ipv64.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.schroederdennis.de

Certificate chain
  • mail.schroederdennis.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.schroederdennis.de
Alternative Names
  • mail.schroederdennis.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-08-18
Not valid after
2025-11-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EB:96:8E:99:E1:51:7E:89:65:22:CC:8F:06:93:8B:08:AE:E4:36:B5:13:54:A2:CC:6D:B3:D8:FB:27:80:EA:B1
SHA1
3D:67:1C:7C:CC:B6:75:31:E6:C0:66:6C:E8:6D:75:26:26:A0:E0:DD
X509v3 extensions
subjectKeyIdentifier
  • F6:08:7D:07:07:CC:02:AA:E3:F4:4E:8A:EB:9B:86:1C:ED:B6:9A:3A
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/16.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Aug 18 07:54:44.256 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:06:A6:5B:97:09:25:7C:7A:2D:6C:AD:D1:
  • FC:76:8B:55:53:11:4C:6A:D9:73:B0:D6:E1:7E:76:3B:
  • B6:B2:9C:F6:02:20:7B:9A:1C:71:49:BE:A7:A1:DA:99:
  • 51:72:81:7F:40:0C:8B:61:89:FA:4A:80:3F:8B:6D:79:
  • BA:00:43:FC:80:AE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Aug 18 07:54:44.320 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:DF:D0:0C:BF:5B:5D:FC:C5:3D:71:DD:
  • 00:8A:89:75:D8:2E:5C:8B:6A:16:EF:DC:7A:9F:4A:B8:
  • 68:B9:4D:87:07:02:21:00:B5:BD:CE:F3:28:2E:36:71:
  • 49:DB:81:77:44:FF:F2:32:41:5F:B5:BD:6A:3B:33:DB:
  • 53:8F:53:90:28:03:BF:63