SSL check results of acorn.su

NEW You can also bulk check multiple servers.

Discover if the mail servers for acorn.su 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 Sun, 17 Aug 2025 09:13:47 +0000

We can not guarantee a secure connection to the mailservers of acorn.su!

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

/mailservers/acorn.su

Servers

Incoming Mails

These servers are responsible for incoming mails to @acorn.su 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
1 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
3 s

Outgoing Mails

We have not received any emails from a @acorn.su 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

      • E5
        • 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)
  • E5
validity period
Not valid before
2025-07-01
Not valid after
2025-09-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8F:2A:2F:FC:12:42:45:B7:A5:8D:64:5A:65:CD:9D:D1:B3:71:5A:2C:E3:E3:A6:A0:92:FA:9B:94:E6:CC:00:8E
SHA1
26:17:8F:35:FB:EF:AB:A6:45:64:DE:65:7E:21:75:4C:32:D5:FE:52
X509v3 extensions
subjectKeyIdentifier
  • 80:F3:8C:7B:E1:50:2F:35:28:CB:6A:5B:B7:A1:82:6A:F2:5B:9F:77
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/8.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jul 1 23:43:10.516 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:11:2F:88:4E:BA:6F:7F:25:BA:6F:D9:31:
  • E2:F1:C0:5A:82:B4:F4:2A:7D:F7:01:0A:1D:59:C4:91:
  • 19:FB:2A:3C:02:20:4D:50:93:3C:73:15:BE:E5:24:D6:
  • F8:CC:54:3D:AB:6D:32:5A:64:0C:42:2A:23:C9:B6:2E:
  • 5D:A5:33:39:73:75
  • 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 : Jul 1 23:43:10.605 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DD:1D:46:01:DC:35:4A:FA:63:AE:ED:
  • E6:5E:94:F0:0E:DB:88:60:8E:3B:DB:9C:BD:22:1C:CB:
  • A0:4A:02:07:69:02:20:03:93:C4:01:F6:0E:95:34:5E:
  • 96:4E:72:31:74:0C:B4:10:90:E8:E9:5F:4B:44:38:98:
  • 36:19:A7:E1:0A:21:38