SSL-Tools

SSL check results of supercomputer321.tk

NEW You can also bulk check multiple servers.

Discover if the mail servers for supercomputer321.tk 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 Mon, 25 May 2020 13:00:38 +0000

error: Couldn't find Certificate with [WHERE (id=E'\\xe6a3b45b062d509b3382282d196efe97d5956ccb')]

The mailservers of supercomputer321.tk can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @supercomputer321.tk addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.supercomputer321.tk
35.188.190.106
 1
supported
www.supercomputer321.tk
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
smtp.supercomputer321.tk
35.188.190.106
 2
supported
www.supercomputer321.tk
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=www.supercomputer321.tk

Certificate chain
Subject
Common Name (CN)
  • www.supercomputer321.tk
Alternative Names
  • mail.supercomputer321.tk
  • supercomputer321.tk
  • www.supercomputer321.tk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-03-31
Not valid after
2020-06-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
53:1A:19:E7:42:35:EE:A7:B8:EB:F3:89:89:B0:30:6C:9D:32:1D:4A:3F:F8:63:70:93:7E:8F:01:E2:27:00:78
SHA1
16:D4:AB:AC:6D:57:A5:B8:C2:12:F1:C6:17:63:94:09:69:F5:3D:E2
X509v3 extensions
subjectKeyIdentifier
  • CD:7F:7C:E3:15:D9:84:C7:9A:82:AA:14:F8:39:23:9C:4D:8E:7D:16
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
  • 7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
  • Timestamp : Apr 1 00:01:09.156 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:69:DD:D0:03:F6:25:BD:EE:CA:99:23:11:
  • 3E:B2:78:66:6F:54:B4:09:24:7A:D6:76:23:1F:B8:AB:
  • 96:F5:B2:97:02:20:1F:FD:5E:4B:1E:C1:DC:31:AB:12:
  • F3:58:45:A2:7B:17:2A:B1:18:9D:6C:A5:F9:59:7E:63:
  • 67:0F:17:A9:3A:DE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Apr 1 00:01:09.143 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A3:C6:1C:D7:F4:62:72:53:A3:EF:BE:
  • 8A:64:45:23:9F:55:C0:BA:68:60:A3:71:4C:FD:5E:97:
  • 06:C6:9A:46:B5:02:20:49:FA:81:16:B0:BB:5D:8A:A1:
  • 74:FF:6E:95:0D:14:29:0F:9C:B1:0F:E2:D9:B3:C9:EC:
  • A3:EA:BD:9A:69:1B:EF