Heartbleed Checker

Test for the Heartbleed vulnerability (CVE-2014-0160)

About

The Heartbleed Vulnerability Checker tests whether your server is vulnerable to the critical Heartbleed bug (CVE-2014-0160), a severe OpenSSL vulnerability that allowed attackers to read private memory from vulnerable servers. It sends a specially crafted heartbeat request to detect the vulnerability.

Heartbleed was one of the most significant security vulnerabilities in internet history, affecting approximately 17% of all SSL servers at the time of disclosure. While most servers have been patched, this tool verifies that your server is not still vulnerable.

How to Use

1Enter the domain name and port to test for Heartbleed vulnerability
2Click "Test for Heartbleed" to send the detection probe
3Review the results showing whether the server is vulnerable or patched
4If vulnerable, immediately update OpenSSL and restart all SSL services

Use Cases

•Vulnerability Assessment: Verify that servers are patched against the critical Heartbleed vulnerability
•Legacy System Check:** Test older systems that may not have received security updates

•Security Audit:** Provide evidence of Heartbleed remediation for compliance audits

•Incident Response:** Quickly assess exposure if Heartbleed indicators are detected

•Third-Party Assessment:** Check if services you depend on are vulnerable

Tips & Best Practices

•If your server is vulnerable, treat it as a critical emergency — private keys may have been compromised

•After patching, revoke and reissue all certificates as private keys should be considered compromised

•Check all OpenSSL installations, not just the primary web server

•Monitor for any signs of past exploitation after patching

Technical Details

●CVE: CVE-2014-0160 (Heartbleed) detection

●Method:** Sends crafted TLS heartbeat request to detect memory leak vulnerability

●Affected:** OpenSSL 1.0.1 through 1.0.1f

●Patch:** Fixed in OpenSSL 1.0.1g and later versions

Frequently Asked Questions

Use this tool to test your server. If vulnerable, your private keys should be considered compromised. Check your OpenSSL version — versions 1.0.1 through 1.0.1f are affected. Even if patched now, review logs for signs of past exploitation.

Immediately update OpenSSL to a patched version, restart all SSL services, revoke and reissue all certificates (since private keys may be compromised), change all passwords and secrets, and review logs for signs of past exploitation.

While most servers have been patched, some legacy systems remain vulnerable. Additionally, private keys compromised during the Heartbleed period may still be in attacker hands. Always verify patch status and consider certificate reissuance.

Related Tools

Vulnerability Checkers Heartbleed Checker SSL Test SSL Scanner Certificate Detail SSL Report