# DNS Record Change Monitor (`invaluable_rondeau/dns-record-change-monitor`) Actor

Compare buyer-provided DNS record snapshots and report record-type changes using hashes only. No production DNS, RDAP, WHOIS, expiry, registrant, or raw record values are fetched or emitted.

- **URL**: https://apify.com/invaluable\_rondeau/dns-record-change-monitor.md
- **Developed by:** [PROOFNEXA](https://apify.com/invaluable_rondeau) (community)
- **Categories:** Automation, Developer tools, SEO tools
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 dns record changes

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## DNS Record Change Monitor

Unofficial, buyer-provided snapshot tool; not affiliated with any DNS provider.

Compare a buyer-supplied current DNS snapshot with the previous snapshot and
return record-type changes without exposing raw record values.

### What it does

- Input: `currentRecords` and an optional `watchlistId`.
- First run: saves a baseline and does not charge `change-detected`.
- Later runs: compares the current snapshot with the named KVS state.
- Output: domain, record type, value/set hashes, status, change kind, counts,
  and timestamps.
- Invalid input is returned as one error item and is not billable.

The Actor does **not** resolve production DNS and does not query RDAP or WHOIS.
It does not output raw record values, expiry dates, registrants, or personal
data. The buyer must provide current records from their own resolver, export,
or scheduled workflow.

### Schedule setup

1. Create a schedule in Apify Console for this Actor.
2. Supply the current `currentRecords` snapshot on each run.
3. Keep the same `watchlistId` to compare against the named KVS state.

Changing `watchlistId` starts a new baseline. The named KVS is
`dns-record-change-monitor-state`; Apify storage usage is charged to the
buyer account.

### Initial validation pricing

- `change-detected`: **$5.00 per 1,000 changed record-type events** ($0.005 per
  event).
- Baseline, unchanged, and invalid-input items do not trigger this custom
  event.
- The standard `apify-actor-start` synthetic event remains enabled when the
  Actor is monetized.
- Demand evidence is currently missing; publication is a validation test,
  not evidence of buyers or revenue.

### Local smoke

```bash
python3 test/smoke_local.py
```

# Actor input Schema

## `watchlistId` (type: `string`):

Namespace for the snapshot. Buyer-owned list identifier.

## `currentRecords` (type: `array`):

Buyer-supplied DNS records. Actor does not fetch production DNS. Each item: {domain, type, value} or {domain, records:\[{type,value}]}.

## `previousSnapshot` (type: `object`):

Prior hash snapshot {capturedAt, entries:\[{domain,type,valueHashes,setHash}]}. If omitted, run is baseline (no change charges).

## `allowEmptyCurrent` (type: `boolean`):

Allow an explicitly empty current snapshot; no change event is charged.

## Actor input object example

```json
{
  "watchlistId": "default",
  "allowEmptyCurrent": false
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("invaluable_rondeau/dns-record-change-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("invaluable_rondeau/dns-record-change-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call invaluable_rondeau/dns-record-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=invaluable_rondeau/dns-record-change-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ruUs5M7xL11olhO27/builds/5tQOAZJRaH7EnN9DT/openapi.json