Discover if the mail servers for 100.com 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 Wed, 27 May 2020 07:01:28 +0000
These servers are responsible for incoming mails to @100.com addresses.
| Hostname / IP address | Priority | STARTTLS | Certificates | Protocol | ||
|---|---|---|---|---|---|---|
|
mail.100.com
183.36.121.86
Results incomplete
|
10 |
supported
|
not checked |
|
3 s
|
We have received emails from these servers with @100.com sender addresses. Test mail delivery
| Host | TLS Version & Cipher | |
|---|---|---|
| unknown (1.55.241.4) |
Insecure - not encrypted!
|
|
| unknown (213.129.99.10) |
Insecure - not encrypted!
|
|
| unknown (180.128.0.237) |
Insecure - not encrypted!
|
|
| unknown (200.77.186.199) |
Insecure - not encrypted!
|
|
| unknown (201.236.143.242) |
Insecure - not encrypted!
|
|
| unknown (103.87.26.134) |
Insecure - not encrypted!
|
|
| unknown (46.172.69.163) |
Insecure - not encrypted!
|
|
| unknown (185.51.92.84) |
Insecure - not encrypted!
|
|
| unknown (1.53.137.92) |
Insecure - not encrypted!
|
|
| unknown (92.86.10.42) |
Insecure - not encrypted!
|
|
| unknown (145.253.118.157) |
Insecure - not encrypted!
|
|
| unknown (109.100.138.62) |
Insecure - not encrypted!
|
|
| unknown (46.35.184.187) |
Insecure - not encrypted!
|
No Certificates found
Heartbleed