Public data
Registration records
Public RDAP or WHOIS responses can include dates, registrar information, nameservers, and status codes.
Services
Privacy should reduce exposure without obscuring ownership.
Privacy and proxy options depend on the extension and provider. PLM can help clarify the technical path, while the customer remains the legal registrant and owner of their domain.
Proxy services
Privacy availability
A registrar may offer a proxy or privacy service, but its availability varies by TLD and policy.
Business records
Separate contacts
Use durable business contact and recovery processes instead of relying on a personal inbox alone.
Ownership
Customer stays owner
PLM acts as a technical manager only when separately authorized; it does not replace the customer as registrant.
Limits
Not every TLD is the same
Some registries require fields or publish different records. Do not assume a privacy option is universal or free.
Support
Ask before a record changes
Use a scoped project or support intake to discuss privacy, contacts, and security without submitting data through a public page.
Read-only lookup
Privacy can look like redaction
A missing registrant field in an RDAP response may reflect privacy or registry redaction; it is not proof of a hidden owner.
Next step
Review what is public, then get human help when it matters.
No privacy setting is changed here. Live provider data must confirm whether a specific domain and extension supports an option.