SSL Server Test: remoteexperience.festo.com (Powered by Qualys SSL Labs)

SSL Report: remoteexperience.festo.com (141.130.250.181)

Assessed on: Fri, 18 Jul 2025 05:16:54 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: B

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 does not support Forward Secrecy with the reference browsers. Grade capped to B. MORE INFO »

This server does not support TLS 1.3. MORE INFO »

HTTP Strict Transport Security (HSTS) with long duration deployed on this server. MORE INFO »

Certificate #1: RSA 4096 bits (SHA256withRSA)

Server Key and Certificate #1
Subject	remoteexperience.festo.com Fingerprint SHA256: 831d00bea2d65e26441fa68d4bb14ede0f37101a50e39ccfad303011251fa394 Pin SHA256: ndFmM7Pv0LZqJKPjht5OjlCaOARUHvOrcFWS4scxB5U=
Common names	remoteexperience.festo.com
Alternative names	remoteexperience.festo.com
Serial Number	3700090ab245fd32e7c67d21a0000300090ab2
Valid from	Wed, 16 Jul 2025 06:40:33 UTC
Valid until	Fri, 16 Jul 2027 06:40:33 UTC (expires in 1 year and 11 months)
Key	RSA 4096 bits (e 65537)
Weak key (Debian)	No
Issuer	FestoSubCA01 AIA: http://crl.festo.company/CertEnroll/FestoSubCA01(3).crt
Signature algorithm	SHA256withRSA
Extended Validation	No
Certificate Transparency	No
OCSP Must Staple	No
Revocation information	CRL, OCSP CRL: http://crl.festo.company/CertEnroll/FestoSubCA01(3).crl OCSP: http://ocsp.festo.company/ocsp
Revocation status	Unchecked (only trusted certificates can be checked)
DNS CAA	No (more info)
Trusted	No NOT TRUSTED (Why?) Mozilla Apple Android Java Windows

Additional Certificates (if supplied)
Certificates provided	4 (7763 bytes)
Chain issues	Extra certs, Contains anchor
#2
Subject	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k=
Valid until	Sun, 20 Feb 2028 09:12:24 UTC (expires in 2 years and 7 months)
Key	RSA 4096 bits (e 65537)
Issuer	FestoGlobalRootCA
Signature algorithm	SHA256withRSA
#3
Subject	FestoGlobalRootCA Not in trust store Fingerprint SHA256: 87f5b5ede6e2f7d4d67aec769e32e7a33b3c91a2d13519801c66034b33e7b37a Pin SHA256: ATOXmPPj3/0NqdIvVLniH6ZALNw2kxeJ/ItLpvBhkZs=
Valid until	Fri, 09 Mar 2040 10:42:07 UTC (expires in 14 years and 7 months)
Key	RSA 4096 bits (e 65537)
Issuer	FestoGlobalRootCA Self-signed
Signature algorithm	SHA256withRSA
#4
Subject	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k=
Valid until	Sun, 20 Feb 2028 09:12:24 UTC (expires in 2 years and 7 months)
Key	RSA 4096 bits (e 65537)
Issuer	FestoGlobalRootCA
Signature algorithm	SHA256withRSA

