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 Sat, 02 Jul 2022 19:35:12 +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
88.215.138.238
 10
supported
mwca.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
13 s
mwca.ru
217.13.219.236
 10
supported
mwca.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • 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
2022-05-11
Not valid after
2022-08-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C9:CE:87:4F:E7:B5:1A:88:A5:CE:6B:34:1B:7D:63:2E:44:E0:45:E6:DC:97:71:29:B9:8A:2B:63:9C:28:17:C4
SHA1
1F:1D:01:B8:6E:C7:35:8E:5E:D4:12:64:2D:A4:90:2F:B3:6C:3F:33
X509v3 extensions
subjectKeyIdentifier
  • 52:A5:96:85:FA:52:34:5F:01:4E:7E:43:0E:C5:30:20:7A:96:1A:75
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 : 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 : May 11 06:19:13.400 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E1:A1:49:F8:3A:FF:35:D1:79:89:F3:
  • E1:CB:33:58:F8:5A:C4:54:13:57:C0:81:C4:97:EA:13:
  • 41:9F:EA:41:79:02:20:6C:79:A0:33:E6:D4:86:73:36:
  • 71:A8:67:60:57:A8:8D:ED:02:5E:96:39:E4:10:3B:20:
  • 85:95:60:9E:5A:C4:1F
  • 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 : May 11 06:19:13.921 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:54:D9:28:7D:11:BF:AC:31:C0:66:0C:80:
  • EB:FC:67:47:08:21:97:CF:56:50:FD:E7:8C:E0:80:AA:
  • 28:9F:56:D5:02:21:00:89:47:A3:A8:45:C0:57:A5:85:
  • 16:CB:71:7F:31:5C:1A:A0:9A:9D:8E:89:D7:C9:F6:C8:
  • 0D:CF:B6:27:ED:3D:96