SSL-Tools

SSL check results of isenberg-lima.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for isenberg-lima.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, 22 Oct 2024 10:08:43 +0000

The mailservers of isenberg-lima.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @isenberg-lima.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.isenberg-lima.de
2a01:4f8:c2c:233a::1
 0
supported
mail.isenberg-lima.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
mail.isenberg-lima.de
188.245.188.131
 0
supported
mail.isenberg-lima.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.isenberg-lima.de

Certificate chain
  • mail.isenberg-lima.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.isenberg-lima.de
Alternative Names
  • autoconfig.isenberg-lima.de
  • autodiscover.isenberg-lima.de
  • mail.isenberg-lima.de
  • mta-sts.isenberg-lima.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-21
Not valid after
2025-01-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
32:AD:4F:08:BF:31:B9:AD:2D:47:BC:91:08:CD:95:BA:ED:B0:20:48:12:13:52:31:DC:31:E8:C7:9B:BA:B3:BC
SHA1
AA:E9:99:85:99:F6:29:F3:34:12:F0:AF:70:44:AA:FA:71:D6:2D:BC
X509v3 extensions
subjectKeyIdentifier
  • 06:E2:71:6E:19:95:87:3C:10:DB:23:23:01:2A:65:59:81:9B:32:43
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Oct 21 08:40:25.410 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B1:EA:A6:FC:C3:FA:24:EF:CA:9E:58:
  • 55:67:38:03:AA:74:57:18:1D:32:A1:AC:59:82:2F:F3:
  • 17:45:0B:E3:AD:02:20:03:CF:7A:FB:58:3C:BC:4D:5A:
  • AA:74:2C:62:6E:0F:77:68:EE:BC:5A:0C:61:16:47:C0:
  • F0:81:41:8B:AE:C1:D4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 21 08:40:25.475 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5E:45:31:FC:37:C8:CF:B7:53:EF:F8:DB:
  • 52:76:5B:07:B5:21:6A:75:39:B6:99:0E:2F:C2:59:F4:
  • 77:DD:A9:7F:02:21:00:C5:8B:97:26:7C:F5:01:39:DD:
  • 64:D6:D4:6A:FC:BE:64:32:9E:D7:4A:4F:52:1C:CF:21:
  • 74:0F:4E:A6:84:26:4A

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