3 ms·
Since the core issue is about registered domains for natural persons it becomes a bit unclear what administrative and technical contact would mean in the contex
by belorn 8y ago
Since the core issue is about registered domains for natural persons it becomes a bit unclear what administrative and technical contact would mean in the context of this lawsuit. Most registries that I have to work with do not use those fields or have hijacked those for their own local purpose (such as local presence). ICANN however only accredit registrars for a few of the generic TLDs so there doesn't seem to be any meaningful reason to have administrative and technical contact for natural persons. Those that do fill in those fields anyway usually just copy the data from the registrant fields, or put the registrar data in as administrative and/or technical contact. Neither adds anything meaningful to whois.
When the registrant is a company it make sense to have admin and technical contact but then good practice for the last decade is to not have natural persons in those fields. If John Doe leaves the company then its a major pain to change contact information for 100+ domains, so from a pure practical reason it is better to have a company, role and the company address in the fields (except when local policy for each of the country code top-level domain demand something else). That information is naturally not protected by GDPR.