Domain Monitoring

Domain Monitoring tracks configured domains as first-class monitoring targets so operations teams can identify domain-related risks before they affect availability, ownership continuity, or incident response.

What Domain Monitoring Checks

• Domain status and current monitoring state.
• Expiration date, days until expiration, and the configured expiration alert window.
• Public registry status codes, registrar name when available, and registrar-lock state when Bitaic can infer it.
• Nameserver drift when expected nameservers are configured.
• DNSSEC state, with drift alerts when a DNSSEC expectation is configured.
• RDAP or WHOIS retrieval state for registry metadata collection.
• Last check time and recent status changes.
• Alert state for healthy, at-risk, degraded, unavailable, or unknown domains.
• Dashboard visibility for monitored domains and domain history.

Product Boundaries

• Use Domain Monitoring to understand whether a domain itself is healthy and operationally safe.
• Use DNS Monitoring to validate record resolution, expected answers, propagation behavior, and DNS latency.
• Use Endpoint Monitoring to confirm that a specific URL, application, or service responds successfully.

Launch Behavior

Data And Alerts

• Domain name.
• Current domain status and alert state.
• Registrar, expiration timestamp, days until expiration, registry status codes, and retrieval state when public metadata is available.
• Observed nameservers, expected nameserver state, DNSSEC state, and registrar-lock state.
• Last check time.

Domain Monitoring alerts when a domain moves from an expected healthy state to an at-risk, degraded, unavailable, or unknown state. Expiration is threshold-based; nameserver, DNSSEC, and registrar-lock alerts are based on expected-state drift. Alert routing uses the same notification and incident integrations as the rest of the Bitaic monitoring platform.

Configuration Example

domains:
  - name: example.com
    check_interval_hours: 24
    expiration_alert_days: 30
    expected_nameservers:
      - ns1.example-dns.com
      - ns2.example-dns.com
    expected_dnssec_state: enabled
    expected_registrar_lock_state: locked

Example Workflow: Track Domain Continuity

Goal: monitor a business-critical domain, catch at-risk domain-state changes, and keep renewal or nameserver issues visible to the owning team.

1. Choose a domain your team owns and confirm the operational owner, registrar owner, and escalation route for domain incidents.
2. Add the domain to the Domain Monitoring configuration with the renewal window, expected nameserver set, DNSSEC expectation, and lock expectation used by the owning team.
3. Connect the domain target to the alert policy that reaches the team responsible for registration, registrar lock, or nameserver changes.
4. Run or wait for the first domain check, then review the dashboard status, registry metadata, nameserver state, DNSSEC state, lock state, last check time, and alert state.
5. During normal operations, review domain alerts alongside registrar records before making renewal, lock, DNSSEC, or nameserver changes.

CLI And API

Bitaic CLI and API workflows cover adding, listing, checking, and removing monitored domains.

bitaic domain add <domain_name> [--expiration-alert-days <days>] [--expected-nameserver <name>]...
bitaic domain list
bitaic domain status <domain_name>
bitaic domain check <domain_name>
bitaic domain remove <domain_name> [--yes]

Domain CLI output includes domain, status, alert_state, registrar, expires_at, days_until_expiration, expiration_alert_days, registry_statuses, registrar_lock_state, nameserver_state, observed_nameservers, expected_nameservers, dnssec_state, rdap_state, and checked_at when those checks are configured or observed.

• Create or list monitored domains with /v1/workspaces/{workspace_id}/targets and type: "domain".
• Attach domain continuity checks with /v1/workspaces/{workspace_id}/targets/{target_id}/checks and type: "domain_status".
• Retrieve domain alerts with /v1/workspaces/{workspace_id}/alerts filtered by target_id.
• Update domain behavior with /v1/workspaces/{workspace_id}/checks/{check_id} for expiration_alert_days, schedule.interval_hours, expected_nameservers, expected_dnssec_state, and expected_registrar_lock_state.
• Retrieve expiration metrics with /v1/workspaces/{workspace_id}/metrics and domain.days_until_expiration.