SSL-Tools

SSL check results of yakumo.ch

NEW You can also bulk check multiple servers.

Discover if the mail servers for yakumo.ch 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 Wed, 19 Feb 2025 10:16:01 +0000

We can not guarantee a secure connection to the mailservers of yakumo.ch!

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

/mailservers/yakumo.ch

Servers

Incoming Mails

These servers are responsible for incoming mails to @yakumo.ch addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
sys6.eientei.ra.yakumo.ch
2001:8b0:1fbf:10::f00d
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s
sys6.eientei.ra.yakumo.ch
90.155.28.134
 10
supported
*.eientei.ra.yakumo.ch
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

We have not received any emails from a @yakumo.ch address so far. Test mail delivery

Certificates

First seen at:

CN=*.eientei.ra.yakumo.ch

Certificate chain
  • *.eientei.ra.yakumo.ch
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.eientei.ra.yakumo.ch
Alternative Names
  • *.eientei.ra.yakumo.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-02-19
Not valid after
2025-05-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F6:C3:45:38:E0:D2:43:C2:FC:58:35:1F:51:7B:8A:BF:24:B3:C6:26:1A:21:7E:7A:D9:46:65:4B:93:D4:BE:01
SHA1
89:6A:C2:C4:A4:61:A3:A4:BA:DA:E2:78:90:9E:DC:64:A6:1B:C4:53
X509v3 extensions
subjectKeyIdentifier
  • A8:64:40:C6:F2:83:AC:B3:F2:A5:E4:3E:2D:C0:5F:16:A3:EF:A5:04
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Feb 19 10:11:51.320 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FD:C7:97:44:F1:C7:8D:10:0E:6B:D1:
  • D1:BC:12:47:76:A4:88:2D:2D:5D:0F:5A:F6:FD:48:CF:
  • E1:33:DE:F0:3A:02:21:00:CD:3E:09:76:B2:DE:CA:5F:
  • FF:B1:C6:12:B4:BF:14:22:08:8F:97:21:ED:34:9C:90:
  • 2E:37:8C:33:97:2A:07:3B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DE:85:81:D7:50:24:7C:6B:CD:CB:AF:56:37:C5:E7:81:
  • C6:4C:E4:6E:D6:17:63:9F:8F:34:A7:26:C9:E2:BD:37
  • Timestamp : Feb 19 10:11:50.996 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:43:60:81:CE:95:34:C5:B5:FE:69:7A:C6:
  • 9D:81:0D:43:D4:1E:D9:D5:6E:3A:55:34:D7:4E:2B:94:
  • D9:FA:FE:21:02:20:78:6E:62:01:0D:42:64:89:58:58:
  • 79:1D:C5:3B:7C:BC:98:D3:14:96:37:32:CC:72:AA:3C:
  • EC:E6:A1:19:12:B4