SSL Security Test of wordpress.rutgers.edu

Test the SSL/TLS stack of your web or email server for security, cryptographic flaws and misconfigurations, and compliance with NIST & HIPAA
Free online tool with PDF report
  • Web Server SSL/TLS Security
  • Post-Quantum Cryptography (PQC) Readiness
  • Email Server SSL/TLS Security
  • PCI DSS, HIPAA & NIST Compliance
  • SSL Certificate Validity
  • Best-Practices Compliance
Free online tool with PDF report
181,650,352 tests performed
Provided "as is" without any warranty of any kind
130
tests
running
65,759
tests
in 24 hours
Tests in 24 Hours
Share this report:

Summary of wordpress.rutgers.edu:443 (HTTPS) SSL Security Test

Provided "as is" without any warranty of any kind.
This test was made 2713 days ago and may be outdated
Refresh Test
Date/Time:Dec 25th, 2018 21:01 GMT+0
Source IP/Port:128.6.194.156:443
Protocol:HTTPS
Location:New Brunswick, United StatesUnited States
Your final score:
  • A
  • B
  • C
  • F
F

Executive Summary for wordpress.rutgers.edu

  • SSL/TLS Certificate Analysis
    1 SSL/TLS end-entity certificate(s) detected: the first certificate is an untrusted RSA 1024 bits certificate with unknown issuer valid until February 12, 2014. 1 certificate chain(s) detected. Show details.
  • PCI DSS Compliance Test
    7 of 31 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.1 and TLSv1.2) as well as non-compliant protocols (TLSv1.0). There are 4 more issue(s) which make the server non-compliant with PCI DSS: certificates' key are weak, certificates have a weak signature, certificates are untrusted, diffie-hellman parameter weak. Show details.
  • NIST and HIPAA Compliance Test
    13 of 31 supported cipher suites are not compliant with NIST and HIPAA. The server supports only NIST and HIPAA compliant protocols: TLSv1.0, TLSv1.1 and TLSv1.2. There are 7 more issue(s) which make the server non-compliant with NIST and HIPAA: certificates are self-signed, certificate does not provide OCSP revocation information, certificates' key are weak, certificates have a weak signature, diffie-hellman parameter weak, no support for common curves, EC point format extension. Show details.
  • Industry Best Practices Test
    3 issue(s) related to industry best practices were identified: server does not support TLS 1.3, server does not have cipher preference, server does not provide HSTS. Show details.
Please wait. Data is loading...
Please wait. Data is loading...
Share this report: