Discover if the mail servers for web.de 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, 03 Oct 2024 14:31:33 +0000
These servers are responsible for incoming mails to @web.de addresses.
Hostname / IP address | Priority | STARTTLS | Certificates | Protocol | ||
---|---|---|---|---|---|---|
mx-ha02.web.de
212.227.17.8
Results incomplete
|
100 |
supported
|
mx.web.de |
|
1 s
|
|
mx-ha03.web.de
212.227.15.17
Results incomplete
|
100 |
supported
|
mx.web.de |
|
1 s
|
We have received emails from these servers with @web.de sender addresses. Test mail delivery
Host | TLS Version & Cipher | |
---|---|---|
unknown (IPv6:2a05:8b81:1000:ac::d5e3) |
TLSv1.2
ECDHE-RSA-AES256-GCM-SHA384
|
|
mout.web.de (212.227.17.11) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
mout.web.de (212.227.17.12) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
mout.web.de (217.72.192.78) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
mout.web.de (212.227.15.3) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
mout.web.de (212.227.15.4) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
mout.web.de (212.227.15.14) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
mout02.posteo.de (185.67.36.142) |
TLSv1.2
ECDHE-RSA-AES256-GCM-SHA384
|
DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.
Name | Options | DNSSEC | Matches |
---|---|---|---|
_25._tcp.mx-ha02.web.de |
|
valid
|
valid
|
_25._tcp.mx-ha02.web.de |
|
valid
|
— |
_25._tcp.mx-ha03.web.de |
|
valid
|
valid
|
_25._tcp.mx-ha03.web.de |
|
valid
|
— |