Discover if the mail servers for mail.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.
Report created Thu, 18 Jun 2026 16:09:29 +0000
These servers are responsible for incoming mails to @mail.ru addresses.
| Hostname / IP address | Priority | STARTTLS | Certificates | Protocol | ||
|---|---|---|---|---|---|---|
|
mxs.mail.ru
94.100.180.31
Results incomplete
|
10 |
supported
|
not checked |
|
1 s
|
|
|
mxs.mail.ru
217.69.139.150
Results incomplete
|
10 |
supported
|
not checked |
|
1 s
|
We have received emails from these servers with @mail.ru sender addresses. Test mail delivery
| Host | TLS Version & Cipher | |
|---|---|---|
| f319.i.mail.ru (217.69.130.170) |
TLSv1.2
ECDHE-RSA-AES256-GCM-SHA384
|
|
| f422.i.mail.ru (185.5.136.93) |
TLSv1.2
ECDHE-RSA-AES256-GCM-SHA384
|
|
| unknown (46.183.222.62) |
Insecure - not encrypted!
|
|
| unknown (46.183.220.24) |
Insecure - not encrypted!
|
|
| unknown (185.180.199.71) |
Insecure - not encrypted!
|
|
| srv03.23553.serviceprovider.de (212.223.35.234) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
| f162.i.mail.ru (128.140.171.250) |
TLSv1.2
ECDHE-RSA-AES256-GCM-SHA384
|
No Certificates found
Heartbleed