SSL-Tools

SSL check results of rhw.info

NEW You can also bulk check multiple servers.

Discover if the mail servers for rhw.info 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, 11 Jul 2024 13:27:15 +0000

The mailservers of rhw.info can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rhw.info addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rhw.info
91.211.9.203
 10
supported
rhw.info
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 @rhw.info address so far. Test mail delivery

Certificates

First seen at:

CN=rhw.info

Certificate chain
  • rhw.info
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • rhw.info
Alternative Names
  • autodiscover.rhw.info
  • imap.rhw.info
  • mail.rhw.info
  • pop3.rhw.info
  • rhw.info
  • smtp.rhw.info
  • www.rhw.info
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-31
Not valid after
2024-08-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3D:C4:84:83:11:CB:66:A8:BD:ED:41:85:2D:49:58:51:F1:34:5F:9D:F2:71:57:04:3E:6E:98:1F:16:B5:DF:A0
SHA1
12:80:FC:99:98:92:28:9F:E5:A5:1F:0E:EC:F6:E6:23:C9:D8:8C:36
X509v3 extensions
subjectKeyIdentifier
  • 9C:C7:B3:EF:3B:E1:30:EF:B7:2D:96:78:62:60:C2:6C:3A:8D:32:F4
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : May 31 08:46:02.611 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:96:97:76:87:A6:52:24:EA:5F:0A:94:
  • FC:0E:7E:02:B5:DF:64:CE:F2:FC:33:37:8A:53:10:3D:
  • 14:8C:1F:50:EC:02:20:30:5C:79:53:9C:61:A2:3A:C4:
  • 92:97:08:B6:A6:73:39:02:9F:8B:33:44:F3:15:F3:83:
  • 98:48:BD:A2:B4:7F:EA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : May 31 08:46:02.595 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3A:BF:08:B9:15:A5:4A:40:B5:94:AA:BF:
  • 73:4B:35:82:BB:FF:59:3E:CF:F7:E1:41:ED:1E:C0:1B:
  • 7A:44:E5:70:02:20:56:98:8F:95:37:78:55:6F:3D:85:
  • 98:D8:3C:5D:3E:B6:13:73:F3:B7:86:0A:98:4E:BA:6C:
  • 18:F5:DA:32:19:C0