SSL-Tools

SSL check results of mail.eyholzer.com

NEW You can also bulk check multiple servers.

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

Summary

JSON Refresh

Report created Sun, 28 Apr 2024 17:14:21 +0000

The mailservers of mail.eyholzer.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.eyholzer.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.eyholzer.com
144.91.99.182
 -
supported
eyholzer.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=eyholzer.com

Certificate chain
  • eyholzer.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • eyholzer.com
Alternative Names
  • abendgruss.ch
  • eyholzer.com
  • eyholzer.consulting
  • eyholzer.info
  • mail.eyholzer.com
  • mail.eyholzer.info
  • morcinczyk.ch
  • morcinczyk.de
  • www.abendgruss.ch
  • www.eyholzer.com
  • www.eyholzer.consulting
  • www.eyholzer.info
  • www.morcinczyk.ch
  • www.weidschuerli.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-22
Not valid after
2024-06-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8E:EA:CB:F6:98:07:51:F6:E6:22:40:73:73:F4:BB:AC:97:36:2B:02:68:D4:9E:59:99:29:49:F5:FF:A6:DF:55
SHA1
EB:BA:75:83:FF:5C:37:5E:39:76:1D:05:07:6D:C1:68:2D:70:0D:35
X509v3 extensions
subjectKeyIdentifier
  • 34:21:8D:74:C4:EF:44:A2:E3:69:30:EF:0D:89:E8:99:65:AB:1F:E1
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 : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 22 19:27:18.072 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:76:0F:30:9C:A0:CB:CB:B1:6F:09:C4:38:
  • 33:56:F0:70:DD:E3:66:BB:DF:B7:7A:F1:9A:93:4F:1B:
  • 87:A9:FD:81:02:20:73:E2:EF:5B:73:55:B9:29:26:88:
  • AC:E4:A8:11:67:4B:57:C9:FF:17:15:8A:6E:15:73:4D:
  • FC:BE:95:69:54:BB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 22 19:27:20.133 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3B:C4:03:E8:5B:F8:52:CC:59:70:5F:75:
  • 50:AC:34:81:71:69:87:7F:6A:E0:6C:E3:73:68:C0:A2:
  • 4F:03:2E:FE:02:20:4F:AD:37:22:92:33:F7:D1:7C:5A:
  • E7:4B:7F:3D:E6:C1:50:9C:77:42:E5:1B:A6:D8:AF:A9:
  • 88:A4:19:EF:08:AD