DNS Record Change Monitor avatar

DNS Record Change Monitor

Pricing

from $5.00 / 1,000 dns record changes

Go to Apify Store
DNS Record Change Monitor

DNS Record Change Monitor

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.

Pricing

from $5.00 / 1,000 dns record changes

Rating

0.0

(0)

Developer

PROOFNEXA

PROOFNEXA

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

8 hours ago

Last modified

Share

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

$python3 test/smoke_local.py