SSL-Tools

SSL check results of itm-hummel.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for itm-hummel.de 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 Tue, 19 Sep 2023 00:55:50 +0000

The mailservers of itm-hummel.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @itm-hummel.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.itm-hummel.de
80.147.28.65
 10
supported
mail.itm-hummel.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @itm-hummel.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.itm-hummel.de

Certificate chain
  • mail.itm-hummel.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.itm-hummel.de
Alternative Names
  • autodiscover.itm-hummel.de
  • mail.itm-hummel.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-08-24
Not valid after
2023-11-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
82:99:0E:28:71:97:0A:AB:6F:AF:AA:B8:D2:41:68:65:A5:9F:2E:72:FA:F5:62:BE:7C:1D:9E:B0:16:1C:0F:78
SHA1
45:9E:2C:9B:FE:AB:27:67:99:38:B7:4E:17:C8:2F:C8:8C:FC:E5:F9
X509v3 extensions
subjectKeyIdentifier
  • A8:FA:42:25:7D:7E:A9:26:09:A9:DE:D7:22:9F:AA:69:71:B8:EB:A2
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 : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Aug 24 09:46:44.675 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:89:68:D7:F9:48:69:B5:53:E0:DC:70:
  • 3B:08:09:B6:A6:4F:A2:FF:73:F7:41:97:53:6C:C2:89:
  • 97:4E:2D:06:FA:02:21:00:D9:DF:3F:A6:EF:47:C4:45:
  • E8:E2:E4:F5:9E:32:8C:78:EF:2B:A0:A5:22:E5:53:AF:
  • 84:0F:DF:EF:0F:71:39:A1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Aug 24 09:46:44.691 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:26:D1:8D:73:9C:27:60:07:2A:E0:7F:68:
  • 4C:CA:6B:A6:34:21:8C:49:54:58:4A:37:1C:08:C1:68:
  • 35:C8:52:9E:02:21:00:D6:2A:AE:34:1E:5C:8C:D1:D2:
  • BE:AE:EC:2A:6C:F8:95:40:3F:F6:CF:B7:AC:FC:1A:D7:
  • B1:5A:D1:9F:0F:84:79