SSL-Tools

SSL check results of ridingdogs.site

NEW You can also bulk check multiple servers.

Discover if the mail servers for ridingdogs.site 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 Tue, 16 Apr 2024 22:31:45 +0000

The mailservers of ridingdogs.site can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ridingdogs.site addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
panel700.harmonweb.net
51.89.75.23
 0
supported
panel700.harmonweb.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
panel700.harmonweb.net
51.89.75.24
 0
supported
panel700.harmonweb.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
panel700.harmonweb.net
51.89.75.26
 0
supported
panel700.harmonweb.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=panel700.harmonweb.net

Certificate chain
  • panel700.harmonweb.net
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • panel700.harmonweb.net
Alternative Names
  • panel700.harmonweb.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-12
Not valid after
2024-06-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
68:33:59:31:00:C3:B1:5A:B9:42:50:C6:69:BC:26:B7:4C:E7:D6:FE:A4:A3:EC:2B:85:F4:D6:8F:0F:A2:01:6A
SHA1
0E:AB:E8:44:38:47:84:BA:09:90:59:C2:81:60:65:6D:6B:9F:56:8F
X509v3 extensions
subjectKeyIdentifier
  • 90:1F:FA:1E:93:80:D7:ED:55:3E:59:B7:7F:D2:98:98:54:8C:F3:84
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 12 18:30:32.914 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5D:5E:08:34:A8:2C:AD:25:E8:5D:4E:3F:
  • C1:48:CB:35:52:67:27:DC:16:C4:6C:4E:57:88:44:71:
  • DB:45:43:7E:02:21:00:F0:B8:78:2D:63:EA:E6:B9:07:
  • 06:E5:58:0D:00:92:E4:87:3C:A0:FF:AF:B2:C5:9E:83:
  • 7A:FC:D1:30:6B:73:99
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Mar 12 18:30:32.928 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:94:2F:A9:BD:E6:4A:81:09:D9:7E:51:
  • F8:F0:1F:5A:F7:09:D1:74:A7:F6:AA:D8:1E:5C:B9:3E:
  • A2:40:B8:13:36:02:20:01:A4:D0:45:F0:79:B8:B8:86:
  • 9F:B5:12:DB:1F:F5:6E:EB:76:10:DD:BB:90:7A:30:9C:
  • 80:29:49:21:37:29:38