The domain privacy endpoint requests the provider's supported ID-protection service for an owned domain. It does not make every TLD eligible for privacy, and a publicly redacted registration-data result is not by itself proof that a paid privacy service is enabled.
IN THIS ARTICLE
01 Check the current offer and state
| Method | Resource | Scope | Idempotency-Key |
|---|---|---|---|
GET |
/v2/domains/{domainId}/id-protection |
domains:read |
Not required by this route |
PUT |
/v2/domains/{domainId}/id-protection |
domains:id-protection |
Required |
- Read the owned domain and the TLD's current offer or supported features.
- GET the recorded ID-protection state. Treat it as stored state, especially if the provider has changed since the last reconciliation.
- Confirm eligibility and any fee through the current account offer and quote workflow.
- PUT an explicit JSON boolean
enabled, plusprice_quote_idwhen a fee applies. - Save the returned operation ID and follow its final result. Reconcile the provider state before reporting that the privacy service changed.
For example, an enable request has the shape:
{
"enabled": true,
"price_quote_id": "CURRENT_QUOTE_IF_REQUIRED"
}Use the actual quote only when applicable. Do not send the placeholder in a live request. Always state the intended boolean, because the handler's omitted-value default is false.
Will privacy hide all uses of the domain owner's identity?
No. The service's scope depends on the provider and registry. It does not remove information already published elsewhere, hide company website content or replace the obligation to supply accurate registration details.
Why does public lookup already show redacted details?
Registration-data disclosure policy and optional ID protection are separate. Check the service's recorded and provider-confirmed state instead of inferring it solely from a lookup page.
If the change is rejected, preserve the eligibility or provider error. Do not try another spelling of the domain or a different owner's ID to force access. If the request times out, retain the original idempotency key and inspect the existing operation before attempting a fresh paid change.