Certification Paths


Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server	remoteexperience.festo.com Fingerprint SHA256: 831d00bea2d65e26441fa68d4bb14ede0f37101a50e39ccfad303011251fa394 Pin SHA256: ndFmM7Pv0LZqJKPjht5OjlCaOARUHvOrcFWS4scxB5U= RSA 4096 bits (e 65537) / SHA256withRSA
2	Sent by server	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k= RSA 4096 bits (e 65537) / SHA256withRSA
3	Sent by server Not in trust store	FestoGlobalRootCA Self-signed Fingerprint SHA256: 87f5b5ede6e2f7d4d67aec769e32e7a33b3c91a2d13519801c66034b33e7b37a Pin SHA256: ATOXmPPj3/0NqdIvVLniH6ZALNw2kxeJ/ItLpvBhkZs= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server	remoteexperience.festo.com Fingerprint SHA256: 831d00bea2d65e26441fa68d4bb14ede0f37101a50e39ccfad303011251fa394 Pin SHA256: ndFmM7Pv0LZqJKPjht5OjlCaOARUHvOrcFWS4scxB5U= RSA 4096 bits (e 65537) / SHA256withRSA
2	Sent by server	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k= RSA 4096 bits (e 65537) / SHA256withRSA
3	Sent by server Not in trust store	FestoGlobalRootCA Self-signed Fingerprint SHA256: 87f5b5ede6e2f7d4d67aec769e32e7a33b3c91a2d13519801c66034b33e7b37a Pin SHA256: ATOXmPPj3/0NqdIvVLniH6ZALNw2kxeJ/ItLpvBhkZs= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server	remoteexperience.festo.com Fingerprint SHA256: 831d00bea2d65e26441fa68d4bb14ede0f37101a50e39ccfad303011251fa394 Pin SHA256: ndFmM7Pv0LZqJKPjht5OjlCaOARUHvOrcFWS4scxB5U= RSA 4096 bits (e 65537) / SHA256withRSA
2	Sent by server	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k= RSA 4096 bits (e 65537) / SHA256withRSA
3	Sent by server Not in trust store	FestoGlobalRootCA Self-signed Fingerprint SHA256: 87f5b5ede6e2f7d4d67aec769e32e7a33b3c91a2d13519801c66034b33e7b37a Pin SHA256: ATOXmPPj3/0NqdIvVLniH6ZALNw2kxeJ/ItLpvBhkZs= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server	remoteexperience.festo.com Fingerprint SHA256: 831d00bea2d65e26441fa68d4bb14ede0f37101a50e39ccfad303011251fa394 Pin SHA256: ndFmM7Pv0LZqJKPjht5OjlCaOARUHvOrcFWS4scxB5U= RSA 4096 bits (e 65537) / SHA256withRSA
2	Sent by server	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k= RSA 4096 bits (e 65537) / SHA256withRSA
3	Sent by server Not in trust store	FestoGlobalRootCA Self-signed Fingerprint SHA256: 87f5b5ede6e2f7d4d67aec769e32e7a33b3c91a2d13519801c66034b33e7b37a Pin SHA256: ATOXmPPj3/0NqdIvVLniH6ZALNw2kxeJ/ItLpvBhkZs= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server	remoteexperience.festo.com Fingerprint SHA256: 831d00bea2d65e26441fa68d4bb14ede0f37101a50e39ccfad303011251fa394 Pin SHA256: ndFmM7Pv0LZqJKPjht5OjlCaOARUHvOrcFWS4scxB5U= RSA 4096 bits (e 65537) / SHA256withRSA
2	Sent by server	FestoSubCA01 Fingerprint SHA256: 77d0c0a4d9a1650d0bdb25807049b99bf46403600d956da0e5dcf6562c30b445 Pin SHA256: 7mHiDillgRxiph8oHkq7d/s5PK/yABVM4ovyrn+vL2k= RSA 4096 bits (e 65537) / SHA256withRSA
3	Sent by server Not in trust store	FestoGlobalRootCA Self-signed Fingerprint SHA256: 87f5b5ede6e2f7d4d67aec769e32e7a33b3c91a2d13519801c66034b33e7b37a Pin SHA256: ATOXmPPj3/0NqdIvVLniH6ZALNw2kxeJ/ItLpvBhkZs= RSA 4096 bits (e 65537) / SHA256withRSA

Click here to expand

Configuration

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

Cipher Suites
# TLS 1.2 (suites in server-preferred order)
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (`0x9f`) DH 4096 bits FS	256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (`0x9e`) DH 4096 bits FS	128
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (`0x39`) DH 4096 bits FS WEAK	256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (`0x33`) DH 4096 bits FS WEAK	128
TLS_RSA_WITH_AES_256_GCM_SHA384 (`0x9d`) WEAK	256
TLS_RSA_WITH_AES_128_GCM_SHA256 (`0x9c`) WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA (`0x35`) WEAK	256
TLS_RSA_WITH_AES_128_CBC_SHA (`0x2f`) WEAK	128

