New advertisers: 50% off your first month with code FIRSTMONTHSee slots

Cloudflare Registrar toolkit that searches, buys, and audits domains with CSV, PDF, and calendar exports.

version
1.1.0
GitHub stars
32
View on GitHub

What it does

  • Adds cfreg and domrep scripts plus skills for search, purchase, listing, and renewal settings
  • Covers domain search and live pricing, a guarded register-domain purchase, and an audit with expiry reports
  • Enforces a live re-check and price match before any purchase, refusing premium or price-changed domains
  • Designed for owners of many domains who want expiry reminders, WHOIS and PII scans, and dated scan commits

Cloudflare domains: search, buy, audit; CSV, expiry PDF, calendar reminders, WHOIS and PII scans, scan workspace.

Add marketplace

/plugin marketplace add danielrosehill/Claude-Code-Plugins

Run it inside Claude Code once, then install the plugin below.

Install

/plugin install cf-domain-reg-ops@danielrosehill

Run it inside Claude Code after adding the marketplace.

Files

Discovered from source

Check existing registrations

Steps

  1. ${CLAUDE_PLUGIN_ROOT}/scripts/cfreg list returns every domain in the account's Registrar. For one domain: cfreg get <domain>.

  2. Summarise as a table sorted by expiry, soonest first:

    DomainExpiresAuto-renewLockedPrivacy

    Flag: anything expiring within 60 days, any domain with auto-renew off, any unlocked domain. Compute days-to-expiry from expires_at against today's date.

  3. For a narrower question ("when does X expire?", "is auto-renew on for everything?"), filter with jq instead of dumping the full list, e.g. cfreg list | jq -r '.[] | select(.auto_renew==false) | .name'.

  4. Changing settings (only when the user asks): cfreg update <domain> '<json>' with any of auto_renew, locked, privacy (booleans). Confirm by re-running cfreg get <domain>.

  5. Pending transfers in: cfreg get <domain> and read its transfer_in block.

Notes

  • Listing is read-only. update changes live settings; turning off locked or auto_renew raises hijack and lapse risk, so state what changes before running it.
  • Domains on Cloudflare DNS but registered elsewhere do not appear in this list.

Readme

CF-Domain-Reg-Ops

Search, check, register and audit domains through the Cloudflare Registrar API (beta), from Claude Code.

Skills

SkillWhat it does
setup-tokenCreate, store and verify the Registrar API token and account ID
search-domainsBrainstorm names, check live availability and at-cost prices across TLDs
check-registrationsList owned domains with expiry, auto-renew, lock, privacy; toggle settings
register-domainBuy a domain after a live check, with a price guard and status polling
export-csvEvery domain to CSV: dates, days left, auto-renew, lock, privacy, nameservers, registrant
expiry-reportPDF of domains by expiry, soonest first; expired / <30 / <90 days highlighted
expiry-reminders.ics calendar file (one all-day event per domain, alerts 30/7/1 days before), or events via a calendar tool
whois-reportRegistrant, admin, tech and billing contact per domain, grouped by registrant, plus what public RDAP exposes
pii-scanSearch every domain's contacts, the registrar's WHOIS record and public RDAP for an email, phone, name or address
setup-workspaceCreate a private "domain workspace" repo for scans and save its path as DOMAIN_WORKSPACE_REPO
run-scanDated scan into the workspace (CSV, PDF, ICS, WHOIS report, summary), diff against the last one, commit and push

Two scripts do the work. scripts/cfreg (bash + curl + jq) talks to the API:

cfreg verify
cfreg search "<keywords>" [limit]
cfreg check <domain> [domain...]          # up to 20, live
cfreg list | get <domain> | update <domain> '<json>'
cfreg register <domain> <expected_price> [--auto-renew]
cfreg status <domain>
cfreg dump                                # full record for every domain, JSON array

scripts/domrep (Python 3, stdlib only) builds reports from a dump (it runs cfreg dump itself unless given --dump file.json):

domrep csv      --out domains.csv
domrep pdf      --out expiry-report.pdf       # typst, else headless Chrome, else HTML
domrep ics      --out domain-expiry.ics [--alarms 30,7,1]
domrep whois    --out whois-report.md [--no-rdap]
domrep pii-scan --term "<value>" [--term ...] --label "<label>" --out pii-scan.md [--no-rdap]
domrep scan     --workspace <dir>             # all of the above into <dir>/scans/YYYY-MM-DD/

Domain workspace

