Product

Certificate monitoring features for the public hostnames your team owns.

Start with the operational problem: expiry windows, wrong certificate served, missed warning, hostname inventory, private certificate planning, shared ownership, or audit review after a change.

Run free SSL checkerCompare plans

Workspace preview

Certificate health

Live checks

api.domaintrustwatch.com

Valid
84 days

checkout.example.com

Warning
13 days

idp.example.com

Issuer changed
2h ago
No private keysEmail verificationSigned webhooks

Command center

Map the certificate problem before choosing a feature.

Each feature starts from the operational question: what is being served, who owns the next action, and where proof should remain after the warning.

01Expiry deadlineExplore SSL expiry monitoring

Use expiry monitoring when the question is how much runway a public hostname has before customers see browser warnings. The page explains 30, 14, 7, 3, and 1-day windows and what each warning should trigger.

02Wrong certificate servedCompare certificate change detection

Use change detection after a renewal, CDN move, load-balancer edit, or platform migration. It focuses on the certificate the public endpoint serves, including issuer, SANs, fingerprint, validity, chain depth, and validation state.

03Missed alertCompare alert routing

Use alert routing when warnings need to land in a shared inbox, watched Slack channel, or signed webhook receiver instead of a personal mailbox that may be ignored during the final week.

04Too many hostnamesExplore bulk SSL monitoring

Use bulk import when domains and subdomains already live in a spreadsheet. Dry-run validation catches malformed rows, duplicates, public reachability problems, and quota impact before monitors are created.

05No certificate inventoryBuild an SSL certificate inventory

Use certificate inventory when DNS, CDN, client, and platform lists need owners, environments, criticality, warning windows, and source notes before monitoring starts.

06Private certificatesPlan internal certificate monitoring

Use internal monitoring planning when VPN-only, split-horizon, cluster, origin, or private PKI certificates need an inside-network agent or connector instead of a public probe.

07Shared ownershipExplore team certificate workspaces

Use team workspaces when certificate follow-up needs owners, admins, members, backup coverage, and monitor context that survives client handoffs, team changes, and vacations.

08What changed?Review certificate audit logs

Use audit logs when monitor edits, alert-channel changes, role updates, and workspace settings need to be reviewable after a renewal incident or ownership handoff.

Workspace evidence

Certificate health, routing, and ownership in one workspace.

The overview shows monitored hostnames, renewal pressure, certificate changes, and whether critical warnings reached Slack, email, or webhook routes.

Decision paths

Use the feature pages with the workflow they support.

The product pages are organized around certificate operations: what is being checked, who owns the fix, and where warnings should go.

GuidePublic certificate monitoring workflowStart with the public hostnames users reach, create monitors for recurring risk, and use the checker for one-off renewal or incident reads.DocsExpiry and validation alert workflowSend early expiry reminders to durable channels and route final-week expiry, expired, and validation failures to watched operational paths.ImportBulk import to team ownership workflowValidate a hostname list, tag client or system context, create monitors, and keep renewal responsibility visible to the team.InventoryInventory before monitoring workflowNormalize scattered hostname lists into owners, environments, criticality, warning windows, and notes before public monitoring or internal agent planning.TroubleshootingProbe failure troubleshooting workflowSeparate DNS, TCP, TLS handshake, hostname mismatch, expiry, active-window, and trust-chain failures before assigning the fix.

Feature library

All certificate monitoring feature pages.

Expiry monitoringSSL Certificate Expiry MonitoringCatch SSL certificate expiries with 30, 14, 7, 3, and 1-day warnings, monitored hostname checks, and Slack, email, or webhook alerts.Change detectionCertificate Change DetectionReview issuer, SAN, serial, fingerprint, validity, chain-depth, and validation changes for certificates served by public hostnames.Alert routingAlert RoutingSend certificate expiry, validation, and change warnings to email, Slack incoming webhooks, or signed customer webhooks.Bulk SSL monitoringBulk SSL MonitoringBulk import public certificate monitors with dry-run validation, duplicate checks, tags, and quota impact before creating monitors.Certificate inventorySSL Certificate InventoryBuild an SSL certificate inventory with hostname owners, environments, criticality, warning windows, and import-ready monitoring context.Internal monitoringInternal Certificate Monitoring PlanningPlan private and internal certificate monitoring with inventory, ownership, agent requirements, alert routes, and public-vs-private coverage boundaries.Team workspacesTeam WorkspacesInvite teammates, assign roles, and keep SSL certificate coverage, renewal ownership, alert routing, and audit history visible as responsibilities change.Audit logsAudit LogsSee who changed monitors, alert channels, invites, roles, billing-sensitive settings, and other certificate monitoring configuration.