Summary of enterpriseenrollment.kroger.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 22:27 GMT+0
Source IP/Port:52.182.141.192:443
Protocol:HTTPS
Location:Des Moines, United States
Your final score:
- A
- B
- C
- F
F
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
Test Results Summary for enterpriseenrollment.kroger.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 issuer Microsoft TLS G2 RSA CA OCSP 02 valid until February 24, 2027. 1 certificate chain detected. Show details.
- 6 of 14 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. All supported elliptic curves are compliant with PCI DSS: P-384 and P-256. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack. Show details.
- 6 of 14 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-384 and P-256. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support TLS 1.3. Show details.
- 1 issue related to industry best practices was identified: server does not support TLS 1.3. Show details.
Compliance Summary for enterpriseenrollment.kroger.com
- PCI DSS Compliance Failed: 6 of 14 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. All supported elliptic curves are compliant with PCI DSS: P-384 and P-256. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack.
- HIPAA Compliance Failed: 6 of 14 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-384 and P-256. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support TLS 1.3.
- GDPR Compliance Failed: 6 of 14 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. All supported elliptic curves are compliant with GDPR: P-384 and P-256. There are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
