For DNS & IT admin

DNS changes you can prove, and undo.

Records and zone settings across every zone in one place. A change is proposed, classified — an apex deletion is high impact and needs an acknowledgement — executed, read back from Cloudflare, and stored with its revert.

Who DNS administrators, IT administrators

What gets in the way

  • Which zone has which record, across dozens of accounts
  • A DNS edit with no record of who made it or what it replaced
  • Certificates and DNSSEC state checked by hand
The Changes tab: each WAF rule change to a site, with when it was made, who made it, and its outcome
Every change, with its outcome

What Zonesteward does about it

  1. DNS across the fleet

    Records by zone, changes admin-only; an apex change is classified high and needs an explicit acknowledgement, as does a bulk change above ten zones or a high-impact one on any number. See it

  2. Read-back and revert

    “Applied” means Cloudflare was asked what the record is now. Every change stores its before-state and a one-click revert. See it

  3. Certificates, DNSSEC, settings

    Edge certificates and expiry, DNSSEC down to the DS record, Universal SSL, zone status and nameservers — a sentence away. See it

Free during the beta.

Your own Cloudflare token and model key; nothing marked up.

  1. 01You
  2. 02Your fleet
  3. 03Fit
Who should we write back to?

Takes about two minutes.