SSL-Tools

SSL check results of schakaki.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for schakaki.net 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, 22 Oct 2024 12:06:47 +0000

The mailservers of schakaki.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @schakaki.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
schakaki.net
2a03:b0c0:1:d0::1b:5001
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
schakaki.net
178.62.59.153
 10
supported
schakaki.net
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 @schakaki.net address so far. Test mail delivery

Certificates

First seen at:

CN=schakaki.net

Certificate chain
  • schakaki.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • schakaki.net
Alternative Names
  • schakaki.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-06
Not valid after
2024-12-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
30:B7:2E:97:DF:56:36:B5:D9:76:F2:67:82:27:8C:68:27:72:6C:86:C4:0F:02:5E:3B:6E:48:B7:61:BC:35:9D
SHA1
39:8A:B4:E5:9C:8F:2D:E0:16:BF:D2:68:47:6C:C3:6C:1B:C9:8B:83
X509v3 extensions
subjectKeyIdentifier
  • 09:92:43:0B:C1:84:22:C6:0C:98:D4:27:08:9A:FF:D3:74:7D:66:E9
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 7 00:35:24.226 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1F:FA:13:46:EC:3A:68:19:39:C3:BA:B4:
  • 5B:B7:57:9E:B8:05:71:2F:CC:CA:49:0A:7C:41:CB:95:
  • DE:96:6F:B5:02:21:00:AD:0D:AC:5A:FB:C3:BD:2C:51:
  • 33:9A:64:F0:F0:42:57:53:FE:9E:C9:5C:BB:34:DD:9B:
  • 25:C5:9A:E6:38:A6:8C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Sep 7 00:35:24.198 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:A0:A0:85:12:97:D5:B7:CC:EF:BF:8B:
  • 9D:28:6A:AD:03:E0:08:BF:18:4D:AA:08:A1:AD:B4:17:
  • B4:EB:86:F6:02:21:00:DC:E0:89:0D:67:D9:60:81:59:
  • A1:15:32:A5:69:5C:0F:6A:73:58:05:6D:33:94:F1:71:
  • 88:A0:11:96:B3:7B:D0