Monitoring certificates for customers and projects

Once you monitor sites for several customers, a plain list of hostnames gets hard to read. Labels, tags and filters keep it tidy, and a CSV file brings in a whole customer at once.

Give every domain a label

The label appears in every table and every alert. Put the customer or project in it, so a warning at 3 a.m. tells you straight away whose site it is:

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

Each domain takes up to ten tags. This scheme works for most agencies:

• customer — acme, customer-b
• environment — prod, staging, dev
• service — web, mail, api

Case and order do not matter. Click a tag in the domain list to show only those domains.

Filter the list

Combine Search, Status and Tag in the filter bar. For example, Status: warning plus Tag: acme shows everything at Acme that needs attention.

The filters are part of the address, so you can bookmark /domains?tag=acme&status=warning or send it to a colleague.

Add a customer with one file

On Starter and Pro, use Import from CSV in the menu next to Add domain:

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. Faulty rows are listed, the rest are imported. Export as CSV gives you the full list back, with the latest results. Details: Adding domains.

Give each customer their own warning time

The alert threshold is set per domain. A customer with a slow change process can get 60 days' notice, an internal staging host 14. On Free it is fixed at 30 days.

Send alerts to the right place

E-mail alerts go to your account address. On Pro you can add up to 10 webhooks (25 on Team) — your Slack channel, a PagerDuty bridge, a customer's own system. Every webhook receives every alert; you cannot route by tag.

To send each customer's alerts to a different channel, point one webhook at a small service of your own. Every alert contains the hostname, so the service can forward it to the right place. See Webhooks.

Show a customer their certificates (Pro)

1. Go to Settings → Client reports.
2. Pick a tag, say customer-a, give the report a title, and click Create link.
3. Send the link to your customer.

The link opens a read-only page with that customer's domains: status, days left, expiry date, issuer and health score, always up to date. It needs no login and shows nothing else about your account.

Revoke stops a link at once. Links also stop working if the account leaves Pro. Need a PDF? Open the link and use your browser's Print → Save as PDF.

Work on it as a team (Team plan)

In most agencies, more than one person looks after the customers. Invite your colleagues under Settings → Team. They work on the same domains, tags and client reports, and every alert reaches all of you — so an expiring certificate does not wait until someone is back from holiday. Each person chooses which alerts they get. See Teams.

Quick reference

Field	Purpose	Example
label	Name 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)