SSL-Tools

SSL check results of lmsk.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for lmsk.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 Fri, 19 Apr 2024 15:32:51 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.lmsk.de
2a01:239:28b:b000::1
 10
supported
mail.lmsk.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
mail.lmsk.de
212.132.120.43
 10
supported
mail.lmsk.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.lmsk.de

Certificate chain
  • mail.lmsk.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.lmsk.de
Alternative Names
  • autoconfig.lmsk.de
  • autodiscover.lmsk.de
  • mail.lmsk.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-14
Not valid after
2024-07-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
69:AC:74:05:DC:D0:71:42:1F:26:48:CC:5A:F0:45:20:11:8D:A6:57:3C:E0:56:9D:E2:B9:11:89:A7:45:48:E6
SHA1
BB:C9:8D:60:D9:07:51:1E:F2:67:45:36:2E:52:46:CA:6E:E7:A8:44
X509v3 extensions
subjectKeyIdentifier
  • 33:B7:73:6E:9A:5A:00:33:D3:B6:60:C7:BC:62:A2:B9:81:EA:EA:69
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 : Apr 14 18:54:43.990 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E0:3E:36:88:40:4B:E8:29:63:76:75:
  • 5E:3E:E1:6C:F1:12:19:EB:F0:D3:05:C0:A6:F5:3C:2D:
  • 90:AB:DC:0B:08:02:21:00:9A:40:65:97:E7:BA:3C:31:
  • 2C:F7:9A:83:34:20:2E:3E:32:5B:EF:0C:93:54:DE:7F:
  • 39:A2:39:F8:96:07:DC:83
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 14 18:54:44.185 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F0:28:0B:4D:B5:36:FF:B0:36:9B:BD:
  • FF:B5:E1:22:42:26:F5:64:AE:D6:8B:49:14:C2:E7:F5:
  • 99:91:6A:0D:94:02:21:00:80:83:3D:81:04:9B:99:6D:
  • 50:6E:31:1A:CC:EC:10:29:81:08:6D:8A:0F:ED:D8:58:
  • A6:A8:47:28:D5:DF:07:DF