SSL-Tools

SSL check results of rick-media.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rick-media.de 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 Thu, 28 Mar 2024 08:17:14 +0000

The mailservers of rick-media.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rick-media.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
strawberry.skylabs.eu
2001:8d8:1800:8682::1
 10
supported
strawberry.skylabs.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
strawberry.skylabs.eu
212.227.75.28
 10
supported
strawberry.skylabs.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @rick-media.de address so far. Test mail delivery

Certificates

First seen at:

CN=strawberry.skylabs.eu

Certificate chain
  • strawberry.skylabs.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • strawberry.skylabs.eu
Alternative Names
  • strawberry.skylabs.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-27
Not valid after
2024-06-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A5:BF:82:96:CF:7F:87:74:DC:09:BC:3F:46:99:DA:56:CD:B5:B9:A8:3E:FC:B9:CB:60:6B:62:B5:06:F6:74:38
SHA1
C4:65:56:CF:54:CE:F5:1F:C9:25:E6:27:A4:EA:EC:57:CD:BC:35:8E
X509v3 extensions
subjectKeyIdentifier
  • AB:CA:57:E8:66:D5:65:55:20:BC:05:F8:0B:C5:D9:A2:C1:03:CC:90
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 : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 28 00:57:12.380 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8B:37:4E:6D:CA:E6:04:75:24:16:78:
  • 6D:55:AA:25:66:87:25:BB:DA:56:EF:F1:D3:68:E0:A0:
  • D5:02:CD:AA:F8:02:21:00:B5:AC:8B:B8:8D:BC:84:A1:
  • EF:AD:42:83:9D:5F:4B:5F:CC:2C:41:0D:93:D5:18:77:
  • A4:93:8B:AC:69:3E:65:9B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 28 00:57:12.345 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AE:D7:57:FB:91:91:D8:13:84:FA:BE:
  • 34:80:EC:19:36:3F:A0:47:58:06:00:1F:B3:55:B2:23:
  • 36:D7:01:7F:BD:02:20:64:6B:46:15:72:49:22:D9:BC:
  • 48:53:3E:3A:32:7C:19:19:C2:00:79:BB:4E:64:ED:1A:
  • B7:4B:B3:78:EF:12:48