SSL-Tools

SSL check results of ipgrussia.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for ipgrussia.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 Sun, 25 May 2025 10:23:29 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mtzavod.com
109.95.210.89
 10
supported
mail.mtzavod.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
21 s
mail.mtzavod.com
109.95.210.89
 20
supported
mail.mtzavod.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
21 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mtzavod.com

Certificate chain
  • mail.mtzavod.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.mtzavod.com
Alternative Names
  • mail.ipgrussia.ru
  • mail.mtzavod.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-03-26
Not valid after
2025-06-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
09:C9:EA:55:18:EB:AD:B9:BC:BB:67:95:1D:C3:E7:47:8C:47:C1:DC:42:D4:8D:F7:C1:07:1A:44:64:25:82:55
SHA1
29:95:92:5E:13:29:4B:34:E4:25:58:F0:12:53:11:1F:09:54:28:0F
X509v3 extensions
subjectKeyIdentifier
  • D7:85:83:3D:24:00:05:46:E7:22:93:47:4D:62:96:CD:31:8F:5A:1C
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/128.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Mar 26 14:47:10.734 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:39:74:8C:F4:80:32:BD:C4:BC:40:1E:5E:
  • 81:AF:71:B6:40:D7:8A:83:15:77:40:62:13:89:40:44:
  • 80:C5:07:9A:02:21:00:C7:A8:E8:6A:E6:F2:B9:6C:15:
  • 0A:F6:6A:2A:B6:B6:79:2E:20:51:21:45:DE:A6:C0:8A:
  • D2:9C:48:22:CC:9A:95
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Mar 26 14:47:10.741 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0C:79:56:84:C8:7C:07:0E:22:95:45:BF:
  • B6:33:F5:E3:04:E2:F4:5C:B5:AA:1D:C8:44:C0:98:39:
  • 2D:52:51:9F:02:20:66:6D:C5:4E:53:EF:07:6A:82:F7:
  • 00:C2:A2:D9:1F:01:E7:73:A5:28:BD:76:03:E5:20:BE:
  • D5:C6:AD:2D:BC:F5