SSL Server Test: prive.lbbw.de (Powered by Qualys SSL Labs)

SSL Report: prive.lbbw.de (91.198.67.20)

Assessed on: Wed, 17 Sep 2025 09:16:59 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary

Overall Rating

If trust issues are ignored: A

100

Certificate

Protocol Support

Key Exchange

Cipher Strength

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.

This server's certificate is not trusted, see below for details.

This server's certificate is not trusted by major browsers. MORE INFO »

This server supports TLS 1.3. MORE INFO »

Certificate #1: RSA 2048 bits (SHA256withRSA)

Server Key and Certificate #1
Subject	localhost.localdomain Fingerprint SHA256: 39c65f3ccdb657a8b1f1f50c850cf11adcd3f83f7e5ff01dd5e07a47b0612574 Pin SHA256: eUyHtapQ8bGnFfzOj1o1yAM7HhyrQMO7Qg5QaTfqESU=
Common names	localhost.localdomain
Alternative names	- INVALID
Serial Number	189f6f51
Valid from	Fri, 03 Feb 2023 14:31:45 UTC
Valid until	Mon, 31 Jan 2033 14:31:45 UTC (expires in 7 years and 4 months)
Key	RSA 2048 bits (e 65537)
Weak key (Debian)	No
Issuer	localhost.localdomain Self-signed
Signature algorithm	SHA256withRSA
Extended Validation	No
Certificate Transparency	No
OCSP Must Staple	No
Revocation information	None
DNS CAA	No (more info)
Trusted	No NOT TRUSTED (Why?) Mozilla Apple Android Java Windows

Additional Certificates (if supplied)
Certificates provided	1 (946 bytes)
Chain issues	None

Certification Paths


Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server Not in trust store	localhost.localdomain Self-signed Fingerprint SHA256: 39c65f3ccdb657a8b1f1f50c850cf11adcd3f83f7e5ff01dd5e07a47b0612574 Pin SHA256: eUyHtapQ8bGnFfzOj1o1yAM7HhyrQMO7Qg5QaTfqESU= RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server Not in trust store	localhost.localdomain Self-signed Fingerprint SHA256: 39c65f3ccdb657a8b1f1f50c850cf11adcd3f83f7e5ff01dd5e07a47b0612574 Pin SHA256: eUyHtapQ8bGnFfzOj1o1yAM7HhyrQMO7Qg5QaTfqESU= RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server Not in trust store	localhost.localdomain Self-signed Fingerprint SHA256: 39c65f3ccdb657a8b1f1f50c850cf11adcd3f83f7e5ff01dd5e07a47b0612574 Pin SHA256: eUyHtapQ8bGnFfzOj1o1yAM7HhyrQMO7Qg5QaTfqESU= RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server Not in trust store	localhost.localdomain Self-signed Fingerprint SHA256: 39c65f3ccdb657a8b1f1f50c850cf11adcd3f83f7e5ff01dd5e07a47b0612574 Pin SHA256: eUyHtapQ8bGnFfzOj1o1yAM7HhyrQMO7Qg5QaTfqESU= RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server Not in trust store	localhost.localdomain Self-signed Fingerprint SHA256: 39c65f3ccdb657a8b1f1f50c850cf11adcd3f83f7e5ff01dd5e07a47b0612574 Pin SHA256: eUyHtapQ8bGnFfzOj1o1yAM7HhyrQMO7Qg5QaTfqESU= RSA 2048 bits (e 65537) / SHA256withRSA

Click here to expand

Configuration

Protocols
TLS 1.3	Yes
TLS 1.2	Yes
TLS 1.1	No
TLS 1.0	No
SSL 3	No
SSL 2	No

Cipher Suites
# TLS 1.3 (suites in server-preferred order)
TLS_AES_128_GCM_SHA256 (`0x1301`) ECDH secp256r1 (eq. 3072 bits RSA) FS	128
TLS_AES_256_GCM_SHA384 (`0x1302`) ECDH secp256r1 (eq. 3072 bits RSA) FS	256
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (`0xc030`) ECDH secp256r1 (eq. 3072 bits RSA) FS	256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (`0xc02f`) ECDH secp256r1 (eq. 3072 bits RSA) FS	128
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (`0x9e`) DH 2048 bits FS	128
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (`0x9f`) DH 2048 bits FS	256

