Domain Portfolio Monitor - Expiry & WHOIS Change Alerts

Watch a list of domains and get told when something important changes: the registration is about to expire, the registrar changed, the nameservers moved, or a status flag appeared.

Built on RDAP, the open successor to WHOIS. No API key, no account, no rate-limit configuration.

What it detects

Signal	Why it matters
Expiry approaching	The single most common cause of accidental outages and lost domains
Registrar change	An unexpected transfer can mean a hijack
Nameserver change	DNS takeover, or a migration you were not told about
Status flags	clientHold, pendingDelete, serverTransferProhibited and friends
DNSSEC toggled	Signing turned on or off
Expiry date moved	Confirms a renewal actually happened

Typical uses

• Never lose a domain to silent expiry across a portfolio you did not personally register
• Watch client or subsidiary domains you manage but do not control
• Detect hijacks early by alerting on registrar or nameserver change
• Verify that auto-renew actually renewed
• Track competitor or acquisition-target domains

Input

Field	Type	Default	Description
domains	array	—	Required. Domains to watch. Full URLs and www. prefixes are cleaned automatically.
alertDaysBeforeExpiry	integer	30	Flag expiringSoon when expiry falls inside this window.
onlyReportChanges	boolean	false	Return a domain only if something changed or it is expiring soon.
concurrency	integer	5	Parallel lookups.
stateName	string	domain-monitor-state	Named store holding each domain's previous snapshot.

{
  "domains": ["github.com", "wikipedia.org", "example.co.uk"],
  "alertDaysBeforeExpiry": 30,
  "onlyReportChanges": true
}

Output

{
  "domain": "github.com",
  "isFirstCheck": false,
  "expiration": "2026-10-09T07:00:00Z",
  "daysUntilExpiry": 53,
  "expiringSoon": false,
  "registrar": "MarkMonitor Inc.",
  "status": ["client delete prohibited", "client transfer prohibited"],
  "nameservers": ["dns1.p08.nsone.net", "dns2.p08.nsone.net"],
  "dnssec": false,
  "changeCount": 1,
  "changes": [
    { "field": "nameservers",
      "from": ["ns1.old.net"],
      "to": ["dns1.p08.nsone.net", "dns2.p08.nsone.net"] }
  ],
  "checkedAt": "2026-08-17T11:02:44.108Z"
}

The first run for a domain records a baseline, so changes is empty and isFirstCheck is true. From the second run onward you get real diffs.

Recommended setup

Attach an Apify Schedule and run it daily with onlyReportChanges: true. Quiet days return an empty dataset, so ongoing monitoring stays cheap, and anything that does come back is worth reading.

Pricing

A small per-run charge covers the check, then a small charge per domain returned. With onlyReportChanges enabled, a day where nothing moved returns nothing and costs only the run charge.

Notes and limitations

• A handful of TLDs do not publish RDAP yet (.io is a notable example). Those return an error record rather than failing the run. In changes-only mode a repeated identical error is reported once, not on every run, so an unsupported TLD will not quietly bill you forever.
• Nameservers and status values are normalised (lowercased, sorted, trailing dots stripped) so cosmetic registry differences are not reported as changes.
• Registrant contact details are redacted by registries under GDPR and are deliberately not returned.

How to use Domain Portfolio Monitor

1. Open Domain Portfolio Monitor on Apify Store and click Try for free.
2. Fill in the input (the form is prefilled with a working example) and click Start.
3. Watch results appear in the Output tab, then download them as JSON, CSV, Excel or HTML, or read them through the API.
4. Optional: save the input as a task and add a schedule to run it automatically, or connect it to your tools with integrations and webhooks.

Use Domain Portfolio Monitor with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/domain-portfolio-monitor

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/domain-portfolio-monitor" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/domain-portfolio-monitor",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--domain-portfolio-monitor; ask it, for example, to "run Domain Portfolio Monitor with {"domains": ["github.com", "wikipedia.org", "python.org"]}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run Domain Portfolio Monitor via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~domain-portfolio-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains": ["github.com", "wikipedia.org", "python.org"]}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/domain-portfolio-monitor").call(run_input={"domains": ["github.com", "wikipedia.org", "python.org"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/domain-portfolio-monitor').call({"domains": ["github.com", "wikipedia.org", "python.org"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~domain-portfolio-monitor/runs and fetch the dataset when the run finishes, or receive a webhook.

Integrations

Domain Portfolio Monitor works with Make, Zapier, n8n, LangChain, Google Sheets, Slack, GitHub and webhooks. Schedule runs in Apify Console and send new results straight to your apps, spreadsheets or AI pipelines.

Related Actors

• Domain WHOIS Lookup — Look up WHOIS records for any domain: registrar, creation and expiry dates, name servers and registrant detail

FAQ

Can I use Domain Portfolio Monitor with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/domain-portfolio-monitor (see above) and the agent can run the Actor and read its results on its own.

Can I call Domain Portfolio Monitor from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.