SSL-Tools

SSL check results of backtotherules.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for backtotherules.net 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 Fri, 19 Apr 2024 00:36:07 +0000

The mailservers of backtotherules.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @backtotherules.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.backtotherules.net
134.255.216.216
 10
supported
mail.backtotherules.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.backtotherules.net

Certificate chain
  • mail.backtotherules.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)
  • mail.backtotherules.net
Alternative Names
  • mail.backtotherules.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-18
Not valid after
2024-07-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
45:2C:0F:94:DA:D4:0C:B0:B3:34:CE:E7:C8:50:45:AE:78:29:3C:8D:52:A6:0F:23:E3:BB:73:F1:61:0A:41:BD
SHA1
2D:4F:9C:CD:08:73:81:EA:65:C8:DA:E2:3A:76:B6:88:DC:D6:0B:0C
X509v3 extensions
subjectKeyIdentifier
  • 1F:C7:BC:96:79:DC:E3:1D:30:D7:99:E2:F2:C3:16:5F:21:D1:79:64
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 : Apr 18 22:47:56.315 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AF:91:35:96:25:2B:C7:5D:FD:CF:38:
  • 81:6E:23:1B:B2:0F:AE:16:A4:7C:F1:11:AA:E7:4C:06:
  • BE:6D:26:14:23:02:21:00:B2:17:66:CD:40:A8:21:97:
  • 5F:4A:3D:2A:41:A9:2A:D9:9D:FA:61:97:F3:06:AE:DF:
  • 75:B6:C4:9F:73:18:7F:F4
  • 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 : Apr 18 22:47:56.378 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0D:F9:5E:F8:C0:3D:AE:AC:62:5A:5D:4D:
  • 66:35:D4:63:C6:36:DF:FD:D9:89:4C:D4:4F:56:8F:4A:
  • 6B:9D:28:38:02:21:00:B2:17:B0:A2:FB:D1:E8:D0:2D:
  • 88:83:4E:30:39:B0:62:B4:6F:E4:28:03:77:B6:41:91:
  • 4E:AE:98:EC:48:4B:5F