Domain Monitoring

Know the moment a domain changes.

Monitor WHOIS/RDAP and DNS automatically. See exactly what changed and notify your team or applications when it matters.

Start 14-Day Free TrialSee how it works

No credit card required

Change Detection Workflow Example.com is monitored for WHOIS/RDAP and DNS changes. A nameserver change is detected, compared, saved to history, emailed, and delivered to an application webhook.

example.com

Monitoring active

WHOIS/RDAP
DNS
Change detected

Nameserver changed

Previous ns1.old.com
Current ns1.new.com

History

Saved

Webhook

Delivered

Product view

See what’s happening across your entire portfolio.

Scan every monitored domain, then open a detected change without losing the portfolio context.

Monitoring

4 of 10 domains monitored

Add domain

All domains

Example portfolio

Last check 12 min ago
DomainStatusLast change
example.comWHOIS/RDAP + DNS Active Nameservers changed
store.ioWHOIS/RDAP Active Expiration extended
mail.appDNS Active MX records changed
payments.devWHOIS/RDAP + DNS Attention needed Registrar changed
WHOIS/RDAP + DNSSelected sources, compared over time
Baseline firstThe first successful check is not an alert
Dashboard historyEvents remain visible even when email is filtered
Signed webhooksAvailable with eligible configured plans

From signal to action

Watch a domain change move through the system.

Selected WHOIS/RDAP and DNS data becomes a comparable snapshot, a detected event, and a useful next action.
  1. MONITORED DOMAIN example.com Active
  2. SELECTED SOURCES WHOIS/RDAP + DNS Fresh data received
  3. COMPARE SNAPSHOT Previous → Current Baseline matched
  4. CHANGE DETECTED Nameserver changed Important · 14:32
  5. HISTORYEvent saved
    WEBHOOKApplication updated

Interactive example

See a detected change in context.

Example data only — no customer monitors, delivery records, or requests are used here.

Example data

example.com

Active
OverviewChangesCurrent dataSettings
Nameservers changedImportantWHOIS / RDAP

Last checked 12 minutes ago

Previous value
ns1.old.example
Current value
ns1.new.example

All example change details

Nameserver: Nameservers changed

example.com · WHOIS / RDAP · Important

Previous
ns1.old.example
Current
ns1.new.example

Immediate email: sent · Webhook: eligible when configured

MX: All MX records removed

example.net · DNS · Critical

Previous
10 mail.example.net
Current
No MX records

Immediate email: sent · Webhook: eligible when configured

Registrar: Registrar changed

example.org · WHOIS / RDAP · Critical

Previous
Example Registrar One
Current
Example Registrar Two

Immediate email: sent · Webhook: eligible when configured

What is monitored

Monitor the domain data that can quietly break things.

Choose the WHOIS/RDAP and DNS sources that matter to your operation. Each successful check becomes the next comparison point.
REGISTRATION DATA

WHOIS / RDAP

Monitoring
  • Registrar monitored
  • Expiration date monitored
  • Domain status monitored
  • Nameservers monitored
  • DNSSEC monitored
EXAMPLE VALUE CHANGENameservers
ns1.old.com ns1.new.com
ROUTING DATA

DNS

Monitoring
A monitored
AAAA monitored
MX monitored
NS monitored
TXT monitored
CNAME monitored
SELECTED RECORD TYPES6 sources compared over time

History, severity, and notifications

Not every change deserves the same reaction.

Review what happened, understand its severity, and decide which events should reach your team or applications.

Change history

Today
  1. Critical

    Domain status changed

    ok → clientHold

  2. Important

    Nameserver changed

    ns1.old.com → ns1.new.com

  3. Informational

    TXT record updated

    Verification value changed

example.comWHOIS / RDAP
Important

Nameserver changed

The current nameserver no longer matches the previous successful check.

Previousns1.old.com
Currentns1.new.com
Email sentImmediate notification
Webhook deliveredSigned event payload

Practical use cases

Change awareness for the teams who own domain risk.

Security teams

Critical

Registrar changed

NameCheapUnknown registrar

Portfolio operators

Important

Expiration approaching

21 days remaining

Infrastructure teams

Critical

MX records removed

3 records0 records

Developers

Delivered

POST /webhook

200 OK

Developer workflow

Send signed change events to your application.

Premium and Enterprise accounts can configure one account-level endpoint. WhoisJSONAPI signs outbound payloads with HMAC-SHA256 and keeps delivery history in the Dashboard. Read monitoring documentation
DOMAIN CHANGEexample.comMX changed
Important
POST/your-endpoint
{
    "domain": "example.com",
    "event_type": "mx_changed",
    "severity": "important",
    "detected_at": "2026-09-20T12:00:00Z"
}
HMAC-SHA256 signed
200 DeliveredResponse recorded in delivery history

Monitoring capacity

Choose the coverage your portfolio needs.

Compare the three variables that shape day-to-day monitoring: domain capacity, check frequency, and webhook access.

See full pricing

Basic

$49/month

Portfolio
10 domains
Check frequency
Daily
Webhook access
No webhook

WHOIS/RDAP and DNS monitoring, change history, and email alerts. Includes a 14-day trial.

Start free trial
Most popular

Premium

$129/month

Portfolio
100 domains
Check frequency
Every 6 hours
Webhook access
1 endpoint

WHOIS/RDAP and DNS monitoring, change history, and email alerts. Includes a 14-day trial.

Start free trial

Enterprise

$299/month

Portfolio
1,000 domains
Check frequency
Hourly
Webhook access
1 endpoint

WHOIS/RDAP and DNS monitoring, change history, and email alerts. Includes a 14-day trial.

Start free trial

Premium and Enterprise include one monitoring webhook endpoint. Plan entitlements and account configuration determine availability.

FAQ

Questions before you monitor?

What does Domain Monitoring watch?

Configured monitors compare selected WHOIS/RDAP and DNS sources over time. WHOIS/RDAP coverage includes Registrar, Expiration date, Domain status, Nameservers, and DNSSEC. DNS coverage includes A, AAAA, MX, NS, TXT, and CNAME.

Does the first check send an alert?

No. The first successful check establishes a baseline. Later comparisons can create detected-change events.

What is shown for a detected change?

The Dashboard keeps a history entry with a source, severity, and previous and current values when those values are available.

Can I monitor many domains at once?

Current plans monitor 10, 100, or 1,000 domains. Bulk import is available when your plan enables it; capacity, imports, and webhooks depend on your plan and permissions.

Can I receive webhooks?

Premium and Enterprise accounts can configure one account-level webhook endpoint. Deliveries are signed with HMAC-SHA256, can be filtered and tested, and may be retried; delivery timing is not guaranteed.

Is Domain Monitoring a REST API?

No. Domain Monitoring is a signed-in Dashboard feature. The WHOIS and DNS APIs remain separate bearer-token API products.

How often are domains checked?

Current monitoring cadence is daily on Basic, every 6 hours on Premium, and hourly on Enterprise. Checks and notifications are asynchronous, not real-time guarantees.

Make domain changes easier to see and act on.

Start with a baseline, then use Dashboard history, eligible immediate email, and configured signed webhooks to keep your team informed.

Start your 14-day trialRead documentation