SSL-Tools

SSL check results of shanet.at

NEW You can also bulk check multiple servers.

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

JSON Refresh

Report created Mon, 05 Oct 2026 00:30:08 +0000

The mailservers of shanet.at can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @shanet.at addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.shanet.at
2a0a:4cc0:1:1156:a88a:2dff:fe63:6913
 10
supported
mail.shanet.at
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.shanet.at
152.53.16.251
 10
supported
mail.shanet.at
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.shanet.at

Certificate chain
  • mail.shanet.at
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.shanet.at
Alternative Names
  • mail.shanet.at
  • mta-sts.shanet.at
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-10-04
Not valid after
2027-01-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
50:6C:72:81:1E:15:AB:27:34:2E:4E:97:28:BB:07:70:C8:65:DD:B9:51:01:43:B5:FC:25:E4:89:2E:43:B6:63
SHA1
3F:35:BD:81:6B:F7:DD:30:DF:28:91:B7:66:E7:16:6B:7E:A4:0A:48
X509v3 extensions
subjectKeyIdentifier
  • DC:3C:40:BE:45:C3:F0:7F:96:1D:0A:FF:20:5E:5D:48:67:9D:3F:C9
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/121.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 8E:CA:47:0B:AC:DE:6A:F3:A2:06:B0:A4:7A:84:B7:46:
  • FE:1F:C6:BF:95:3E:25:E6:9B:4E:E4:02:48:F3:C6:E8
  • Timestamp : Oct 4 18:22:58.861 2026 GMT
  • Extensions: 00:00:05:00:1C:16:2B:F9
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F4:F6:57:19:C0:41:E2:AA:FF:FC:65:
  • 1B:D6:02:0A:60:12:83:B8:0A:D5:07:A4:B6:A8:FE:81:
  • 69:55:B0:8C:EF:02:21:00:D9:7D:56:9D:25:C3:9F:C4:
  • 08:98:F0:47:68:0A:9F:20:28:C5:6C:22:45:E6:E5:06:
  • 6F:6D:23:E9:64:D4:2B:F2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1C:9F:68:2C:E9:FA:F0:45:69:50:F8:1B:96:8A:87:DD:
  • DB:32:10:D8:4C:E6:C8:B2:E3:82:52:4A:C4:CF:59:9F
  • Timestamp : Oct 4 18:22:59.354 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:10:89:43:CE:F6:FB:6D:68:46:7B:5B:F7:
  • 74:28:96:3D:78:36:1C:67:2F:19:60:38:C6:F0:69:32:
  • 6F:AB:7E:B4:02:21:00:90:E8:30:3C:B9:B2:6A:C1:DA:
  • 18:8A:6F:63:1B:FF:AA:D1:A3:3F:BF:50:5C:80:2D:7D:
  • 98:FD:78:97:6D:15:12