SSL-Tools

SSL check results of keppler-it.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for keppler-it.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 Sun, 15 Jun 2025 00:31:08 +0000

The mailservers of keppler-it.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @keppler-it.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.keppler-it.de
2a01:4f8:bb:c00::1:2
 10
supported
secure.keppler-it.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.keppler-it.de
88.198.223.3
 10
supported
secure.keppler-it.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=secure.keppler-it.de

Certificate chain
  • secure.keppler-it.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • secure.keppler-it.de
Alternative Names
  • mail.keppler-it.de
  • secure.keppler-it.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-03
Not valid after
2025-09-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
47:91:E1:2A:56:BD:B5:87:21:05:D2:69:99:85:7D:A3:B9:A3:FD:9F:EE:15:F0:2B:34:24:13:B9:C7:82:39:F1
SHA1
EC:62:F0:E1:F1:49:86:43:E4:75:7B:B3:7E:DD:A2:A0:B7:3C:19:5A
X509v3 extensions
subjectKeyIdentifier
  • A9:A2:A3:13:4B:E6:D4:C6:E2:9D:6E:0E:01:C5:44:D2:53:D5:E7:A2
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/24.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Jun 3 20:45:09.863 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:83:19:8C:66:B4:46:71:D4:65:DE:50:
  • B4:22:C8:53:10:62:E5:EA:C0:98:87:5D:5C:0C:B3:1D:
  • C6:39:33:AC:5D:02:21:00:89:C7:8F:21:49:BC:08:D9:
  • 66:90:78:D2:D3:5E:36:61:31:A4:68:79:FC:5A:AF:CA:
  • CD:A8:CA:8D:1A:CE:CA:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 3 20:45:09.873 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:17:0A:FE:50:0E:82:9E:12:EE:99:62:B2:
  • 19:AF:E1:1E:CD:00:A8:DD:FF:4A:3F:45:9A:28:99:A7:
  • 59:8E:58:98:02:21:00:A3:8A:38:41:B5:05:B1:B7:20:
  • 67:CF:D0:26:A6:06:3C:23:02:AC:18:E0:16:B5:3B:66:
  • 5D:01:9B:A2:3D:2B:20

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