Scans and exports can go to a private Git repo of your own. setup-workspace scaffolds it from templates/domain-workspace/ and stores its path as DOMAIN_WORKSPACE_REPO in the config file (an environment variable of the same name overrides it). Until it is set, skills write to the current directory.

Requirements

  • curl, jq, Python 3. For PDFs: typst or Chrome/Chromium.
  • A Cloudflare user API token with Account → Registrar: Domains → Edit (Read is enough for search, check and list), plus your account ID.
  • For purchases: a default payment method, a default registrant contact and the accepted Domain Registration Agreement in the Cloudflare dashboard.

Credentials are read from CLOUDFLARE_REGISTRAR_TOKEN (falls back to CLOUDFLARE_API_TOKEN) and CLOUDFLARE_ACCOUNT_ID, or from ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/cf-domain-reg-ops/config.env. Run the setup-token skill to create it.

Safety

cfreg register re-checks the domain live immediately before buying and refuses if it is no longer registrable, is premium, or its price differs from the price you approved. Registrations are billed to the account's default payment method and are non-refundable.

API endpoints used

Base https://api.cloudflare.com/client/v4, all under /accounts/{account_id}/registrar/:

CommandMethod + path
searchGET domain-search?q=&limit= (cached, discovery only)
checkPOST domain-check {"domains":[…]} (live, max 20)
list / getGET domains, GET domains/{domain}
updatePUT domains/{domain}
registerPOST registrations {"domain_name":…}
statusGET registrations/{domain}/registration-status

list, get and update use the registrar/domains routes. These answer live but no longer appear in Cloudflare's published OpenAPI schema (checked 2026-11-15). get is the only source of contacts and WHOIS data: registrant_contact, administrator_contact, technical_contact, billing_contact, and whois (privacy, registrant, raw). whois.raw is the unredacted record Cloudflare holds; public RDAP shows the redacted view. list pages at 30 and its pages are 0-indexed.

Public RDAP lookups (whois, pii-scan) go straight to each registry using the IANA bootstrap (data.iana.org/rdap/dns.json), with rdap.org as a fallback.

Contact updates: dashboard only

The Registrar API can't change contacts on existing domains. The only documented update, PATCH registrations/{domain}, accepts auto_renew alone, and contacts can only be set at registration (POST registrations, contacts). Cloudflare documents contact changes as a dashboard flow (domain contact updates):

  • Changing first name, last name, organisation or email is a Change of Registrant. The current registrant must approve by email, and so must the new address if the email changes. Unapproved requests lapse after 7 days.
  • Approving applies a 60-day transfer lock unless the registrant opts out. Phone and address changes apply immediately.

To find which domains need changing, run pii-scan with the old value.

Verified behaviour (2026-11-15)

  • Against a live 30-domain account: dump, csv, pdf (typst), ics, whois (29/29 registry RDAP lookups succeeded; one expired domain returned 404), pii-scan (email and phone terms matched exactly the expected contact fields).

  • rdap.org on its own rate-limited a burst: 19 of 30 lookups returned 429. That is why lookups now go direct to the registry.

  • The pii-scan "publicly exposed" path is untested: every domain tested had redacted public RDAP.

  • Confirmed live: verify, search, check (available, taken, and .uk), list, and both register refusal paths (price mismatch, domain taken). No purchase was made.

  • Not yet exercised: a real register and status poll. The request shape follows Cloudflare's Registrar API guide.

  • domain-search can return names whose renewal price differs from the first-year price (e.g. a .org at 8.50 / 11.20).

  • The API defaults auto-renew to off; --auto-renew sets it after a successful registration.

  • list follows result_info.total_pages. The account tested fits in one page, so multi-page results are unverified.

History

  • 1.0 (2026-11-15): search, check, register, list.
  • 1.1 (2026-11-15): reports (CSV, PDF, ICS, WHOIS, PII scan) and the domain workspace. Also absorbed the domain-search playbook from the author's private Cloudflare management plugin, whose search, check and buy guidance this plugin's skills already covered.

Installation

/plugin install cf-domain-reg-ops --marketplace danielrosehill/Claude-Code-Plugins

Older Claude Code:

claude plugins marketplace add danielrosehill/Claude-Code-Plugins
claude plugins install cf-domain-reg-ops@danielrosehill

License

MIT

Details

Marketplace
danielrosehill/Claude-Code-Plugins
Source
danielrosehill/CF-Domain-Reg-Ops
Author
Daniel Rosehill
Category
Network & Smart Home
License
MIT

More from danielrosehill/Claude-Code-Plugins

All 264

Similar to cf-domain-reg-ops

More Productivity & Planning