SSL check results of mail.kleemann-beton.de

NEW You can also bulk check multiple servers.

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

Report created Wed, 15 Jul 2026 12:58:17 +0000

The mailservers of mail.kleemann-beton.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.kleemann-beton.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.kleemann-beton.de
46.224.132.135
-
supported
mail.kleemann-beton.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mail.kleemann-beton.de
2a01:4f8:c012:7b85::1
-
supported
mail.kleemann-beton.de
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 @mail.kleemann-beton.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.kleemann-beton.de

Certificate chain
  • mail.kleemann-beton.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384

          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384

              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384

Subject
Common Name (CN)
  • mail.kleemann-beton.de
Alternative Names
  • mail.kleemann-beton.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-07-11
Not valid after
2026-10-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
3C:26:26:E6:C3:C4:48:22:EB:EC:E6:2C:29:14:3C:C6:1D:83:5C:44:23:40:18:69:FA:D8:71:4D:CA:93:50:B9
SHA1
81:9F:A4:3F:92:94:F8:DB:F3:21:4C:3B:09:15:C5:5D:B0:4D:8F:BB
X509v3 extensions
subjectKeyIdentifier
  • 21:DE:72:F5:9E:7D:CD:7B:3F:72:92:32:C5:72:7F:6B:C3:91:BF:B0
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/65.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:4E:43:87:FA:EC:C1:EF:81:F3:19:24:26:A8:18:65:
  • 01:C7:D3:5F:38:02:01:3F:72:67:7D:55:37:2E:19:D8
  • Timestamp : Jul 11 13:53:58.072 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:94:E7:A0:03:72:7E:70:27:78:55:37:
  • BA:7C:02:4A:47:73:87:34:21:14:80:44:BE:B1:08:97:
  • A3:8E:00:14:73:02:20:31:69:8A:23:59:E4:88:CF:38:
  • 42:12:09:93:F6:59:D0:26:35:4A:9C:B3:E7:6A:AF:E7:
  • DB:9E:E3:1C:89:3E:0B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A8:26:CB:E3:0A:C6:35:12:46:53:3F:E0:65:F1:4F:19:
  • D9:6E:19:08:13:C4:1D:D9:6D:79:00:B3:12:3C:55:27
  • Timestamp : Jul 11 13:53:58.287 2026 GMT
  • Extensions: 00:00:05:00:13:90:52:0F
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E4:93:9A:04:24:BA:C3:38:79:07:AC:
  • 0A:5D:0B:14:B9:C3:06:05:F3:2D:6B:2C:E2:FF:F2:E5:
  • BE:B3:E9:16:F2:02:21:00:F4:CA:D0:DA:83:28:41:E7:
  • 3E:82:0F:EC:D0:80:1E:5D:EC:19:60:D3:7D:AE:43:2C:
  • 41:C1:E7:62:3F:BF:42:17