Handshake Simulation
Android 4.4.2	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Android 5.0.0	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Android 6.0	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Android 7.0	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Android 8.0	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Android 8.1	Protocol or cipher suite mismatch
Android 9.0	Protocol or cipher suite mismatch
BingPreview Jan 2015	Protocol or cipher suite mismatch
Chrome 49 / XP SP3	Protocol or cipher suite mismatch
Chrome 69 / Win 7 R	Protocol or cipher suite mismatch
Chrome 70 / Win 10	Protocol or cipher suite mismatch
Chrome 80 / Win 10 R	Protocol or cipher suite mismatch
Firefox 31.3.0 ESR / Win 7	Protocol or cipher suite mismatch
Firefox 47 / Win 7 R	Protocol or cipher suite mismatch
Firefox 49 / XP SP3	Protocol or cipher suite mismatch
Firefox 62 / Win 7 R	Protocol or cipher suite mismatch
Firefox 73 / Win 10 R	Protocol or cipher suite mismatch
Googlebot Feb 2018	Protocol or cipher suite mismatch
IE 11 / Win 7 R	Protocol or cipher suite mismatch
IE 11 / Win 8.1 R	Protocol or cipher suite mismatch
IE 11 / Win Phone 8.1 R	Protocol or cipher suite mismatch
IE 11 / Win Phone 8.1 Update R	Protocol or cipher suite mismatch
IE 11 / Win 10 R	Protocol or cipher suite mismatch
Edge 15 / Win 10 R	Protocol or cipher suite mismatch
Edge 16 / Win 10 R	Protocol or cipher suite mismatch
Edge 18 / Win 10 R	Protocol or cipher suite mismatch
Edge 13 / Win Phone 10 R	Protocol or cipher suite mismatch
Java 8u161	Protocol or cipher suite mismatch
Java 11.0.3	Protocol or cipher suite mismatch
Java 12.0.1	Protocol or cipher suite mismatch
OpenSSL 1.0.1l R	Protocol or cipher suite mismatch
OpenSSL 1.0.2s R	Protocol or cipher suite mismatch
OpenSSL 1.1.0k R	Protocol or cipher suite mismatch
OpenSSL 1.1.1c R	Protocol or cipher suite mismatch
Safari 6 / iOS 6.0.1	Protocol or cipher suite mismatch
Safari 7 / iOS 7.1 R	Protocol or cipher suite mismatch
Safari 7 / OS X 10.9 R	Protocol or cipher suite mismatch
Safari 8 / iOS 8.4 R	Protocol or cipher suite mismatch
Safari 8 / OS X 10.10 R	Protocol or cipher suite mismatch
Safari 9 / iOS 9 R	Protocol or cipher suite mismatch
Safari 9 / OS X 10.11 R	Protocol or cipher suite mismatch
Safari 10 / iOS 10 R	Protocol or cipher suite mismatch
Safari 10 / OS X 10.12 R	Protocol or cipher suite mismatch
Safari 12.1.2 / MacOS 10.14.6 Beta R	Protocol or cipher suite mismatch
Safari 12.1.1 / iOS 12.3.1 R	Protocol or cipher suite mismatch
Apple ATS 9 / iOS 9 R	Protocol or cipher suite mismatch
Yahoo Slurp Jan 2015	Protocol or cipher suite mismatch
YandexBot Jan 2015	Protocol or cipher suite mismatch
# Not simulated clients (Protocol mismatch)
Android 2.3.7 No SNI ²	Protocol mismatch (not simulated)
Android 4.0.4	Protocol mismatch (not simulated)
Android 4.1.1	Protocol mismatch (not simulated)
Android 4.2.2	Protocol mismatch (not simulated)
Android 4.3	Protocol mismatch (not simulated)
Baidu Jan 2015	Protocol mismatch (not simulated)
IE 6 / XP No FS ¹ No SNI ²	Protocol mismatch (not simulated)
IE 7 / Vista	Protocol mismatch (not simulated)
IE 8 / XP No FS ¹ No SNI ²	Protocol mismatch (not simulated)
IE 8-10 / Win 7 R	Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0	Protocol mismatch (not simulated)
Java 6u45 No SNI ²	Protocol mismatch (not simulated)
Java 7u25	Protocol mismatch (not simulated)
OpenSSL 0.9.8y	Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8	Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4 R	Protocol mismatch (not simulated)
Click here to expand
(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.

Protocol Details
Secure Renegotiation	Supported
Secure Client-Initiated Renegotiation	No
Insecure Client-Initiated Renegotiation	No
BEAST attack	Mitigated server-side (more info)
POODLE (SSLv3)	No, SSL 3 not supported (more info)
POODLE (TLS)	No (more info)
Zombie POODLE	No (more info)
GOLDENDOODLE	No (more info)
OpenSSL 0-Length	No (more info)
Sleeping POODLE	No (more info)
Downgrade attack prevention	Yes, TLS_FALLBACK_SCSV supported (more info)
SSL/TLS compression	No
RC4	No
Heartbeat (extension)	No
Heartbleed (vulnerability)	No (more info)
Ticketbleed (vulnerability)	No (more info)
OpenSSL CCS vuln. (CVE-2014-0224)	No (more info)
OpenSSL Padding Oracle vuln. (CVE-2016-2107)	No (more info)
ROBOT (vulnerability)	No (more info)
Forward Secrecy	Yes (with most browsers) ROBUST (more info)
ALPN	No
NPN	No
Session resumption (caching)	Yes
Session resumption (tickets)	No
OCSP stapling	No
Strict Transport Security (HSTS)	No
HSTS Preloading	Not in: Chrome Edge Firefox IE
Public Key Pinning (HPKP)	No (more info)
Public Key Pinning Report-Only	No
Public Key Pinning (Static)	No (more info)
Long handshake intolerance	No
TLS extension intolerance	No
TLS version intolerance	No
Incorrect SNI alerts	No
Uses common DH primes	No
DH public server param (Ys) reuse	No
ECDH public server param reuse	No
Supported Named Groups	secp256r1, x25519, secp384r1 (server preferred order)
SSL 2 handshake compatibility	Yes
0-RTT enabled	No

HTTP Requests

1 https://prive.lbbw.de/ (HTTP/1.1 404 )
1
	Content-Type	text/html;charset=utf-8
	Content-Language	en
	Content-Length	431
	Date	Wed, 17 Sep 2025 09:12:38 GMT
	Server
	Connection	close
	Set-Cookie	X-LBBW-PERSIST=!/22qvfHlAnlr3tJoGat2lI8Y+jrOQlSAyY56M5d4eAlwHTI6aKptUBfZhyPT1IVK4lrkkGo1zTaieg==; path=/; Httponly; Secure

Miscellaneous
Test date	Wed, 17 Sep 2025 09:12:25 UTC
Test duration	273.784 seconds
HTTP status code	404
HTTP server signature	-
Server hostname	prive.lbbw.de

Why is my certificate not trusted?

There are many reasons why a certificate may not be trusted. The exact problem is indicated on the report card in bright red. The problems fall into three categories:

Invalid certificate
Invalid configuration
Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

It is used before its activation date
It is used after its expiry date
Certificate hostnames don't match the site hostname
It has been revoked
It has insecure signature
It has been blacklisted

2. Invalid configuration

In some cases, the certificate chain does not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.

3. Unknown Certificate Authority

In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain its own trust store; instead we use the store maintained by Mozilla.

If we mark a web site as not trusted, that means that the average web user's browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your browser. Such special cases do not work for the general public, however, and this is what we indicate on our report card.

4. Interoperability issues

In some rare cases trust cannot be established because of interoperability issues between our code and the code or configuration running on the server. We manually review such cases, but if you encounter such an issue please feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.

SSL Report v2.4.1

Copyright © 2009-2025 Qualys, Inc. All Rights Reserved. Privacy Policy.	Terms and Conditions
Try Qualys for free! Experience the award-winning Qualys Cloud Platform and the entire collection of Qualys Cloud Apps, including certificate security solutions.