upm.edu.my SSL Security Test

Summary of upm.edu.my:443 (HTTPS) SSL Security Test

Provided "as is" without any warranty of any kind.

Date/Time:Nov 4th, 2026 08:33 GMT+0

Source IP/Port:119.40.116.110:443

Protocol:HTTPS

Location:Seri Kembangan, Malaysia

Your final score:

A
B
C
F

B+

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

The server supports the most recent and secure TLS protocol version of TLS 1.3.

Good configuration

Test Results Summary for upm.edu.my

Post-Quantum Cryptography (PQC) Readiness Test
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.
SSL/TLS Certificate Analysis
1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer Sectigo Public Server Authentication CA DV R36 valid until December 24, 2026. 2 certificate chains detected. Show details.
PCI DSS Compliance Test
10 of 28 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) 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, brainpoolP256r1, brainpoolP384r1, brainpoolP512r1 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
NIST and HIPAA Compliance Test
14 of 28 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) 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, brainpoolP256r1, brainpoolP384r1, brainpoolP512r1 and X25519. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling. Show details.
Industry Best Practices Test
No issues related to industry best practices were identified. Show details.

Compliance Summary for upm.edu.my

PCI DSS Compliance Failed: 10 of 28 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) 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, brainpoolP256r1, brainpoolP384r1, brainpoolP512r1 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
HIPAA Compliance Failed: 14 of 28 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) 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, brainpoolP256r1, brainpoolP384r1, brainpoolP512r1 and X25519. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling.
GDPR Compliance Failed: 10 of 28 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2 and TLSv1.3) 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, brainpoolP256r1, brainpoolP384r1, brainpoolP512r1 and X25519. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.