Summary of pr.marbellaclub.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 8th, 2026 16:11 GMT+0
Source IP/Port:178.238.239.121:443
Protocol:HTTPS
Location:Lauterbourg, France
Your final score:
- A
- B
- C
- F
C
The SSL certificate is untrusted. Modern browsers will display a security warning message to all website visitors. Review and remediate highlighted issues.
Non-compliant with PCI DSS requirements
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for pr.marbellaclub.com
- The server on the tested port is currently not prepared for post-quantum key exchange. The server’s certificate chain relies entirely on classical signature algorithms without post-quantum support. Show details.
- 1 SSL/TLS end-entity certificate detected: the first certificate is an untrusted RSA 2048 bits certificate with unknown issuer valid until September 24, 2025. 1 certificate chain detected. Show details.
- 8 of 17 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with PCI DSS: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack. Show details.
- 9 of 17 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with HIPAA: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with HIPAA: certificates are self-signed, certificate does not include an OCSP responder url. Show details.
- 2 issues related to industry best practices were identified: HTTP site does not redirect to the HTTPS version, server does not provide HSTS. Show details.
Compliance Summary for pr.marbellaclub.com
- PCI DSS Compliance Failed: 8 of 17 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with PCI DSS: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack.
- HIPAA Compliance Failed: 9 of 17 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with HIPAA: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with HIPAA: certificates are self-signed, certificate does not include an OCSP responder url.
- GDPR Compliance Failed: 8 of 17 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with GDPR: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
