HTTP Vulnerability Checks Test

Supported protocols refer to the versions of SSL/TLS protocols that the server can use to establish secure connections with clients, ensuring both security and compatibility across different environments. By regularly monitoring supported protocols, administrators can identify if there are any outdated or insecure protocols enabled on the servers.

The Detailed Diagnosis of this measure shows the list of supported protocols configured for this URL.

This measure refer to the combinations of encryption algorithms, key exchange algorithms, and message authentication algorithms that are supported by a particular SSL/TLS implementation (such as OpenSSL, Microsoft SChannel, or others). When a client (like a web browser) and a server establish an SSL/TLS connection, they negotiate which cipher suite to use based on their respective capabilities.

Different SSL/TLS implementations and versions support different sets of cipher suites. Server administrators often configure their servers to support a specific list of cipher suites based on security best practices, compatibility with clients, and compliance requirements.

The Detailed Diagnosis of this measure shows the list of supported protocols configured for this URL and the ciphers.

This measure refer to cryptographic combinations used in SSL/TLS protocols that are considered weak or vulnerable to security threats. These cipher suites should ideally be avoided or disabled due to known vulnerabilities or weaknesses that could compromise the confidentiality, integrity, or authenticity of the transmitted data.

A value close to 0 is desired.

This measure refers to cryptographic combinations used in SSL/TLS protocols, while not as insecure as those considered "insecure", still exhibit vulnerabilities or weaknesses that could potentially compromise the security of data transmission.

The Detailed Diagnosis of this measure shows the list of supported protocols configured for this URL and the weak ciphers.

Heart bleed refers to a serious security vulnerability that affected the OpenSSL library, which is used to implement the Transport Layer Security (TLS) protocol in many websites and services. The discovery of Heart bleed prompted a widespread effort to patch vulnerable OpenSSL installations. Website administrators were advised to update their OpenSSL libraries and reissue SSL/TLS certificates as a precautionary measure. Users were also encouraged to change their passwords for affected services once they had been patched.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to heart bleed. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

A BEAST (Browser Exploit Against SSL/TLS) attack is a cryptographic exploit that targets the SSL/TLS protocol, specifically targeting the Cipher Block Chaining (CBC) mode of encryption used in SSL and TLS versions prior to TLS 1.1. BEAST attacks are significant because they can potentially expose sensitive information such as session tokens or login credentials, allowing attackers to hijack user sessions or impersonate legitimate users. To mitigate the risk of BEAST attacks, it's essential to use more secure encryption protocols such as TLS 1.2 or later, which employ countermeasures to prevent this type of exploit.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to BEAST attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The POODLE (Padding Oracle On Downgraded Legacy Encryption) attack is a security vulnerability that exploits the SSLv3 (Secure Sockets Layer version 3) protocol. It allows attackers to decrypt sensitive information such as authentication cookies and other secure data exchanged between a web server and a client. POODLE attacks are particularly dangerous because they can be used to intercept and steal sensitive information, such as login credentials or session tokens, from users who are using outdated web browsers or servers that still support SSLv3. To mitigate the risk of POODLE attacks, it's important to disable support for SSLv3 and use more secure protocols such as TLS (Transport Layer Security).

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to POODLE attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

