Epic: Transfer peterp.org domain registration to Cloudflare Registrar

Goal

Transfer the registration of peterp.org from its current registrar to Cloudflare Registrar (at-cost pricing, single-pane management with the Worker).

Why

• Consolidates DNS, hosting, and registrar inside Cloudflare.
• Cloudflare Registrar charges domains at-cost.

Scope

Registrar transfer only. Hosting and code migration are tracked in #2 and #1.

Sub-issues

• #15 Identify current registrar; unlock domain & retrieve auth (EPP) code
• #16 Add peterp.org as a Cloudflare zone and update nameservers
• #17 Initiate registrar transfer in Cloudflare dashboard
• #18 Verify registrar transfer completion + DNS still resolves
• #19 Investigate whether the new cf CLI can drive the registrar transfer

Notes on the cf CLI

The cf CLI is in technical preview (npx cf / npm install -g cf) and only covers a small subset of products today; Registrar operations still require the dashboard or the Registrar API. Worth re-checking before doing the transfer manually \u2014 see #19.

Dependencies

• Independent of #1; can run in parallel.
• Custom-domain wiring on the Worker (#12) is simpler once nameservers are on Cloudflare (#16).

References

• https://developers.cloudflare.com/registrar/get-started/transfer-domain-to-cloudflare/
• https://blog.cloudflare.com/cf-cli-local-explorer/

Start with sub-issue #15 to identify the current registrar, unlock the domain, and retrieve its EPP code, then read Cloudflare’s transfer guide linked in the issue. Work through sub-issues #16–#18, checking DNS resolution after the transfer; completion means peterp.org is registered with Cloudflare and still resolves correctly. Re-check #19 for current cf CLI support before using the dashboard.