SSL-Tools

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

JSON Refresh

Report created Sat, 23 Sep 2023 20:55:03 +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:8641:7:1697::
 5
supported
mail.mythiccloud.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.mythiccloud.net
88.151.194.140
 5
supported
mail.mythiccloud.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mythiccloud.net

Certificate chain
  • mail.mythiccloud.net
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.mythiccloud.net
Alternative Names
  • mail.mythiccloud.net
  • mythiccloud.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-08-08
Not valid after
2023-11-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D0:F3:14:3B:F2:37:6D:E1:09:9C:4B:F7:8C:86:B6:E5:1A:ED:D5:33:52:2B:36:1C:C3:AF:96:24:EC:95:BB:0C
SHA1
0A:E0:41:76:D0:43:56:53:53:F8:15:A9:DC:7E:B3:66:A6:C5:3C:B2
X509v3 extensions
subjectKeyIdentifier
  • 8F:91:5A:79:58:16:DD:30:1D:FE:A9:5A:D0:A4:47:0B:1D:06:C2:48
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Aug 8 14:54:51.183 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:DB:12:4B:E1:DB:2B:21:73:D1:29:A3:
  • A1:54:C4:A9:61:17:F1:80:2E:54:23:BC:9D:E6:EB:BC:
  • 2E:DB:B1:59:22:02:21:00:85:F2:E8:94:58:0C:7D:12:
  • 6A:10:5C:F1:FF:A2:FA:D2:FA:50:B7:50:03:D8:4B:80:
  • 11:BD:91:D6:5A:49:5D:B8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Aug 8 14:54:51.206 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0C:11:3F:FB:02:F4:16:81:AF:96:2F:47:
  • D5:AA:21:37:46:C5:A9:21:A9:71:1C:39:A4:B0:56:D6:
  • 7E:BE:EE:F5:02:21:00:A7:FA:8D:9E:9B:EB:D0:D4:12:
  • 16:EC:81:58:81:6D:36:C9:54:14:81:FA:E5:4F:59:EF:
  • 31:2E:B7:59:6F:48:49

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 full certificate
  • SHA-256 Hash
valid
—
_25._tcp.mail.mythiccloud.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid