SSL-Tools

SSL check results of 1c.hk-vostok.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for 1c.hk-vostok.ru 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, 16 Nov 2023 08:23:51 +0000

We can not guarantee a secure connection to the mailservers of 1c.hk-vostok.ru!

Please contact the operator of 1c.hk-vostok.ru and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/1c.hk-vostok.ru

Servers

Incoming Mails

These servers are responsible for incoming mails to @1c.hk-vostok.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
1c.hk-vostok.ru
78.85.13.110
 -
supported
*.hk-vostok.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 s
1c.hk-vostok.ru
2a03:6f00:6:1::517:32bf
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

We have not received any emails from a @1c.hk-vostok.ru address so far. Test mail delivery

Certificates

First seen at:

CN=*.hk-vostok.ru

Certificate chain
  • *.hk-vostok.ru
    • remaining
    • 3072 bit
    • sha256WithRSAEncryption
    • Expired
    • Unknown Authority
      R3
Subject
Common Name (CN)
  • *.hk-vostok.ru
Alternative Names
  • *.hk-vostok.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-11-01
Not valid after
2022-01-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A9:45:A4:A6:00:CA:67:4C:8A:AF:AF:5B:C4:2F:E3:52:4C:A9:F9:05:B3:F9:09:EE:09:AD:20:15:60:C0:63:CC
SHA1
23:A5:3B:59:86:AD:2E:01:95:15:D5:0C:CD:7D:DC:51:29:D3:9F:A0
X509v3 extensions
subjectKeyIdentifier
  • 5C:7E:36:E2:0D:69:0C:1F:B3:64:A5:18:62:5B:8A:0D:A7:5D:BA:8F
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 : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Nov 1 09:57:02.120 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B9:F3:56:A4:56:D6:69:7B:81:6B:E2:
  • ED:E8:F8:0D:87:B2:33:AC:C7:62:89:6D:36:A6:F1:E9:
  • 4A:49:0C:E4:63:02:20:73:60:DF:ED:E2:81:25:40:A7:
  • EF:4A:E5:0C:6C:D4:15:50:AF:42:C2:DC:00:BE:15:6F:
  • 93:F7:24:C7:3F:FD:10
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Nov 1 09:57:02.159 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:88:3C:2E:4E:57:6C:05:23:C8:0E:92:
  • 73:77:5B:67:25:15:90:50:86:ED:ED:C5:09:BB:AA:14:
  • 16:6E:93:D2:E3:02:21:00:AD:95:AA:72:63:9D:01:97:
  • 39:B4:17:1F:C9:8B:78:39:E1:AA:CA:8A:A7:FB:BE:E2:
  • 33:17:17:D0:05:5A:9A:75