Does this policy only apply to .COM, .NET and .JOBS or all gTLDs?
- As required by the Policy, all gTLD registrations are required to be thick.The transition from thin to thick WHOIS is required for .COM, .NET and .JOBS because they are currently providing thin Whois.
- Does this policy mean that registrars will no longer be required to run their own WHOIS server for .COM, .NET and .JOBS domain names once the data has been migrated to the registries?
- Once registrars migrate to the relevant Registry Operator all required fields of Existing Domain Names that are available in the Registrar database that enable the Registry Operator to comply with WHOIs, the registrar is no longer required to provide port-43 WHOIS service. However, registrars must maintain and continue to support a web-based WHOIS service.
- If a registrant subscribed privacy and proxy (PnP) service, does the policy require the registrar to release registrant's PnP and contact information to the registry?
No - registrars provide the privacy/proxy data to the registry, not the underlying customer or licensee information.
According to the policy section 4.7, registry operators MUST submit monthly reports for Thin to Thick Transition Progress. How should this report be submitted to ICANN?
- Please submit the monthly Transition Progress Metrics report in Comma-Separated Values (CSV) format to firstname.lastname@example.org with subject heading "Transition Progress Metrics."
Who should I contact if I have questions?
- Submit questions via email@example.com with the following subject heading “Inquiry – Thick Whois Transition Policy.”