Monitoring certificates for customers and projects
Monitor SSL certificates across many customers and projects. Tag each domain by client or environment, filter the dashboard, onboard with one CSV upload.
A flat list of hostnames stops being readable the moment it mixes your own sites with three customers' staging and production environments. CertWatchr keeps it organised with labels, tags and filters, and lets you onboard a whole customer with one CSV file.
Name each domain with a label
The label is the human-readable name shown in every table and in every alert e-mail. Put the customer or project in it, so a warning at 3 a.m. tells you whose site it is without decoding the hostname:
| Hostname | Label | Tags |
|---|---|---|
shop.acme.com |
Acme Corp – shop | acme,prod,web |
api.acme.com:8443 |
Acme Corp – API | acme,prod,api |
staging.acme.com |
Acme Corp – staging | acme,staging |
Tag by customer, environment and service
Every domain takes up to ten comma-separated tags. A scheme that works for most teams:
- customer:
acme,customer-b - environment:
prod,staging,dev - service:
web,mail,api
Tags are lowercased and de-duplicated for you, so Prod, Web and web,prod are the same. On the
domain list they appear under the hostname; click one to see only the domains carrying it.
Filter the list
The filter bar has three controls that combine and stay in effect while you page:
- Search: any part of the hostname or label.
- Status: only what is warning, critical or in error — the "what needs attention today" view.
- Tag: one customer, one environment, one service.
The filters are in the page URL, so /domains?tag=acme&status=warning can be bookmarked or shared
with a colleague as "Acme's problems".
Onboard a customer with one file
Use Add domain → Import with a CSV like this:
hostname,port,label,tags,alert_at_days
shop.acme.com,443,Acme Corp – shop,"acme,prod,web",30
api.acme.com,8443,Acme Corp – API,"acme,prod,api",14
Only hostname is required. Rows with mistakes are reported individually and the rest are
imported. To hand a customer their list, or move it elsewhere, Export downloads everything
including the latest check results. Details in Adding domains.
Different warning lead times per customer
Each domain has its own alert threshold, so a customer with a slow change process can get 60 days' notice while an internal staging host gets 14. Free accounts can set up to 30 days; Starter and Pro up to 365.
Routing alerts per customer
E-mail alerts always go to your account address, and a webhook is one URL and one format per account. Every alert names the hostname, so to send different customers' alerts to different Slack channels, point the webhook at a small endpoint of your own that looks at the hostname and forwards accordingly. See Webhooks.
Quick reference
| Field | Purpose | Example values |
|---|---|---|
label |
Name shown in tables and alerts | Acme Corp – shop |
tags |
Comma-separated, for filtering | acme,prod,web |
alert_at_days |
Days before expiry to warn | 30, 60 |
check_frequency |
How often to check | daily, weekly, custom (Pro) |