Handshake Simulation
Android 4.4.2	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
Android 5.0.0	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 DH 4096 FS
Android 6.0	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 DH 4096 FS
Android 7.0	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Android 8.0	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Android 8.1	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Android 9.0	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
BingPreview Jan 2015	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
Chrome 49 / XP SP3	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_128_GCM_SHA256 No FS
Chrome 69 / Win 7 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Chrome 70 / Win 10	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Chrome 80 / Win 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Firefox 31.3.0 ESR / Win 7	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Firefox 47 / Win 7 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Firefox 49 / XP SP3	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Firefox 62 / Win 7 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Firefox 73 / Win 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Googlebot Feb 2018	RSA 4096 (SHA256)	TLS 1.2	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
IE 11 / Win 7 R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
IE 11 / Win 8.1 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
IE 11 / Win Phone 8.1 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_CBC_SHA No FS
IE 11 / Win Phone 8.1 Update R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
IE 11 / Win 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
Edge 15 / Win 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Edge 16 / Win 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Edge 18 / Win 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Edge 13 / Win Phone 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
Java 8u161	Client does not support DH parameters > 2048 bits RSA 4096 (SHA256) \| TLS 1.2 \| TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 \| DH 4096
Java 11.0.3	Client does not support DH parameters > 2048 bits RSA 4096 (SHA256) \| TLS 1.2 \| TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 \| DH 4096
Java 12.0.1	Client does not support DH parameters > 2048 bits RSA 4096 (SHA256) \| TLS 1.2 \| TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 \| DH 4096
OpenSSL 1.0.1l R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
OpenSSL 1.0.2s R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
OpenSSL 1.1.0k R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
OpenSSL 1.1.1c R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
Safari 6 / iOS 6.0.1	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Safari 7 / iOS 7.1 R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Safari 7 / OS X 10.9 R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Safari 8 / iOS 8.4 R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Safari 8 / OS X 10.10 R	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 4096 FS
Safari 9 / iOS 9 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Safari 9 / OS X 10.11 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Safari 10 / iOS 10 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Safari 10 / OS X 10.12 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Safari 12.1.2 / MacOS 10.14.6 Beta R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Safari 12.1.1 / iOS 12.3.1 R	RSA 4096 (SHA256)	TLS 1.2 > http/1.1	TLS_RSA_WITH_AES_256_GCM_SHA384 No FS
Apple ATS 9 / iOS 9 R	Server sent fatal alert: handshake_failure
Yahoo Slurp Jan 2015	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
YandexBot Jan 2015	RSA 4096 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 4096 FS
# 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) TLS 1.2 : `0x0035`
GOLDENDOODLE	No (more info) TLS 1.2 : `0x0035`
OpenSSL 0-Length	No (more info) TLS 1.2 : `0x0035`
Sleeping POODLE	No (more info) TLS 1.2 : `0x0035`
Downgrade attack prevention	Unknown (requires support for at least two protocols, excl. SSL2)
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	With some browsers (more info)
ALPN	Yes http/1.1
NPN	No
Session resumption (caching)	Yes
Session resumption (tickets)	Yes
OCSP stapling	No
Strict Transport Security (HSTS)	Yes max-age=15768000
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, ECDHE suites not supported
Supported Named Groups	-
SSL 2 handshake compatibility	Yes

HTTP Requests

1 https://remoteexperience.festo.com/ (HTTP/1.1 302 Found)
1
	Date	Fri, 18 Jul 2025 05:15:22 GMT
	Server	Apache
	Location	/wbm/login/
	Content-Length	0
	X-Frame-Options	sameorigin
	Vary	Accept-Language,Cookie
	Content-Language	en
	X-Content-Type-Options	nosniff
	X-XSS-Protection	1; mode=block
	Strict-Transport-Security	max-age=15768000
	Content-Security-Policy	frame-ancestors 'self';
	Cache-Control	no-cache, no-store, must-revalidate, private
	Pragma	no-cache
	Connection	close
	Content-Type	text/html; charset=utf-8

2 https://remoteexperience.festo.com/wbm/login/ (HTTP/1.1 200 OK)
2
	Date	Fri, 18 Jul 2025 05:15:23 GMT
	Server	Apache
	Content-Length	5902
	Expires	Fri, 18 Jul 2025 05:15:23 GMT
	Cache-Control	no-cache, no-store, must-revalidate, private
	Vary	Cookie,Accept-Language,Accept-Encoding
	X-Frame-Options	sameorigin
	Content-Language	en
	X-Content-Type-Options	nosniff
	X-XSS-Protection	1; mode=block
	Set-Cookie	csrftoken=eVyLECCILXG5qnht51JQduyB1djOf0voSXOVpQzsr2qGgsu36yOykp1YitfUcrnl; expires=Fri, 17 Jul 2026 05:15:23 GMT; HttpOnly; Max-Age=31449600; Path=/; SameSite=Lax; Secure
	Set-Cookie	sessionid=brqui7zdv8yslmd4nnpa9uwweyxauxfj; HttpOnly; Path=/; SameSite=Lax; Secure
	Strict-Transport-Security	max-age=15768000
	Content-Security-Policy	frame-ancestors 'self';
	Pragma	no-cache
	Connection	close
	Content-Type	text/html; charset=utf-8

Miscellaneous
Test date	Fri, 18 Jul 2025 05:15:11 UTC
Test duration	103.237 seconds
HTTP status code	200
HTTP server signature	Apache
Server hostname	remoteexperience.festo.com

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.