SSL check results of rocrou.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for rocrou.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

Report created Fri, 05 Sep 2025 08:49:49 +0000

The mailservers of rocrou.eu can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mythiccloud.net
2a12:de40:21:8099::
5
supported
*.mythiccloud.net
DANE
errors
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s
mail.mythiccloud.net
88.151.194.140
5
supported
*.mythiccloud.net
DANE
errors
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.mythiccloud.net

Certificate chain
  • *.mythiccloud.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • *.mythiccloud.net
Alternative Names
  • *.mythiccloud.net
  • mythiccloud.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-08-05
Not valid after
2025-11-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
29:E7:74:A6:38:B8:97:16:0B:81:06:C3:36:00:B6:28:D3:C3:C7:47:CF:D3:CD:CB:58:E1:7F:62:E9:9F:DA:50
SHA1
F2:16:D2:7F:AF:5A:FD:E9:46:B2:7E:C3:8E:84:86:7A:DC:B9:70:32
X509v3 extensions
subjectKeyIdentifier
  • 77:52:91:A9:F8:D7:BC:78:E4:D7:42:57:9F:8B:30:8C:05:00:1F:67
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/23.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Aug 5 18:56:59.170 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C7:C0:C6:4A:E7:D2:93:A0:35:D3:FD:
  • 41:CB:F5:8A:8A:B6:A1:2E:91:6B:1F:94:19:93:65:57:
  • 57:54:28:8E:45:02:20:1C:8D:F7:31:D0:89:0A:30:B5:
  • E7:05:35:0E:50:A7:0C:6C:5A:60:B1:71:BD:CC:E4:00:
  • B2:1B:23:DE:30:92:FE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Aug 5 18:57:01.169 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4E:7F:C3:D7:D8:4B:0B:05:66:90:A4:94:
  • 8D:02:93:BC:57:97:F4:D7:3C:BB:8E:EF:EC:B0:CC:79:
  • 90:C1:8D:BC:02:21:00:A8:B7:1A:AA:AC:7A:47:65:31:
  • E8:F4:97:B5:DB:1F:80:1F:0B:19:C8:2B:A6:A0:9D:95:
  • 9C:FF:91:DE:1F:6E:6B

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.mythiccloud.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid