SSL check results of smarter.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for smarter.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.

Summary

Report created Mon, 13 Nov 2023 14:56:43 +0000

The mailservers of smarter.net can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @smarter.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smarter.net
64.91.225.90
10
supported
Plesk
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
26 s

Outgoing Mails

We have not received any emails from a @smarter.net address so far. Test mail delivery

Certificates

First seen at:

emailAddress=info@plesk.com,CN=Plesk,O=Plesk,L=Schaffhausen,C=CH

Certificate chain
  • Plesk (Certificate is self-signed.)
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
    • Expired
    • Unknown Authority

Subject
Country (C)
  • CH
Locality (L)
  • Schaffhausen
Organization (O)
  • Plesk
Common Name (CN)
  • Plesk
Email
  • info@plesk.com
Issuer

Certificate is self-signed.

validity period
Not valid before
2017-09-27
Not valid after
2018-09-27
Fingerprints
SHA256
A0:84:B0:C3:33:85:1B:45:CB:40:65:C0:DE:DE:9A:A2:26:73:97:34:6E:0D:7C:D3:3B:78:69:9B:33:59:64:01
SHA1
86:44:FC:A8:84:96:CA:7C:D6:38:AA:FC:CE:3B:2C:2F:CA:09:DC:27