SSL-Tools

SSL check results of mwca.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for mwca.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 Mon, 20 Sep 2021 08:46:53 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mwca.ru
217.13.219.236
 10
supported
mwca.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s
mwca.ru
88.215.138.238
 10
supported
mwca.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s

Outgoing Mails

We have received emails from these servers with @mwca.ru sender addresses. Test mail delivery

Host TLS Version & Cipher
mwca.ru (217.13.219.236)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mwca.ru

Certificate chain
  • mwca.ru
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mwca.ru
Alternative Names
  • mwca.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-08-31
Not valid after
2021-11-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1F:78:DA:1E:B0:70:CF:A6:2B:2C:B3:D0:37:D7:8C:16:50:51:41:FD:A7:CC:64:DB:0E:FF:37:E2:5C:92:AE:99
SHA1
15:F7:7D:B7:10:7B:58:B7:A6:50:94:76:39:FB:2F:2C:6B:B1:87:12
X509v3 extensions
subjectKeyIdentifier
  • A4:7E:04:35:19:D1:B8:54:3E:2E:50:68:DC:38:C0:1F:1F:A5:52: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
  • 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 : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Aug 31 06:56:03.595 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:88:8C:57:57:92:DC:EA:ED:CF:46:A6:
  • 38:6B:6D:D5:1D:7E:9D:58:37:8B:DB:99:55:F7:1C:7E:
  • 0D:70:3C:7C:95:02:20:1B:6F:07:EA:F0:A6:B3:24:E4:
  • 2B:A0:B3:01:D0:6F:84:0A:75:9C:45:08:D5:61:21:22:
  • B1:F0:3F:C3:9A:B3:3E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Aug 31 06:56:03.650 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F7:11:F4:1E:43:08:EF:98:62:3B:93:
  • DE:19:C2:2E:99:65:C2:C7:D5:A2:A1:D2:7F:44:20:8F:
  • E3:93:2C:F7:8C:02:20:23:27:C3:20:B0:92:C1:1C:7B:
  • E1:C8:C1:77:F4:09:70:AE:95:07:BF:2C:1D:91:91:9E:
  • FF:B3:1A:AC:A8:39:F1