Discover if the mail servers for inexio.email 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, 26 Jul 2021 21:29:21 +0000
These servers are responsible for incoming mails to @inexio.email addresses.
Hostname / IP address | Priority | STARTTLS | Certificates | Protocol | ||
---|---|---|---|---|---|---|
in-n3.mx.inexio.net
2a01:5c0:0:4::206
Results incomplete
|
10 |
supported
|
not checked |
|
2 s
|
|
in-n3.mx.inexio.net
131.117.148.206
Results incomplete
|
10 |
supported
|
not checked |
|
2 s
|
|
in-n4.mx.inexio.net
2a01:5c0:0:5::141
Results incomplete
|
10 |
supported
|
not checked |
|
2 s
|
|
in-n4.mx.inexio.net
131.117.148.141
Results incomplete
|
10 |
supported
|
not checked |
|
2 s
|
We have received emails from these servers with @inexio.email sender addresses. Test mail delivery
Host | TLS Version & Cipher | |
---|---|---|
out17.mx.inexio.net (IPv6:2a02:6d40:63:1::1) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
|
out9.mx.inexio.net (IPv6:2a01:5c0:60::33) |
TLSv1.3
TLS_AES_256_GCM_SHA384
|
No Certificates found
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.in-n3.mx.inexio.net |
|
valid
|
— |
_25._tcp.in-n3.mx.inexio.net |
|
valid
|
— |
_25._tcp.in-n4.mx.inexio.net |
|
valid
|
— |
_25._tcp.in-n4.mx.inexio.net |
|
valid
|
— |