SSL-Tools

SSL check results of skytophosting.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for skytophosting.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 Sun, 31 May 2020 17:08:36 +0000

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

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

/mailservers/skytophosting.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
sub1.mx.skytophosting.net
94.130.190.128
 100
supported
skytophosting.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
20 s
sub2.mx.skytophosting.net
95.216.161.201
Results incomplete
200
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=skytophosting.net

Certificate chain
Subject
Common Name (CN)
  • skytophosting.net
Alternative Names
  • skytophosting.net
  • smtp.skytophosting.net
  • sub1.mx.skytophosting.net
  • sub1.skytophosting.net
  • www.skytophosting.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-18
Not valid after
2020-08-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7D:94:08:1E:5B:44:2C:B5:CA:31:96:41:6C:C7:FC:8A:70:C3:30:E8:37:39:09:A1:61:9F:EF:87:3E:B6:03:77
SHA1
98:82:BF:33:93:3A:D0:B6:C3:9A:97:35:DC:67:66:66:11:C1:4B:F0
X509v3 extensions
subjectKeyIdentifier
  • 06:80:F6:9E:D0:1D:BE:11:16:EB:2E:42:42:6E:87:94:0C:92:F4:F4
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 : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
  • 7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
  • Timestamp : May 18 15:25:38.289 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C5:BE:12:2E:0E:76:8D:2D:74:EB:3C:
  • 86:5F:4B:10:4F:B5:25:A0:AE:C9:89:92:82:BB:33:C1:
  • 1B:AC:3F:86:C9:02:20:67:8C:3B:EE:A1:0A:22:C9:20:
  • C2:15:68:66:7C:0B:A3:1F:F4:1A:E3:36:28:56:63:50:
  • 78:89:DB:B1:AC:92:A7
  • 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 : May 18 15:25:38.769 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:55:47:4B:BE:71:DC:16:CB:81:B4:44:94:
  • BB:85:D9:17:2A:8F:63:26:3E:4F:63:95:A4:43:3B:34:
  • 5C:9F:C7:39:02:21:00:A7:7D:AF:5D:68:59:BE:64:07:
  • 43:D6:FF:82:0E:3C:B0:D5:C5:21:55:9E:F1:7B:6F:A5:
  • 09:18:ED:E8:37:0F:16