SSL-Tools

SSL check results of linuz.ch

NEW You can also bulk check multiple servers.

Discover if the mail servers for linuz.ch 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 Thu, 25 Apr 2024 19:41:04 +0000

The mailservers of linuz.ch can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @linuz.ch addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.linuz.ch
2a01:4f8:c2c:48bd::
Results incomplete
10 not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.linuz.ch
2a01:4f8:c2c:3fe7::1
Results incomplete
10 not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.linuz.ch
159.69.11.43
 10
supported
mail.linuz.ch
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.linuz.ch

Certificate chain
  • mail.linuz.ch
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.linuz.ch
Alternative Names
  • autodiscover.linuz.ch
  • mail.linuz.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-24
Not valid after
2024-07-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D1:A4:AE:CF:27:A2:9F:FC:34:BD:E0:A6:21:2E:F8:A4:DB:F7:5C:DE:B0:64:DF:5E:B3:85:6C:6A:07:14:7B:A2
SHA1
00:C8:9C:3A:13:CA:7C:23:A3:73:32:89:3B:3B:8C:B1:D1:84:D3:CB
X509v3 extensions
subjectKeyIdentifier
  • 53:DF:B6:20:06:3A:9A:21:D7:CE:86:66:8B:AE:A1:12:02:9A:FA:51
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 24 01:13:37.203 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:79:E7:08:D3:FF:DA:95:B5:01:39:EE:94:
  • 84:E7:A5:82:EA:3E:C0:38:8A:50:F2:F4:39:53:FE:7C:
  • 76:A4:F5:4F:02:20:2F:85:83:AB:47:86:50:95:79:F2:
  • B1:6D:7C:5A:13:9E:2E:03:7E:64:69:E7:EE:45:CC:53:
  • 1B:3F:2D:73:F5:72
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 24 01:13:37.193 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:43:02:20:2F:AF:FB:3E:15:0D:4A:E5:B1:5A:44:B5:
  • 3E:BA:3F:F1:EA:C6:77:26:CF:E1:AA:55:4B:7F:9E:E4:
  • 34:A4:BC:DE:02:1F:05:5A:A2:14:03:6C:1D:A2:D1:CF:
  • 27:BA:AD:96:DA:36:B1:29:74:17:D6:9A:04:28:31:F4:
  • D1:B4:91:83:51

DANE

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.mail.linuz.ch
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid