RDAP Portfolio Change Receipts
Pricing
$2.00 / 1,000 domain checkeds
Go to Apify Store
RDAP Portfolio Change Receipts
Pricing
$2.00 / 1,000 domain checkeds
Rating
0.0
(0)
Developer
muazah
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
21 hours ago
Last modified
Categories
Share
Monitor a domain portfolio against live registry records and get receipts you can reconcile, one line per domain per run.
What it does
- Checks up to 200 distinct domains per run against the authoritative RDAP service for each TLD (via the IANA bootstrap, longest-suffix routing, including multi-part TLDs like co.uk).
- Diffs registrar, nameserver set, domain status set, and the registry-published expiration date against your prior run.
- Emits expiry-window alerts at 90 / 30 / 14 / 7 / 1 days to the published expiration, firing once per crossing (no repeat storms).
- Flags
REGISTRATION_NO_LONGER_OBSERVEDonly after two independent authoritative 404 observations with timestamps. Faults never count as confirmation, and failures never overwrite a good snapshot. - Records what could not be verified: per-domain status (SUCCESS, NOT_FOUND_OBSERVED, UNSUPPORTED_TLD, RATE_LIMITED, FETCH_FAILED, INVALID_RESPONSE, INVALID_INPUT, DUPLICATE_INPUT), source URL, and billable flag.
- Metadata only. No WHOIS privacy redaction problems: it stores registrar name, nameservers, statuses, and event dates. Never registrant contacts.
Input
{"domains": [{"domain": "example.com"}], "monitorKey": "my-portfolio", "stateMode": "compare-and-save"}
- monitorKey namespaces your stored snapshot. Run the same key repeatedly to get change receipts over time.
- stateMode:
compare-and-save(default),lookup-only, orreset-baseline. - Also accepts a multiline CSV (
domain,label).
Output
- Dataset: one observation row per input domain, plus change rows with before/after and the prior observation timestamp.
- Run artifacts: observations.csv and changes.csv in the run's key-value store.
- Summary: counts by status, billable domains, and the monitor key.
Billing
Pay per distinct domain that returns a successful check or an authoritative 404 observation. Duplicates, unsupported TLDs, rate-limits, and fetch failures are not charged. Unchanged successful checks are billable (that is the check you paid for).
Honest limits
NOT_FOUND_OBSERVEDis an authoritative absence at observation time. It is never a claim that a domain is available to register.- Expiration is the registry-published event date, not a renewal or purchase promise.
- Some TLDs have no public RDAP service; those come back as UNSUPPORTED_TLD, uncharged.