Skip to content

Domain monitoring

Domain monitoring continuously checks certificates on domains and ports, including validity, chain health, issuer, validation level, and reachability. Open it at Domain monitoring.

The monitoring page supports:

  • Discovering related domains from a primary domain and adding monitors in bulk.
  • Filtering by all, healthy, abnormal, and expiring-soon states.
  • Searching existing monitors by domain keyword.
  • Card and table views.
  • Table column configuration for dense account views.
  • Single detection, batch detection, and batch deletion.
  • Turning alert reminders on or off for one or many monitors.
  • Jumping from monitor details to WHOIS lookup or SSL check.

The latest frontend discovers related domains first, then lets you choose the candidates to monitor.

  1. Open the add dialog

    Click Add monitor on the monitoring page. Domains are prefilled when opened from WHOIS or SSL check results.

  2. Enter primary domain and port

    • Primary domain: for example anssl.cn.
    • Port: defaults to 443. If the input includes a port, such as example.com:8443, the form extracts the host and port automatically.
    • Alert reminder: enabled by default.
  3. Search related domains

    Click Search related domains. Candidates stream in with status, IP, issuer, validation level, remaining days, and notes.

  4. Select monitorable candidates

    Only candidates that are not already monitored and have a healthy status can be selected. Already monitored, unreachable, expired, invalid, or failed candidates show the reason but cannot be added directly.

  5. Submit

    Click Monitor N domains. The list refreshes after success, and already monitored items are skipped.

StateMeaningRecommended action
HealthyConnection succeeds and certificate is validKeep monitoring
Expiring soonCertificate is valid but close to expiryRenew or request a replacement
ExpiredCertificate is past its validity windowFix immediately
Invalid certificateChain, hostname match, or validity is abnormalOpen details and correct configuration
UnreachableTarget domain or port cannot be reachedCheck DNS, firewall, and service status
Detection failedTLS or certificate check did not completeRe-run detection or use SSL check
  • Use domain search to filter monitor records.
  • Use status filters for all, healthy, abnormal, and expiring-soon records.
  • In table view, use Column configuration to choose visible fields.
  • Run detection for a single monitor.
  • Select multiple rows and run batch detection. The frontend submits checks sequentially and refreshes the list when finished.

Each monitor can turn alerts on or off. After selecting multiple rows, you can enable or disable alerts in bulk.

Deleting one or many monitors only removes monitoring records. It does not delete certificates or affect online services.

Open the detail drawer to see:

  • Domain, port, status, created time, and last check time.
  • Issuer, validation level, effective time, expiry time, and remaining days.
  • Domains contained in the certificate, with a copy-all action.

The drawer has two quick actions:

  • WHOIS lookup: opens WHOIS with the current domain.
  • SSL check: opens SSL check with domain:port.

From the certificate lifecycle drawer, you can add a 443 monitor for the certificate’s primary domain. The monitoring page helps identify expiring or abnormal online certificates, then you can return to certificate management to renew, re-request, or deploy replacements.

Candidates can be selected only when they are not already monitored and their status is healthy. Already monitored, unreachable, expired, invalid, or failed candidates need their underlying issue addressed first.

Section titled “What should I do if related-domain search times out?”

Discovery depends on certificate records and network checks. Narrow the input, retry later, or start by monitoring the primary domain.

Check:

  1. DNS resolves to the expected IP.
  2. The port is open.
  3. The service supports TLS.
  4. Firewall or security group rules allow external access.
  5. A non-443 port should be specified.