Discover if the mail servers for brick.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 Mon, 13 Nov 2023 03:59:12 +0000
These servers are responsible for incoming mails to @brick.com addresses.
Hostname / IP address | Priority | STARTTLS | Certificates | Protocol | ||
---|---|---|---|---|---|---|
us-smtp-inbound-1.mimecast.com
207.211.30.221
|
10 |
supported
|
*.mimecast.com |
|
6 s
|
|
us-smtp-inbound-1.mimecast.com
207.211.30.141
|
10 |
supported
|
*.mimecast.com |
|
6 s
|
|
us-smtp-inbound-1.mimecast.com
205.139.110.141
|
10 |
supported
|
*.mimecast.com |
|
6 s
|
|
us-smtp-inbound-1.mimecast.com
205.139.110.242
|
10 |
supported
|
*.mimecast.com |
|
5 s
|
|
us-smtp-inbound-1.mimecast.com
205.139.110.221
|
10 |
supported
|
*.mimecast.com |
|
5 s
|
|
us-smtp-inbound-1.mimecast.com
207.211.30.242
|
10 |
supported
|
*.mimecast.com |
|
6 s
|
|
us-smtp-inbound-2.mimecast.com
205.139.110.141
|
10 |
supported
|
*.mimecast.com |
|
6 s
|
|
us-smtp-inbound-2.mimecast.com
205.139.110.242
|
10 |
supported
|
*.mimecast.com |
|
5 s
|
|
us-smtp-inbound-2.mimecast.com
205.139.110.221
|
10 |
supported
|
*.mimecast.com |
|
7 s
|
|
us-smtp-inbound-2.mimecast.com
207.211.30.141
|
10 |
supported
|
*.mimecast.com |
|
5 s
|
|
us-smtp-inbound-2.mimecast.com
207.211.30.242
|
10 |
supported
|
*.mimecast.com |
|
5 s
|
|
us-smtp-inbound-2.mimecast.com
207.211.30.221
|
10 |
supported
|
*.mimecast.com |
|
5 s
|
We have not received any emails from a @brick.com address so far. Test mail delivery