SSL-Tools

SSL check results of mail.leonklingele.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.leonklingele.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 Mon, 25 Nov 2024 21:57:14 +0000

The mailservers of mail.leonklingele.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.leonklingele.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.leonklingele.de
185.183.159.234
 -
supported
mail.leonklingele.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.leonklingele.de
2a03:4000:1d:46d::1
 -
supported
mail.leonklingele.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.leonklingele.de

Certificate chain
  • mail.leonklingele.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.leonklingele.de
Alternative Names
  • mail.leonklingele.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-11-24
Not valid after
2025-02-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6E:F1:E3:AD:64:26:23:0D:8D:C0:05:F4:FA:C5:38:EE:0A:22:58:DF:B7:AD:CF:BC:89:BD:57:88:F7:C9:39:6B
SHA1
80:C8:84:D4:74:41:89:AE:4F:61:33:D2:63:DA:BC:B6:F3:A5:A3:DE
X509v3 extensions
subjectKeyIdentifier
  • 90:94:3F:91:C6:C7:5C:7E:B9:CE:32:9E:79:80:A5:22:76:D8:E2:AC
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Nov 24 05:00:18.214 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:13:4B:31:A0:DA:74:70:A9:09:47:BE:DB:
  • 1D:AB:A9:BA:46:AC:D3:33:08:51:50:B6:EA:76:97:45:
  • EA:0D:0E:48:02:20:68:F8:87:64:44:78:77:7B:75:96:
  • 17:19:83:24:3E:8A:79:EE:8B:26:2B:66:96:87:72:8D:
  • E0:D9:55:79:15:1D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Nov 24 05:00:18.561 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:09:D2:8E:E9:58:B4:9B:E9:FA:AA:F8:93:
  • 4C:39:02:C5:1E:D9:56:66:F9:87:A2:66:60:BA:9C:A1:
  • 70:A3:77:D5:02:20:14:F1:5C:C9:B0:4D:7F:1D:93:A8:
  • EC:DC:8E:23:F7:59:3E:5A:FE:E8:D3:BD:FB:08:59:2C:
  • B9:BD:63:C8:75:CE

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.leonklingele.de
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid