Metrics Dashboard

View detailed SSL/TLS metrics and performance data

Domain

Port

Results

About

The TLS Metrics Dashboard provides a centralized view of all your SSL/TLS monitoring metrics, including certificate expiry timelines, security scores, compliance status, and connection performance. It aggregates data from all monitoring tools into a single operational dashboard for at-a-glance visibility into your TLS infrastructure health.

The dashboard displays key performance indicators (KPIs) including total certificates monitored, average security score, compliance percentage, certificates expiring soon, and active alerts. Trend charts show how metrics change over time, helping you identify patterns and proactively address issues before they impact users.

How to Use

1Access the dashboard from the main navigation menu
2View the summary KPIs at the top for overall TLS health
3Drill down into specific metric categories using the navigation tabs
4Configure alert thresholds and display preferences in the dashboard settings

Use Cases

•Operational Overview: Get instant visibility into TLS health across your entire infrastructure without checking individual tools
•Executive Reporting: Generate summary reports showing TLS security posture, compliance status, and improvement trends for leadership
•Incident Response:** Quickly assess the scope of TLS issues during security incidents by viewing aggregate metrics

•Capacity Planning:** Use trend data to plan certificate renewals, infrastructure upgrades, and security investments

•Team Coordination:** Share dashboard access with DevOps, security, and compliance teams for unified visibility

What Each Metric Comes From

An earlier version of this page reported four of its six metrics as constants — a fixed certificate score, a fixed HSTS result, a stapling result that could only ever be false, and a trend that always said stable. Each figure below is now measured.

1Protocol and cipher scores come from the negotiated version and suite. TLS 1.3 scores highest, 1.2 slightly below, and an AEAD suite outranks a CBC one, so the pair reflects what a client actually received.

2The certificate score is derived from the live expiry date rather than being a fixed number. Time remaining is mapped to a score, which means an expired certificate scores zero and a distant one scores full marks — the opposite of the constant it replaced.

3HSTS is fetched by requesting the site and reading the header. OCSP is not reported at all, since no client library here can observe a stapled response, and the trend is labelled as a single sample rather than claiming stability it cannot know about.

The overall score averages only the three measured components, so nothing inflates it. Every figure here describes one connection at one moment — useful as a snapshot and as a before-and-after comparison, not as a standing property of the host.

Tips & Best Practices

•Customize the dashboard layout to prioritize the metrics most relevant to your role

•Set up scheduled dashboard reports for weekly or monthly management reviews

•Use the alert configuration to surface critical metrics that need immediate attention

•Compare dashboard metrics month-over-month to demonstrate security improvement progress

Technical Details

●Data Sources: Aggregates metrics from Certificate Monitor, Security Scanner, Compliance Checker, and Performance tools

●Refresh Rate: Real-time updates for critical metrics, 5-minute refresh for secondary metrics

●Export: CSV, PDF, and JSON export for integration with external reporting systems

●API: RESTful API endpoints for programmatic access to all dashboard metrics

Frequently Asked Questions

The dashboard shows: total certificates monitored, certificates expiring within 30/60/90 days, average security score, compliance percentage by standard, active alerts, TLS handshake performance, cipher suite distribution, and protocol version usage. All metrics include historical trend data.

Yes, the dashboard is fully customizable. You can add, remove, and rearrange metric widgets, create custom views for different roles (executive, technical, compliance), and save multiple dashboard configurations. Custom metrics can be added via the API integration.

Individual tool reports provide deep detail for specific domains or checks. The dashboard aggregates data across all domains and tools to provide operational-level visibility. Think of it as the "health overview" while individual tools provide the "diagnostic detail."

Because it cannot be measured from here. Python's TLS library exposes no way to observe a stapled response, and the previous version of this page included a stapling metric that was therefore permanently false — which reads as a finding rather than as a limitation. Reporting nothing is the honest option, and the dedicated stapling page covers the question properly.

Nothing beyond this run. It is labelled as a single sample because the page performs one measurement per request and keeps no history, so any trend claim would be invented. A previous version returned a fixed value reading stable, which looked like monitoring output while being a constant. If you want trends, monitor on a schedule and compare the results yourself.

From days remaining on the live certificate, mapped into bands: zero once expired, rising through the final week and month, and full marks beyond ninety days. That makes it respond to the thing that actually goes wrong — approaching or passing expiry — rather than reporting a constant that never changed regardless of the certificate.

Treat it as confirmation of three specific properties on one connection, nothing more. It cannot see cipher lists you never offered, protocols disabled for other client types, or anything on a load balancer terminating TLS ahead of your origin. The score is a useful summary of what a visitor got; it is not a configuration review and should not be reported as one.

Work out what changed before assuming something broke. A drop in the certificate score usually means a renewal moved the expiry date, which is often an improvement even though the number moved. Protocol or cipher changes point at a configuration or edge change. Comparing two runs far enough apart to rule out a transient is the sensible first step, since single measurements vary.

Related Tools

Security Score Expiry Notifier Certificate Monitor Performance Monitor Expiry Notifier Audit Log