Security Headers & TLS Expiry Checker
Pricing
$10.00 / 1,000 site auditeds
Security Headers & TLS Expiry Checker
Check HTTP security-header presence (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) and TLS certificate expiry for a list of sites. Score reflects header presence only - an informational signal, not a security audit or verdict.
Pricing
$10.00 / 1,000 site auditeds
Rating
0.0
(0)
Developer
Tom
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Security
Limited permissionsShare
Check HTTP security-header presence and TLS certificate expiry for a list of sites.
The score reflects header presence only. It is an informational signal, not a security audit, pentest or verdict.
How it works
- One lightweight request per site (HEAD, with GET fallback when HEAD is not supported) to read response headers.
- Checks presence of six common security headers: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
- Opens a TLS handshake to read the certificate's expiry date and days remaining.
- Score = share of the six headers present, as a percentage.
Input
{"urls": ["https://example.com"]}
Up to 500 sites per run. Only public HTTPS/HTTP destinations are accepted; private and loopback addresses are refused.
Output
One dataset row per site: URL, per-header presence, score, TLS expiry date and days remaining, plus errors where a site could not be reached.
Charging
Pay per event: one site-audited event per site checked ($0.01). Unreachable sites that fail before any check completes are not charged.
Limitations
- Presence-only checks. A present header can still be misconfigured; an absent header can be mitigated elsewhere (e.g. at a CDN).
- Some sites block HEAD requests or bots; the GET fallback covers most, but results for blocking sites may be incomplete.