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 Wed, 10 Jul 2024 12:21:30 +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
2024-05-15
Not valid after
2024-08-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B0:A2:28:ED:F0:23:CC:C9:22:3D:3F:A8:A9:C8:6D:51:99:D2:D4:B5:07:0D:56:AF:1A:7C:60:11:03:FC:56:90
SHA1
F9:D0:08:88:74:00:85:CF:FE:72:0E:AD:93:EF:DE:0F:31:F5:49:C0
X509v3 extensions
subjectKeyIdentifier
  • 45:5E:F4:F4:20:8B:73:3B:88:24:B4:AC:EC:9C:90:9D:DB:88:0B:CD
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : May 15 08:19:20.423 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:86:F7:1E:87:4B:C2:FF:92:8B:44:CD:
  • 61:8C:B4:1A:0F:76:86:D5:E8:4B:85:BB:FE:9B:BD:CE:
  • 0A:04:81:F9:73:02:21:00:80:75:B5:B4:AD:19:0B:93:
  • AB:D0:1F:68:A6:CD:39:0A:1F:67:E2:5E:86:42:9F:53:
  • FF:A6:24:71:C8:34:77:FB
  • 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 : May 15 08:19:20.655 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:75:EF:F4:F6:49:87:4E:5B:18:9F:98:45:
  • 07:DC:B2:2D:9D:4A:2F:A5:15:D8:0D:8E:8F:81:B4:02:
  • EF:06:40:29:02:20:45:BB:4F:B1:72:95:98:5F:E3:9E:
  • 57:3F:EE:D7:85:C6:73:D4:C3:18:88:3C:EA:7D:3E:4B:
  • 80:E4:FC:49:00:19