Summary of s28.gcv.aia.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 07:46 GMT+0
Source IP/Port:20.195.59.143:443
Protocol:HTTPS
Location:Singapore, Singapore
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
CA of your SSL certificate is distrusted by Google Chrome and Mozilla Firefox.
Misconfiguration or weakness
The server has TLS 1.0 enabled. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 30th of June 2018.
Non-compliant with PCI DSS and NIST
The server has TLS 1.1 enabled. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 31st of March 2025.
Non-compliant with PCI DSS and NIST
Certificate chain relies on expired certificate, it can break connection for some clients.
Misconfiguration or weakness
Test Results Summary for s28.gcv.aia.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 AIA-GOEQXPWICA010-CA valid until June 10, 2029. 1 certificate chain detected. Show details.
- 6 of 12 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-384, P-521, 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.
- 6 of 12 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384, P-521, X25519 and X448. There are 2 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, server does not support TLS 1.3. Show details.
- 4 issues related to industry best practices were identified: certificates have a validity period of more than 398 days, server does not support TLS 1.3, server supports client-initiated secure renegotiation, certificate chain rely on expired certificate. Show details.
Compliance Summary for s28.gcv.aia.com
- PCI DSS Compliance Failed: 6 of 12 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-384, P-521, 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: 6 of 12 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384, P-521, X25519 and X448. There are 2 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, server does not support TLS 1.3.
- GDPR Compliance Failed: 6 of 12 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256, P-384, P-521, X25519 and X448. There are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
