SSL check results of rusticretreat.live

NEW You can also bulk check multiple servers.

Discover if the mail servers for rusticretreat.live 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 Sat, 10 May 2025 00:31:38 +0000

The mailservers of rusticretreat.live can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rusticretreat.live addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
stargazer.open-resource.org
2a03:4000:62:cd8::1
0
supported
open-resource.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
stargazer.open-resource.org
89.58.24.127
0
supported
open-resource.org
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 @rusticretreat.live address so far. Test mail delivery

Certificates

First seen at:

CN=open-resource.org

Certificate chain
  • open-resource.org
    • 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)
  • open-resource.org
Alternative Names
  • apollo.open-resource.org
  • git.open-resource.org
  • open-resource.org
  • stargazer.open-resource.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-05-02
Not valid after
2025-07-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C2:12:EF:DD:16:10:6E:3E:9A:5B:87:E3:E2:B6:77:04:F2:B6:85:83:57:8F:68:40:89:82:73:C5:7B:51:B6:B5
SHA1
CE:CA:EC:06:AA:46:E1:9E:0F:E7:1A:37:F4:4D:4E:50:16:33:E9:EA
X509v3 extensions
subjectKeyIdentifier
  • A0:39:4F:9D:D4:CA:B2:D2:8E:29:0D:F3:94:2B:A3:52:FE:82:33:46
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • 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/47.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 : May 2 21:35:06.541 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:74:B8:DE:FC:5D:7D:F8:98:D1:9F:77:64:
  • 43:6D:BF:13:44:94:54:F2:F7:1C:73:CC:29:7E:BD:C7:
  • D2:06:99:89:02:20:35:6E:D1:4C:13:DC:78:2A:4E:11:
  • C5:FC:F2:02:93:9F:FB:6B:A2:B1:59:A7:C4:12:ED:EB:
  • 90:8D:68:7B:2B:4F
  • 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 : May 2 21:35:06.603 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:03:18:40:4E:09:E2:AB:48:CD:CE:75:74:
  • 58:AB:C6:59:4E:6A:62:BC:FF:27:55:D4:52:76:37:40:
  • 10:29:5C:9D:02:20:2B:12:65:EF:CA:31:88:9E:EA:AE:
  • A9:DE:63:B7:09:9A:09:01:71:0A:AE:2E:74:40:B2:9A:
  • DC:BD:E5:50:40:F8