Discover if the mail servers for safe-mail.net 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 Mon, 25 May 2020 11:35:37 +0000
However, we found problems that may affect the security.
These servers are responsible for incoming mails to @safe-mail.net addresses.
Hostname / IP address | Priority | STARTTLS | Certificates | Protocol | ||
---|---|---|---|---|---|---|
tamar.safe-mail.net
212.29.227.86
|
10 |
supported
|
*.safe-mail.net |
|
23 s
|
|
dekel.safe-mail.net
212.29.227.84
|
10 |
supported
|
*.safe-mail.net |
|
24 s
|
|
pitango.safe-mail.net
212.29.227.82
|
40 |
supported
|
*.safe-mail.net |
|
18 s
|
|
mango.safe-mail.net
212.29.227.83
|
40 |
supported
|
*.safe-mail.net |
|
18 s
|
|
orange.safe-mail.net
212.29.227.81
|
40 |
supported
|
*.safe-mail.net |
|
16 s
|
We have received emails from these servers with @safe-mail.net sender addresses. Test mail delivery
Host | TLS Version & Cipher | |
---|---|---|
pitango.safe-mail.net (212.29.227.82) |
TLSv1.2
ECDHE-RSA-AES256-GCM-SHA384
|