SSL-Tools

SSL check results of vegaeco.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for vegaeco.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, 09 Aug 2026 00:30:28 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.vegaeco.ru
46.34.159.13
 10
supported
mail.vegaeco.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mail.vegaeco.ru
46.34.159.13
 20
supported
mail.vegaeco.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.vegaeco.ru

Certificate chain
  • mail.vegaeco.ru
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.vegaeco.ru
Alternative Names
  • mail.vegaeco.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-03
Not valid after
2026-11-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
57:74:7F:39:06:59:DB:38:27:30:4C:6E:F9:41:A3:99:EB:C1:48:06:E5:59:9E:8E:24:F6:FF:7D:9D:4D:CD:FF
SHA1
C6:A5:44:85:D6:A5:A6:E0:96:6A:82:54:6F:46:40:D8:E4:F4:88:E1
X509v3 extensions
subjectKeyIdentifier
  • D0:E8:6F:15:D4:1F:1E:25:19:62:95:1C:62:F1:3F:F3:F8:B5:E9:C6
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/73.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AF:67:88:3B:57:B0:4E:DD:8F:A6:D9:7E:F6:2E:A8:EB:
  • 81:0A:C7:71:60:F0:24:5E:55:D6:0C:2F:E7:85:87:3A
  • Timestamp : Aug 3 08:43:53.959 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3A:B9:4F:AD:A6:BB:A4:50:B8:ED:D3:23:
  • 4C:72:12:5E:E3:12:6F:4C:C6:6C:D5:FD:FB:83:81:30:
  • 9E:CB:22:A4:02:20:13:A4:30:5C:C8:B2:38:EB:22:07:
  • 75:D7:0F:1B:B0:1F:76:D4:35:B4:53:54:FD:AC:72:7C:
  • D5:41:A7:BD:C1:CE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 26:E3:64:6E:58:69:21:23:BC:34:3F:47:24:35:9B:37:
  • 92:CD:24:5A:88:D8:15:D3:93:33:FD:99:18:AB:47:23
  • Timestamp : Aug 3 08:43:52.627 2026 GMT
  • Extensions: 00:00:05:00:30:8C:32:07
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E8:C8:7E:9D:F5:5E:08:7E:8F:09:C0:
  • D6:B1:30:78:6D:64:94:CD:91:37:3E:FC:CA:8F:37:9D:
  • 9A:7E:82:D4:44:02:21:00:91:FF:52:21:2B:D6:E3:E8:
  • D0:F9:BF:80:20:6E:18:08:2C:3F:3B:7A:A6:4B:8E:33:
  • 16:2C:E4:E9:D8:32:80:F9