Abstract: A system, method, and computer-readable medium, is described that enables a domain name registrant the ability to exchange their existing domain in favor of a new domain without incurring additional domain registration fees and without affecting the other data fields of the existing domain. Once the domain exchange service is added to the domain registration, the registrant can exchange the domain name as often as it likes in accordance with the business rules of the registry until the domain exchange service expires.

Abstract: A computer-implemented method, computer-readable medium, and an apparatus operable to perform the method is provided for managing multiple provisioned domain name system (“DNS”) registry objects. The method can include receiving, at a DNS registry, a multiple domain extensible provisioning protocol (“EPP”) command from a registrar on behalf of a registrant to perform an action for each provisioned DNS registry object of the multiple provisioned DNS registry objects; comparing the action with one or more allowable actions in a policy maintained by the registry; determining, by a processor, that the action is allowable based on the comparing; and performing, based on the determining, the action on each of the provisioned DNS registry objects in one transaction.

Abstract: A method for administering a top-level domain by analyzing domain name registrations for requests for suspicious or malicious domain names. A request to register a domain name is received. The requested domain name's information may be stored in a registry database. The requested domain name may also be conditionally stored in the domain name system (DNS) zone. The requested domain name is compared to a list of botnet domain names stored in a watch list database. If the requested domain name corresponds to one of the botnet domain names, the requested domain name is prevented from being added to the DNS zone or is removed from the DNS zone, if it has already been stored there. The information regarding the requested domain name is stored in the registry database, even if the domain name does not ultimately stay in the DNS zone.

Abstract: Systems and methods of performing incremental DNSSEC signing at a registry are described in which digital signature operations may be performed as part of a single transaction including DNS add, update, and/or delete operations and the like. Exemplary methods may include receiving a domain command from a requester, the domain command including an identifier of a domain. The received domain command may be executed with respect to data stored by the registry for the domain. As part of an individual transaction including the execution of the domain command, the registry may also sign DNSSEC records for the domain using a private key of an authoritative server. After the DNSSEC records have been signed, the registry may incrementally publish the signed DNSSEC records to a separate server.

Abstract: A system and method for modifying a bulk set of domain names through bulk operations. A request to modify a bulk set of data associated with domain names is received by a registry. A bulk processing engine associated with the registry can analyze the requested update job, and enforce compliance with a set of policies governing the operation of registry. A priority level can also be assigned to the requested job, so that it will be executed before or after other pending jobs. The user can likewise provide user-supplied policies, which can also be validated against the set of registry policies. Data faults can be reduced or eliminated, and update operations can be performed by comparatively inexperienced personnel.

Abstract: A method for administering a top-level domain by analyzing domain name registrations for requests for suspicious or malicious domain names. A request to register a domain name is received. The requested domain name's information may be stored in a registry database. The requested domain name may also be conditionally stored in the domain name system (DNS) zone. The requested domain name is compared to a list of botnet domain names stored in a watch list database. If the requested domain name corresponds to one of the botnet domain names, the requested domain name is prevented from being added to the DNS zone or is removed from the DNS zone, if it has already been stored there. The information regarding the requested domain name is stored in the registry database, even if the domain name does not ultimately stay in the DNS zone.

Abstract: Systems, methods, and apparatuses consistent with the invention relate to protecting namespaces. In one exemplary implementation, the systems, methods, and apparatuses may validate whether or not there is consistency of sponsorship between a first namespace and a second namespace grouped with the first namespace, and perform an action related to the first namespace if there is consistency of sponsorship.

Abstract: Systems and methods for registering a domain, including Internationalized Domain Names (IDNs), including receiving a request to register an IDN and determining a language category of the request. Code points of the request are converted to yield a generalized variant of the IDN. The generalized variant is compared to a stored database of registered IDNs that may include similar generalized variants of the registered IDNs. Based on the comparison, it is determined whether or not to resister the IDN. In the case the that IDN registration is allowed, the generalized variant of the IDN may be stored in the database to protect against later registration by similar IDNs. Converting the code points of the request may include identifying corresponding code points of variants within the language category, and converting each of the code points of the requested IDN based on a deterministic algorithm applied to the corresponding code points.

Abstract: A system, method, and computer-readable medium enable a domain name or host name registry to effectively manage status codes associated with the domain or host. Status codes are organized into status sets that can be added, removed, activated, or deactivated in accordance with a suitable change request. The status codes corresponding to a removed status set that are also enabled according to other active status sets are not removed when the removal of the status set is processed.

Abstract: A system, method, and computer-readable medium, is described that enables a domain name registrant the ability to exchange their existing domain in favor of a new domain without incurring additional domain registration fees and without affecting the other data fields of the existing domain. Once the domain exchange service is added to the domain registration, the registrant can exchange the domain name as often as it likes in accordance with the business rules of the registry until the domain exchange service expires.

Abstract: Systems and methods for registering a domain, including Internationalized Domain Names (IDNs), including receiving a request to register an IDN and determining a language category of the request. Code points of the request are converted to yield a generalized variant of the IDN. The generalized variant is compared to a stored database of registered IDNs that may include similar generalized variants of the registered IDNs. Based on the comparison, it is determined whether or not to resister the IDN. In the case the that ION registration is allowed the generalized variant of the IDN may be stored in the database to protect against later registration by similar IDNs. Converting the code points of the request may include identifying corresponding code points of variants within the language category, and converting each of the code points of the requested IDN based on a deterministic algorithm applied to the corresponding code points.