In the ChangeCipherSpec (CVE-2014-0224) attack, a malicious actor can exploit a weakness in the OpenSSL implementation to perform a man-in-the-middle (MitM) attack. The vulnerability allows an attacker to force a connection to downgrade its encryption protocol to a less secure version, enabling the attacker to eavesdrop on supposedly secure communications.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to ChangeCipherSpec (CVE-2014-0224) attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The ROBOT (Return Of Bleichenbacher's Oracle Threat) attack is a vulnerability that arises from servers' responses to RSA encryption attempts. By carefully crafting RSA ciphertexts and analyzing the server's responses, an attacker can infer information about the decryption process and, in some cases, recover the private RSA key.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to ROBOT attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

OCSP stapling allows servers to provide clients with time-stamped, digitally signed OCSP responses during the SSL/TLS handshake, enhancing SSL/TLS certificate revocation checks. This method enhances performance and privacy by removing the necessity for clients to contact the Certificate Authority (CA).

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating whether/not OCSP Stapling is supported on this URL. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The FREAK (Factoring RSA Export Keys) attack exploits a weakness in SSL/TLS protocol implementations that allowed attackers to force clients to use weaker encryption, specifically the RSA export cipher suites. By exploiting FREAK, attackers could potentially intercept and decrypt supposedly secure communications between clients and servers.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to FREAK attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The DROWN (Decrypting RSA with Obsolete and Weakened eNcryption) attack takes advantage of servers that support SSLv2 (Secure Sockets Layer version 2), an outdated and insecure protocol for secure communication. Even if a server primarily uses a more modern version of SSL/TLS, if it supports SSLv2 and shares the same RSA key pair for both SSLv2 and the modern protocol, attackers can exploit the vulnerability.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to DROWN attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The LUCKY13 attack (CVE-2013-0169) is a cryptographic timing attack that targets implementations of the TLS (Transport Layer Security) and DTLS (Datagram Transport Layer Security) protocols. The LUCKY13 attack allows an attacker to gradually recover plaintext from encrypted communication, compromising the confidentiality of the data being transmitted. To mitigate the LUCKY13 attack, affected TLS and DTLS implementations were updated to improve the handling of padding errors and to reduce the risk of timing-based attacks. Additionally, TLS and DTLS clients and servers should be configured to use secure cipher suites and protocols to minimize the risk of exploitation.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to LUCKY13 attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The Winshock vulnerability allows remote attackers to execute arbitrary code on a targeted system by sending specially crafted packets to a Windows server. Essentially, it exploits a flaw in the way Windows handles specially crafted packets during the negotiation of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections.

An attacker could exploit this vulnerability to conduct a variety of malicious activities, such as remotely executing code, installing malware, or performing other unauthorized actions on the vulnerable system. This could potentially lead to a complete compromise of the affected system and pose significant security risks.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to Winshock attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

RC4 (Rivest Cipher 4) is a stream cipher that was widely used for securing internet communications, such as HTTPS connections, in the past.

These vulnerabilities are significant because they undermine the security provided by RC4, potentially allowing attackers to decrypt encrypted communications or recover sensitive information.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the vulnerability of the configured URL with respect to RC4 attacks. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

Forward secrecy is a property of key exchange algorithms in SSL/TLS protocols that ensures session keys derived from the long-term key exchange are not compromised even if the server's private key is compromised in the future.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if the forward secrecy is enabled or not on the URL. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The Server Name Indication (SNI) extension allows a client (such as a web browser) to specify the host name it is attempting to connect to during the SSL/TLS handshake process. This extension is particularly useful in scenarios where a single IP address hosts multiple websites (virtual hosting) that are secured with SSL/TLS using different SSL certificates.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if the Server Name Indication extension is enabled on the URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

HTTP Strict Transport Security (HSTS) is a security mechanism that helps protect websites from certain types of attacks, such as man-in-the-middle (MITM) attacks and protocol downgrade attacks. It forces browsers to interact with the server only over a secure HTTPS connection and prevents them from accessing the site via HTTP, even if the user initially tries to do so.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if HTTP Strict-Transport-Security (HSTS) is enabled in the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

Content Security Policy (CSP) is an important security feature that helps prevent a variety of attacks, such as cross-site scripting (XSS), clickjacking, and data injection attacks, by specifying which content is allowed to load and execute on a web page.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if Content-Security-Policy' security header is available in the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The X-Content-Type-Options HTTP header is a security feature that helps prevent browsers from interpreting files as a different MIME type than the one declared by the server. The purpose of this header is to prevent attacks that rely on the browser automatically determining the content type of a file, which is commonly employed in MIME sniffing.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if X-Content-Type-Options' security header is available on the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The X-Frame-Options HTTP header is a security feature designed to prevent clickjacking attacks by controlling whether a browser can display a web page inside a <frame>, <iframe>, <object>, <embed>, or <applet> element. Clickjacking is a type of attack where a malicious website embeds your website in a hidden or transparent iframe and tricks users into clicking on something different from what they think they're clicking on (e.g., a button that submits a form or makes a purchase).

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if 'X-Frame-Options' security header is available on the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The X-XSS-Protection HTTP header is a security feature that was implemented to provide basic protection against cross-site scripting (XSS) attacks in web browsers. It is a mechanism that attempts to block reflected XSS attacks by enabling the browser to detect and neutralize potentially dangerous script content that could be injected into web pages.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if 'X-XSS-Protection' security header is available on the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The Referrer-Policy HTTP header is a security feature that controls how much information is included in the Referer header when navigating from one page to another, or when making requests (e.g., clicking links, submitting forms, or loading external resources).

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if 'Referrer-Policy' security header is available on the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The Feature-Policy HTTP header is a security feature that allows a website to control which browser features can be used on its pages. It allows you to specify which web platform features a site or iframe is allowed to access, and it gives website owners more control over the capabilities of their content.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if 'Feature-Policy' security header is available on the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The Permissions-Policy HTTP header is a security feature that allows web developers to control which browser features can be accessed by their website or embedded content (such as iframes, images, or external resources).

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating if 'Permissions-Policy' security header is available on the configured URL or not. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

The values reported by this measure and its numeric equivalent are mentioned in the table below:

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the HTTP response status of the URL. However, in the graph of this measure, Measure Values will be represented using the corresponding numeric equivalents only.