TLS versions, certificate expiry, and HTTPS redirects in one browser-style check
Why teams bundle TLS hygiene with headers and DNS when they want a release-week score,not a raw certificate dump or a disconnected header list.
What “TLS in the score” actually means here
Negotiated protocol versions, certificate validity windows, and obvious chain issues are inputs to the same published 0–100 model as everything else. We are not replacing a dedicated TLS lab or compliance audit; we are answering whether a typical browser handshake to your public site looks broadly sane today.
If you want the score framed as a product story, start from the website security score landing page, then run a live scan on the homepage.
Redirects matter as much as ciphers
Port-80 behavior and upgrade paths often show up in incident postmortems even when ciphers look fine on 443 alone. Scorifya records what we can observe from the outside about HTTP to HTTPS upgrades when the listener exists,still passive configuration review, not an authenticated crawl.
For a plain-language framing of what the number does and does not claim, see is my website secure? before you share results with non-technical stakeholders.
When you outgrow ad-hoc checks
The public scanner stays useful for spot checks; Scorifya Pro removes the hourly fair-use cap for your account and adds JSON, CSV, and PDF exports so you can attach the same structured results to tickets or release notes.
Try a scan on scorifya.com, read how we score, or see Pro for unlimited scans and exports.
Get a weekly digest
New KEV CVE notices and (later) score changes on the domains you watch. One email a week, easy unsubscribe. We don't share or sell your address.
By subscribing you confirm you can receive transactional security updates from Scorifya at this email.