| Site | Port | Availability | Certificate | TLS | Issuer | Expires | Last checked |
|---|---|---|---|---|---|---|---|
| certtracker.12squared.com | 443 | Online | Valid | TLSv1.3 | 2027-01-06 | 2026-10-15 18:00 | |
| github.com ⚠ 1 | 443 | Online | Valid | TLSv1.3 | 2026-11-29 | 2026-10-15 18:00 | |
| sha1-intermediate.badssl.com ⚠ 4 | 443 | Online | Expired | TLSv1.2 | 2020-05-30 | 2026-10-15 17:53 | |
| cbc.badssl.com ⚠ 2 | 443 | Online | Valid | TLSv1.2 | 2026-12-28 | 2026-10-15 17:50 | |
| tls-v1-1.badssl.com ⚠ 1 | 443 | Online | Valid | TLSv1.2 | 2026-12-28 | 2026-10-15 18:00 | |
| wrong.host.badssl.com ⚠ 2 | 443 | Online | Valid | TLSv1.2 | 2026-12-28 | 2026-10-15 18:00 | |
| dh1024.badssl.com ⚠ 1 | 443 | Online | Valid | TLSv1.2 | 2026-12-28 | 2026-10-15 18:00 |
Monitor view — Demo account
This is live data from a real CertTracker account. Your account would show your own certificates here.
Click any row to see the full TLS audit — protocol & cipher walk, OCSP stapling,
HSTS header, chain-signature analysis (catches SHA-1 intermediates), forward-secrecy roll-up,
compliance pass/fail (PCI‑DSS 4.0, NIST 800‑52r2, Mozilla Modern), CAA records, and
any active advisories.
sha1-intermediate.badssl.com— weak-signature intermediate caught by the chain walktls-v1-1.badssl.com— deprecated-protocol-only endpoint flagged as “modern clients cannot connect”dh1024.badssl.com— weak DH key caught even though the regular handshake fails