Docs

Add the first monitored hostname and send a test warning.

Use this path for the first setup: workspace, monitor, immediate check, alert channel, and teammate invite.

Start freeMonitor docs

Reading path

Guidance turns into setup

Next steps

Articles connect the operational decision to checker, docs, monitoring, and routing workflows.

CheckRun one hostname now
LearnRead certificate monitoring docs
RouteSend urgent warnings
Checker, guide, docs, feature pages
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.

01

1. Create the workspace

Sign up with email and password, complete the verification challenge, and create the workspace where monitors, channels, delivery attempts, audit rows, and teammates will live.

  • Use a workspace name your team will recognize.
  • Keep experiments separate from production coverage.
  • Success state: the dashboard opens with an empty monitor list and workspace settings available.
02

2. Add the first monitor

Add the domain or subdomain users connect to, optional port, optional SNI hostname, label, tags, and expiry thresholds. Domain Trust Watch runs the first check immediately.

  • Start with a production hostname that customers or API clients use.
  • Use labels and tags while the list is still small.
  • Success state: the monitor shows the latest certificate snapshot or a clear DNS, TCP, TLS, or validation failure.
03

3. Configure alert channels

Create an email, Slack incoming webhook, or signed webhook channel, then attach it to workspace-wide or monitor-specific alert settings based on severity.

  • Use workspace-wide settings for default coverage.
  • Use monitor-specific settings for checkout, API, identity, CDN, or client hostnames.
  • Success state: a test delivery reaches the expected inbox, Slack channel, or webhook receiver.
04

4. Invite the team

Invite operators who handle renewal or alert follow-up. Use owner, admin, and member roles to separate workspace administration from daily certificate review.

  • Invite at least one backup owner or admin before production coverage depends on one person.
  • Use member access for teammates who only need to inspect health and history.
  • Success state: the workspace has the people needed to act on future warnings.
Related3 pagesSSL checkerInspect one public hostname before creating the monitor.Run free SSL checker
FeatureAlert routingChoose which channels receive early and urgent warnings.FeatureTeam workspacesInvite teammates and separate access by role.
Need a live read?

Check the hostname before creating the monitor.

Use the free checker when you need to confirm what the endpoint serves right now.

Run SSL checkerView monitor docs