SSL-Tools

SSL check results of sixmo.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for sixmo.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 Sat, 09 Dec 2023 09:39:54 +0000

We can not guarantee a secure connection to the mailservers of sixmo.com!

Please contact the operator of sixmo.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/sixmo.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
sixmo.com
2001:4ba0:fff4:ee:c0ff:ee::7
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
3 s
sixmo.com
5.199.133.227
 20
supported
sixmo.com
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 @sixmo.com address so far. Test mail delivery

Certificates

First seen at:

CN=sixmo.com

Certificate chain
  • sixmo.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • sixmo.com
Alternative Names
  • sixmo.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-11-09
Not valid after
2024-02-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7D:F6:5A:B0:35:B6:9E:BC:0F:8B:3F:6B:79:B6:9E:33:71:1D:AB:27:95:23:C8:85:3E:B6:17:3F:F2:9E:52:A6
SHA1
EF:ED:71:C3:0F:2E:80:D5:E0:2F:63:75:0B:53:46:9C:3C:B7:AE:53
X509v3 extensions
subjectKeyIdentifier
  • AF:23:39:C4:4F:90:8F:4D:21:EB:9E:B4:D9:10:E7:F0:57:47:4F:BA
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 : 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 : Nov 9 19:46:24.033 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A3:63:D6:2A:5D:85:CD:74:A9:D5:0F:
  • FC:CA:18:C4:98:C3:DE:BB:88:64:40:85:7C:46:57:B1:
  • 0F:CC:AF:76:60:02:20:6C:55:3C:88:F3:B8:A8:B0:01:
  • 4F:32:05:10:09:3A:FF:70:16:D3:86:63:2A:5C:52:AB:
  • 05:B9:E0:82:F7:F8:F8
  • 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 : Nov 9 19:46:24.037 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8F:79:96:BE:DF:58:70:1F:0B:7E:A6:
  • 28:BA:57:2F:F9:87:21:E9:81:34:C6:8A:8B:C3:48:8E:
  • 59:72:EB:B4:D4:02:21:00:FA:B2:C9:4C:6F:56:FA:8A:
  • 7C:28:AB:8C:43:9B:51:F6:7F:C6:7F:55:33:48:BE:3E:
  • 96:2F:5A:B6:21:43:28:F1