Restricted Mode
When the balance of an account is not settled, PrimeDNS restricts the account instead of switching DNS off. Your zones keep answering, so websites and mail keep working, but the account can no longer change anything or look at the paid add-on services until the balance is settled. This page lists exactly what still works, what is refused, and what your code receives.
The rule
DNS answers are not affected. Records stay where they are and your zones keep resolving. While an account is restricted it can see what it has, pay, and manage its own login and billing details. It cannot change records or settings, and it cannot read statistics, logs, notifications or certificates.
An account is restricted when its billing status is frozen, suspended or pending_del. The same rules apply to all three.
A team member acting on behalf of a restricted account is restricted as well, and so is an API key of that account.
What still works
| Area | Allowed |
|---|---|
| Sign-in | All of /v1/auth/*: login, two-factor, passkeys, magic link, password reset. |
| Account | GET /v1/account, /v1/account/balance, /v1/account/subscription, /v1/account/tax-settings, PATCH /v1/account/tax-settings, POST /v1/account/vies-validate, GET /v1/account/api-keys (list only), DELETE /v1/account, GET /v1/plans |
| Payments | All of /v1/payments/*: checkout, recurring payments, orders, transactions, invoices. |
| State of your DNS | GET /v1/domains, GET /v1/dns/records, GET /v1/dns/records/{id}, GET /v1/zones/{zone}/dnssec |
| Other accounts' teams | GET /v1/team/memberships, GET /v1/team/my-invitations, DELETE /v1/team/my-invitations/{token}, POST /v1/team/invitations/{token}/accept. Membership in someone else's active account does not depend on your own balance. |
What is refused
| Area | Refused |
|---|---|
| Every change | Records (create, update, delete, bulk, import, applying a template, syncing views, ACME challenges), zones (add external, delete), DNSSEC (enable, disable, rectify), views and their networks, templates and server profiles, webhooks, alert rules, SSL monitors, managed certificates, API keys (create, update, delete), team (invite, roles, zones, remove), profile, plan change. |
| Reading add-on services | GET /v1/audit (JSON, CSV, ndjson), GET /v1/webhooks* and deliveries, GET /v1/alert-rules*, GET /v1/alert-incidents, GET /v1/monitors/ssl*, GET /v1/zones/{zone}/export, GET /v1/ssl/certificates* (including download), GET /v1/views*, GET /v1/templates*, GET /v1/team, GET /v1/zones/{zone}/views* |
| Dynamic DNS | GET/POST /v1/dns/update answers abuse, the standard protocol reply for a blocked account. |
| Notifications and monitors | Webhook deliveries wait and are sent after the balance is settled. Alert rules and SSL monitors of the account are not evaluated while it is restricted. |
What your code receives
A refused request answers 403 with the code ACCOUNT_FROZEN and the billing status in error.details:
HTTP/1.1 403 Forbidden
Content-Type: application/json
{
"success": false,
"error": {
"code": "ACCOUNT_FROZEN",
"message": "Your account is frozen: changes are not possible until the balance is settled. DNS keeps answering.",
"details": { "billing_status": "frozen" }
}
}
Treat it as a state of the account, not as a bug in the request: retrying does not help until the balance is settled. A script that changes records
should stop and report the error instead of retrying. The same code is listed as a possible 403 answer on every affected operation in the
API reference.
Leaving Restricted Mode
Settle the balance in the panel (Billing) or with the payment endpoints, which stay available. Pending webhook deliveries are then sent.
Related
- Webhook events: how deliveries behave for a restricted account.
- Team & RBAC: roles and acting on behalf of an account.
- Terms of Service, section 5 (Plans and Payment).