Protect intellectual property (IP) rights across namespaces

1. A system for validating a consistency of sponsorship comprising a memory device storing instructions that, when executed by a processor, cause the processor to perform operations comprising:

obtaining, at a server of a Domain Name System (DNS) registry, over a network, a request for a domain service, wherein the request is from a client device;

providing the request for domain services from a server of a DNS registry to a processing unit of the DNS registry, wherein the processing unit performs operations comprising:

determining, by the DNS registry, that a second-level domain label of a requested domain name in a first top level domain is related to a second-level domain label of an existing domain name in a second top level domain that is grouped in a top level domain database with the first top level domain;

validating consistency of sponsorship between the requested domain name in the first top level domain and the existing domain name in the second top level domain;

based on validating the consistency of sponsorship:

grouping the requested domain name in the first top level domain with the existing domain name in the second top level domain, and

linking the requested domain name in the first top level domain with the existing domain name in the second top level domain in a linked domain database associated with the DNS registry; and

providing, to the client device over the network, a result of the request to a client device.

2. The system of claim 1 , wherein validating consistency of sponsorship comprises:

if the first top level domain and the second top level domain are thin: validating that a first registrar associated with the first top level domain and a second registrar associated with the second top level domain are related; and

if the first top level domain and the second top level domain are thick: validating that (1) the first registrar and the second registrar are related; and (2) a first registrant associated with the first top level domain and a second registrant associated with the second top level domain are related.

3. The system of claim 2 ,

wherein validating that the first registrar associated with the first top level domain and the second registrar associated with the second top level domain are related comprises: validating that the first registrar associated with the first top level domain and the second registrar associated with the second top level domain are the same,

wherein validating that (1) the first registrar and the second registrar are related and (2) the first registrant associated with the first top level domain and the second registrant associated with the second top level domain are related comprises: validating that (1) the first registrar and the second registrar are the same and (2) the first registrant associated with the first top level domain and the second registrant associated with the second top level domain are the same.

4. The system of claim 1 , wherein the operations further comprise:

registering one or more variants of an internationalized domain name with a shared top level domain in the top level domain database.

5. The system of claim 1 , wherein the operations further comprise:

determining whether a variant of a requested second level domain name is stored in a variant database, wherein the variant database is configured to store information related to variants of second level domain labels.

6. The system of claim 1 , further comprising using one or more extensible provisioning protocol (EPP) commands, wherein the one or more extensible provisioning protocol (EPP) commands comprises a domain check command that returns an availability or registered information across a set of grouped top level domains.

7. The system of claim 1 , wherein the operations further comprise:

determining that a variant grouped with the requested domain name exists in the first top level domain or the second top level domain.

8. The system of claim 1 , wherein one or more extensible provisioning protocol (EPP) commands are used to update the top level domain database and the linked domain database.

9. The system of claim 2 , wherein the operations further comprise:

if there is not consistency of sponsorship, determining whether a consent holder has given consent to allow at least one of the first registrant and the first registrar to register the requested domain name;

if the consent holder has given consent, allowing the at least one of the first registrant and the first registrar to register the requested domain name; and

if the consent holder has not given consent, not allowing the at least one of the first registrant and the first registrar to register the requested domain name.

10. The system of claim 9 , wherein the operations further comprise:

validating a received consent identifier by determining whether the received consent identifier is associated with a stored consent identifier, wherein the first registrant is allowed to register the requested domain name if the received consent identifier is validated.

11. The system of claim 9 , wherein the consent holder is automatically assigned based on whether the second top level domain is thin or thick.

12. A method for validating a consistency of sponsorship comprising:

obtaining, at a server of a Domain Name System (DNS) registry, over a network, a request for a domain service, wherein the request is from a client device;

providing the request to a processing unit of the DNS registry;

determining, by the DNS registry, that a second-level domain label of a requested domain name in a first top level domain is related to a second-level domain label of an existing domain name in a second top level domain that is grouped in a top level domain database with the first top level domain;

validating consistency of sponsorship between the requested domain name in the first top level domain and the existing domain name in the second top level domain;

based on validating the consistency of sponsorship: grouping the requested domain name in the first top level domain with the existing domain name in the second top level domain and linking the requested domain name in the first top level domain with the existing domain name in the second top level domain in a linked domain database associated with the DNS registry; and

providing, to the client device over the network, a result of the request.

13. The method of claim 12 , wherein validating consistency of sponsorship comprises:

if the first top level domain and the second top level domain are thin: validating that a first registrar associated with the first top level domain and a second registrar associated with the second top level domain are related; and

if the first top level domain and the second top level domain are thick: validating that (1) the first registrar and the second registrar are related; and (2) a first registrant associated with the first top level domain and a second registrant associated with the second top level domain are related.

14. The method of claim 13 ,

wherein validating that the first registrar associated with the first top level domain and the second registrar associated with the second top level domain are related comprises validating that the first registrar associated with the first top level domain and the second registrar associated with the second top level domain are the same,

wherein validating that (1) the first registrar and the second registrar are related and (2) the first registrant associated with the first top level domain and the second registrant associated with the second top level domain are related comprises validating that (1) the first registrar and the second registrar are the same and (2) the first registrant associated with the first top level domain and the second registrant associated with the second top level domain are the same.

15. The method of claim 12 , further comprising:

registering one or more variants of an internationalized domain name with a shared top level domain in the top level domain database.

16. The method of claim 12 , further comprising:

determining whether a variant of a requested second level domain name is stored in a variant database, wherein the variant database is configured to store information related to variants of second level domain labels.

17. The method of claim 12 , further comprising using one or more extensible provisioning protocol (EPP) commands, wherein the one or more extensible provisioning protocol (EPP) commands comprises a domain check command that returns an availability or registered information across a set of grouped top level domains.

18. One or more non-transitory computer-readable media for validating a consistency of sponsorship comprising a plurality of instructions that, in response to execution by a processor, cause the processor to perform operations comprising:

obtaining, at a server of a Domain Name System (DNS) registry, over a network, a request for a domain service, wherein the request is from a client device;

providing the request to a processing unit of the DNS registry;

determining, by the DNS registry, that a second-level domain label of a requested domain name in a first top level domain is related to a second-level domain label of an existing domain name in a second top level domain that is grouped in a top level domain database with the first top level domain;

validating consistency of sponsorship between the requested domain name in the first top level domain and the existing domain name in the second top level domain;

based on validating the consistency of sponsorship: grouping the requested domain name in the first top level domain with the existing domain name in the second top level domain and linking the requested domain name in the first top level domain with the existing domain name in the second top level domain in a linked domain database associated with the DNS registry; and

providing, to the client device over the network, a result of the request.

19. The one or more non-transitory computer-readable media of claim 18 , wherein validating consistency of sponsorship comprises:

if the first top level domain and the second top level domain are thin: validating that a first registrar associated with the first top level domain and a second registrar associated with the second top level domain are related; and

if the first top level domain and the second top level domain are thick: validating that (1) the first registrar and the second registrar are related; and (2) a first registrant associated with the first top level domain and a second registrant associated with the second top level domain are related.

20. The one or more non-transitory computer-readable media of claim 19 , wherein validating that the first registrar associated with the first top level domain and the second registrar associated with the second top level domain are related comprises validating that the first registrar associated with the first top level domain and the second registrar associated with the second top level domain are the same,

wherein validating that (1) the first registrar and the second registrar are related and (2) the first registrant associated with the first top level domain and the second registrant associated with the second top level domain are related comprises validating that (1) the first registrar and the second registrar are the same and (2) the first registrant associated with the first top level domain and the second registrant associated with the second top level domain are the same.