chromium/badssl.com

:lock: Memorable site for testing clients against bad SSL configs.

View on GitHub ↗Jump to charts ↓

chromium/badssl.com has 3k+ stars and 200+ forks on GitHub, is written in HTML, and was last pushed on Jun 1, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 22nd, 2026
Created on April 7th, 2015
Open Issues & Pull Requests: 210 (+0)
GitHub issues: Enabled
Number of forks: 205
Total Stargazers: 3,051 (+0)
Total Subscribers: 49 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.0 days
Mean response time: 153.6 days
90th percentile: 496.2 days
Tracked items: 26

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 790 days
Stale 30+ days: 19
Stale 90+ days: 15

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs-acme (3)
  • needs-prod-cert (1)
  • subdomain (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

badssl.com is a testing resource that provides a collection of subdomains configured with intentionally bad SSL/TLS setups for validating how clients handle certificate errors and security issues.

The project solves the problem of testing browser and client behavior against misconfigured SSL certificates and protocols. It hosts multiple subdomains, each demonstrating a specific failure mode: self-signed certificates, expired certificates, mixed content, weak ciphers like RC4, and HSTS configurations. Rather than requiring developers to set up their own broken certificate infrastructure, badssl.com provides a stable, publicly accessible testing ground where security teams can verify that their clients properly reject or warn about problematic certificates.

The tool is designed for manual testing of security UI in web clients, making it suitable for browser developers, security researchers, and anyone building applications that need to validate SSL/TLS handling. It works best as a reference implementation for testing certificate validation logic rather than as an automated testing framework. The project explicitly disclaims being suitable for automated testing and notes that subdomains may change without notice, though most are expected to remain stable. For teams needing guaranteed stability, the README suggests forking and hosting a private copy.

Development on the project involves contributions from multiple organizations including Mozilla and Google Chrome, with external contributors implementing various subdomains and test pages. The infrastructure is hosted on Google Cloud and maintained across several maintainers with expertise in browser security. The project accepts community contributions and encourages filing issues for specific use cases or documentation needs.