SSL-Tools

SSL check results of muscletest.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for muscletest.com 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, 20 Jan 2022 15:44:51 +0000

The mailservers of muscletest.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @muscletest.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.muscletest.com
162.253.153.38
 10
supported
muscletest.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
10 s

Outgoing Mails

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

Certificates

First seen at:

CN=muscletest.com

Certificate chain
  • muscletest.com
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • muscletest.com
Alternative Names
  • ftp.muscletest.com
  • mail.muscletest.com
  • muscletest.com
  • pop.muscletest.com
  • smtp.muscletest.com
  • www.muscletest.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-01-19
Not valid after
2022-04-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F0:57:69:D5:09:5E:39:3B:0D:16:DE:98:BF:4C:BB:16:D4:5E:43:70:EA:46:FB:C9:4B:3F:18:14:A0:06:93:79
SHA1
34:24:26:1B:79:2C:83:E0:FD:49:01:64:5E:D3:BE:3E:5E:8B:68:F6
X509v3 extensions
subjectKeyIdentifier
  • 70:C9:5F:F9:84:FA:BB:A5:27:DA:90:98:12:A7:CC:3E:57:BC:2A:1A
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Jan 19 11:53:42.034 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:01:C1:EF:1E:90:F8:C1:26:56:1A:23:0C:
  • 08:02:29:F1:93:F3:93:3D:50:68:98:4E:3E:3C:F5:6D:
  • 94:A4:F6:A4:02:21:00:C7:14:5D:69:18:76:73:7A:13:
  • F4:DC:51:19:AF:12:82:3A:A6:62:12:33:55:0F:B8:9B:
  • 86:8E:5F:DD:9D:1B:B9
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jan 19 11:53:42.090 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:50:34:8B:BF:37:CF:40:C0:EA:4D:A5:37:
  • 07:D2:78:29:A7:73:4A:23:3A:D8:42:3F:FD:10:85:58:
  • 72:77:1C:DB:02:21:00:C0:37:91:57:06:BB:9A:0E:6A:
  • 54:A2:A7:66:DB:77:5D:6E:C5:B4:A4:2F:1E:EA:BD:32:
  • 5E:FE:F8:72:28:33:71