SSL check results of mx.msk.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for mx.msk.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

Report created Sat, 27 Apr 2024 07:59:43 +0000

The mailservers of mx.msk.ru can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mx.msk.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.msk.ru
5.252.195.67
-
supported
mx.msk.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s
mx.msk.ru
2a07:ac80:0:5f::5
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 @mx.msk.ru address so far. Test mail delivery

Certificates

First seen at:

CN=mx.msk.ru

Certificate chain
  • mx.msk.ru
    • remaining
    • 256 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mx.msk.ru
Alternative Names
  • mx.msk.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-24
Not valid after
2024-06-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
51:F5:D8:84:0B:C7:EE:CC:04:6C:59:3E:75:D5:A8:55:13:84:4A:C3:24:37:0F:5F:E7:CF:A2:92:80:BB:71:5A
SHA1
FD:FB:2D:F7:00:F1:CB:75:DD:5F:06:EC:BA:BE:E4:E4:30:96:B5:2C
X509v3 extensions
subjectKeyIdentifier
  • 54:73:48:12:71:81:09:96:D3:29:D5:DE:86:5E:54:78:89:97:68:CF
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Mar 24 20:12:15.844 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:67:A1:4C:9F:7A:2C:80:22:FB:94:DA:AD:
  • 13:47:24:65:6A:A9:A7:18:58:7B:5E:33:80:19:D9:92:
  • D7:EE:A5:62:02:21:00:9E:75:26:44:0C:39:35:D4:91:
  • 5F:E0:F2:78:E1:14:FC:5A:45:05:CE:8A:20:72:28:67:
  • EB:07:87:13:8C:9F:07
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 24 20:12:15.908 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:22:78:7C:70:3C:92:CB:54:D1:28:87:BF:
  • 69:A3:AD:8F:9A:E1:08:E0:64:14:6D:AE:8B:91:8C:A5:
  • 9F:60:74:80:02:20:0C:07:AC:04:AC:8D:BE:C5:2D:8E:
  • E8:45:EF:7B:5E:36:05:46:DA:F2:83:9D:0E:5C:33:D9:
  • D1:8B:39:4E:3E:0B