SSL-Tools

SSL check results of helioscloud.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for helioscloud.eu 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 Sat, 15 Feb 2025 16:07:30 +0000

We can not guarantee a secure connection to the mailservers of helioscloud.eu!

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

/mailservers/helioscloud.eu

Servers

Incoming Mails

These servers are responsible for incoming mails to @helioscloud.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
helioscloud.eu
2a03:4000:29:1c6::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
3 s
helioscloud.eu
94.16.119.242
 10
supported
mail.helioscloud.eu
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 @helioscloud.eu address so far. Test mail delivery

Certificates

First seen at:

CN=mail.helioscloud.eu

Certificate chain
  • mail.helioscloud.eu
    • 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.helioscloud.eu
Alternative Names
  • mail.helioscloud.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-22
Not valid after
2025-04-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5A:CA:C7:04:B0:01:7B:29:BF:6C:93:C8:A1:36:D7:69:A8:2F:DC:73:40:EB:83:F6:BD:8F:C2:4D:4E:F4:CD:0A
SHA1
7E:73:68:47:C7:EF:BB:CB:B0:12:36:81:C8:9A:AC:0E:C2:F5:34:D2
X509v3 extensions
subjectKeyIdentifier
  • 06:1C:5E:9F:83:A8:CC:36:C2:76:93:48:76:B7:EC:A5:B9:E1:8D:16
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Jan 22 05:44:17.703 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:36:56:8C:4B:49:E1:B6:EE:EF:B5:43:BA:
  • 62:C0:A2:77:08:89:AF:30:3A:41:AD:55:0E:FD:04:BF:
  • AE:95:2F:D3:02:21:00:C6:95:B6:92:24:7F:F2:09:72:
  • 45:25:E2:06:38:93:21:FF:E9:07:25:81:8F:A9:16:49:
  • 1C:82:1A:F4:BD:1F:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 22 05:44:17.710 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:20:A8:11:78:E4:A6:96:01:A1:BD:9A:47:
  • E5:F1:79:7A:5F:4E:18:6D:98:EC:AD:23:4E:C1:D6:BF:
  • 1A:2B:D3:0E:02:20:1E:96:21:9E:6A:85:9B:CC:0A:12:
  • 2A:A7:D8:9A:BD:75:FD:44:BE:43:FC:3C:FF:A7:FC:54:
  • AD:C3:2A:5B:64:1B