SSL-Tools

SSL check results of bezirksrichter-hinwil.ch

NEW You can also bulk check multiple servers.

Discover if the mail servers for bezirksrichter-hinwil.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 Sat, 20 Apr 2024 08:38:12 +0000

The mailservers of bezirksrichter-hinwil.ch can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @bezirksrichter-hinwil.ch addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
orion.bezirksrichter-hinwil.ch
2a01:4f8:c0c:896b::1
 10
supported
orion.bezirksrichter-hinwil.ch
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
orion.bezirksrichter-hinwil.ch
167.235.48.21
 10
supported
orion.bezirksrichter-hinwil.ch
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 @bezirksrichter-hinwil.ch address so far. Test mail delivery

Certificates

First seen at:

CN=orion.bezirksrichter-hinwil.ch

Certificate chain
  • orion.bezirksrichter-hinwil.ch
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • orion.bezirksrichter-hinwil.ch
Alternative Names
  • orion.bezirksrichter-hinwil.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-18
Not valid after
2024-07-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
64:9F:23:41:6D:71:79:95:25:ED:CA:05:31:24:DD:2E:E2:DE:58:EC:8F:3A:27:49:87:80:3D:1A:A8:F4:E6:76
SHA1
6B:55:4E:5D:72:70:6E:50:8F:E6:F0:52:50:23:1D:C6:B7:0E:6E:15
X509v3 extensions
subjectKeyIdentifier
  • 19:94:70:BD:A6:16:4F:BD:7A:10:56:1B:5A:8C:34:60:47:8F:E8:72
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 18 09:35:05.148 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AA:06:81:87:B4:70:77:0D:C4:5E:A8:
  • 83:E9:BD:85:DE:42:14:99:E5:94:34:33:77:1E:5E:AC:
  • 97:37:41:C7:DC:02:20:01:E0:14:89:BE:AA:BE:F0:19:
  • 6B:D4:DA:99:60:91:E6:34:1A:36:3E:32:38:ED:4B:C9:
  • 49:02:3B:02:09:9E:B8
  • 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 18 09:35:05.151 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F0:F8:1F:D1:A6:7D:A5:55:60:57:9C:
  • 99:D5:95:2C:89:67:B0:33:33:FE:DA:DC:10:79:9E:69:
  • 4F:22:17:C2:DA:02:21:00:B5:37:48:86:B1:1D:F6:D9:
  • C9:50:1E:46:DE:9D:1D:FA:0B:C1:F0:C2:1A:96:F5:CC:
  • 82:0A:ED:77:2C:48:E0:07