View and edit records
See your zone and add, edit or delete records — TXT for verification, CNAME for services, MX for mail and more — with changes applied through the same DNS driver that runs the platform.
Self-service DNS & cache
Manage your own DNS and purge caches — safely
View, add, edit and delete your own DNS records in bulk, and purge caches on demand, from one panel and the MCP. The records that keep your sites online — the IP and origin A-records — stay locked, and on the Footprint-Free line they are hidden entirely, so you get full control without a footprint leak or a self-inflicted outage.
- Full record CRUDTXT, CNAME, MX, bulk
- Origin lockedIP records can't be changed
- PBN-safehosting records hidden
- Dashboard + MCPone engine-side policy
Your records, in your hands
Everything you would expect from a DNS panel, exposed the same way to a person and to an AI agent.
Bulk operations
Apply a record set across many domains at once instead of clicking through one zone at a time — a verification TXT across a network, an MX preset across a portfolio.
Cache purge, coordinated
Purge everything, specific URLs or specific cache tags. The purge is mirrored across the server cache, the CDN and the edge, so every layer clears in step.
Same on dashboard and MCP
Every operation is available to your AI tool through the MCP as well as the dashboard, so bulk and automated DNS work is first-class, not a manual chore.
IP-protected by design
Self-service DNS is only safe if the dangerous records are out of reach. Ours are — and the rule lives in the engine, so it cannot be worked around.
- You may never change the IP or origin A-records that point a site at our hosting — the single fastest way to take a site offline.
- On the Footprint-Free line those hosting records are not shown at all, so the link between a PBN site and its origin is never exposed in the panel.
- On the other lines the records are visible for transparency but locked against editing.
- The guardrail is engine-side policy, not an interface check, so the dashboard, the API and the MCP all enforce it identically — an agent cannot bypass it.
- Every change is tenant-scoped and audit-logged, with the identity that made it recorded.
FAQ
Which records can I manage myself?
The records that are safely yours to change: TXT, CNAME, MX and the rest, added, edited, deleted and managed in bulk. The one thing you cannot touch is the IP or origin A-record that points a site at our hosting — that stays locked so a bad edit can never take a site offline. On the Footprint-Free line those hosting records are not even shown.
Why can't I edit the origin A-record?
Because it is the record most likely to break a site and, on a PBN, most likely to leak a footprint. The guardrail is enforced in the engine, not the interface, so it holds identically on the dashboard, the API and the MCP — an AI agent acting for you cannot change it either. You get full control of everything else.
What is different on the PBN line?
On the Footprint-Free line the IP and origin records are hidden entirely — you manage your TXT, CNAME and MX records, and the hosting records simply are not part of the surface. On the other lines those records are visible but locked. Either way the origin cannot be changed.
Can I purge the cache myself?
Yes. Clear everything, specific URLs or specific cache tags whenever you need to, from the dashboard or the MCP. Purges are coordinated across the server cache, the CDN and the edge so every layer clears the same pages at once.
Can my AI assistant manage DNS and purge caches?
Yes. Record CRUD, bulk edits and cache purges are exposed on the MCP as well as the dashboard, under the same engine-side policy — so an agent can apply a record set across a hundred domains or purge a batch of zones, and still never change an origin record.
Related
Take control of your DNS
Start a card-free 7-day trial and manage your own records and cache purges from one panel and your AI tool — with the origin records protected so nothing you do can take a site offline.
Start free