SSL-Tools

SSL check results of www.lippescape.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for www.lippescape.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 Wed, 14 Apr 2021 10:24:28 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
www.lippescape.de
92.51.148.211
 -
supported
www.lippescape.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
www.lippescape.de
2a01:488:66:1000:5c33:94d3::1
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=www.lippescape.de

Certificate chain
  • www.lippescape.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • www.lippescape.de
Alternative Names
  • www.lippescape.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-25
Not valid after
2021-05-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2A:25:B6:3A:1C:37:C2:5C:15:8B:4D:C2:BB:39:5B:68:47:7A:37:A4:84:56:D1:AC:C9:5C:72:A9:15:AB:04:E3
SHA1
6F:27:63:DE:1F:2A:4C:DF:E9:D6:84:C0:4A:8B:79:01:CC:C9:89:68
X509v3 extensions
subjectKeyIdentifier
  • 43:9F:27:42:9B:1C:6D:7C:D7:FD:2C:33:EA:F7:0E:8E:8C:2F:81:AA
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Feb 25 09:56:17.366 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9F:CC:AE:12:A3:3E:08:BA:6C:DC:B5:
  • 0E:01:F1:5C:DD:E6:93:47:D4:D4:FD:99:AE:AB:83:7E:
  • BF:8A:D3:0E:A1:02:20:6A:9E:A0:24:80:BB:48:19:07:
  • ED:7E:7E:77:6A:3B:EC:0E:33:65:D6:9F:05:69:BA:DD:
  • B8:6F:4E:4B:D4:04:AA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Feb 25 09:56:17.285 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3E:C9:81:BE:E0:6F:C7:02:54:3A:FB:9A:
  • 9E:D2:D0:06:90:DB:61:BF:E8:15:ED:D0:E5:23:40:8F:
  • 85:87:65:CB:02:20:5C:C6:AD:24:22:3B:40:89:52:37:
  • 00:F7:E3:79:8D:86:57:5F:DA:22:C6:35:FE:4A:70:D6:
  • 68:27:69:6B:B2:0F