Abstract: A method, system, and computer-readable memory containing instructions include receiving a DNS request containing authentication information, validating the authentication information, determining an appropriate action to take based on the validating status, and taking the appropriate action. Actions may include responding with an individualized network layer address or service location address, delaying sending a response message, sending a network layer address or service location address corresponding to a site containing authentication information, and sending a response with a network layer address or service location address with a web address configured to mimic the website related to the requested resource.

Abstract: A technique for facilitating registration of an internet domain name with the domain name system (DNS) is presented. The technique can include receiving a request to register an encoding domain name with the DNS, the encoding domain name including an indication of a temporal event and of a target domain name. The technique can also include registering the encoding domain name to a registrant, where the registering the encoding domain name confers to the registrant a right to register the target domain name upon specified conditions, where the specified conditions include an occurrence of the temporal event. The technique can also include receiving a request initiated by the registrant to register the target domain name, and registering the target domain name to the registrant after satisfaction of the specified conditions.

Abstract: Provided is a method for providing Registration Data Access Protocol (“RDAP”) responses. The method includes obtaining, at a RDAP client over a network, a RDAP query for RDAP data from a user; providing, by the RDAP client, the RDAP query to one or more thick RDAP services; obtaining an answer to the RDAP query from the one or more thick RDAP services; and providing the answer to the user.

Abstract: Embodiments relate to systems, devices, and computing-implemented methods for dynamically allocating domain name acquisition resources by receiving indications of available domain name acquisition resources and available time windows from registrars, receiving, from devices, requests for available domain name acquisition resources during requested time windows, determining lists of domain name acquisition resources available during the requested time window, transmitting, to the devices, the lists of available domain name acquisition resources, receiving, from the devices, selections of the available domain name acquisition resources, specified time windows, and indications of domain names to request during the specified time windows, generating and transmitting communications to the registrars, where the communications result in the registrars sending a plurality of requests for the domain names to a domain name registry during the specified time windows.

Abstract: System, apparatus, methods, and computer-readable medium for generating a verification code related to a registry operation request are provided. A verification process may be performed to determine if a verification request related to a registry operation is to be approved. If the request is to be approved, a verification code is generated that includes identifying information of a verification service provider and a code indicating that the request has been verified.

Abstract: Embodiments relate to systems, devices, and computer-implemented methods for providing secure access to a shared registration system of a domain name registry by generating authorization information associated with a domain name, storing the authorization information in an archive, receiving, from a non-registrar service provider, a request for access to functionality of a shared registration system of the domain name registry, where the request is associated with the domain name and includes authorization information, determining whether the received authorization information is valid using the archived authorization information, and allowing the non-registrar service provider access to the functionality of the SRS based on a determination that the second authorization information is valid.

Abstract: A method of recovering a registry includes accessing a plurality of registry zone files for the registry and archiving, on a first periodic basis, the plurality of registry zone files. Each of the registry zone files includes at least domain names, registrar IDs, and status information represented in a first predetermined format. The method also includes accessing bulk WHOIS data for the registry and archiving, on a second periodic basis, the bulk WHOIS data. The bulk WHOIS data includes at least nameserver server names, IP addresses, and status information represented in a second predetermined format. The method further includes validating one of the plurality of archived registry zone files based on a comparison between the plurality of registry zone files and the bulk WHOIS data, publishing the validated registry zone file to a second registry's nameservers, initiating a root zone change request, and updating authoritative nameservers.

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 method, system, and computer-readable memory containing instructions include receiving a DNS request containing information related to user-specific information, device-specific information, and/or authentication information, analyzing the information, determining an appropriate action to take based on analyzing the status, and taking the appropriate action. Actions may include responding with an individualized network layer address or service location address, delaying sending a response message, sending a network layer address or service location address corresponding to a site containing authentication information, and sending a response with a network layer address or service location address with a web address configured to mimic the website related to the requested resource.

Abstract: A method, system, and computer-readable memory containing instructions include receiving a DNS request containing information related to user-specific information, device-specific information, and/or authentication information, analyzing the information, determining an appropriate action to take based on analyzing the status, and taking the appropriate action. Actions may include responding with an individualized network layer address or service location address, delaying sending a response message, sending a network layer address or service location address corresponding to a site containing authentication information, and sending a response with a network layer address or service location address with a web address configured to mimic the website related to the requested resource.

Abstract: A system, method, and computer-readable medium, is described that implements a repository object history (“WhoWas”) service that receives a WhoWas query to retrieve historical information about a repository object's change history, including a domain's registration activity. The WhoWas service searches repository object history information, formats it, and returns the results. The WhoWas service may be restricted to authorized users and may charge a fee for use. The service may also perform statistical data gathering based on historical WhoWas information, including on subsets of domains based on particular domain characteristics. In addition, historic IP address information and location information may be gathered and returned.

Abstract: A method, system, and computer-readable memory containing instructions include receiving a DNS request containing authentication information, validating the authentication information, determining an appropriate action to take based on the validating status, and taking the appropriate action. Actions may include responding with an individualized network layer address or service location address, delaying sending a response message, sending a network layer address or service location address corresponding to a site containing authentication information, and sending a response with a network layer address or service location address with a web address configured to mimic the website related to the requested resource.

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 technique is provided for designing and evaluating service models for components, functions, subsystems and field replaceable units in a complex machine system. At a component or item level, each model identifies various items, failure modes, and so forth which may be the root cause of anticipated serviceable events or faults. The design tools permit numerous interfaces to be used in the design of service models, and in the evaluation of the degree to which the models address detectability and isolation capabilities for the root causes of serviceable events and faults.

Abstract: Devices comprising a plug positioned within a housing to regulate air within a container, for example, plastic storage containers or bags. One embodiment utilizes a plug that occludes an opening in a housing. The plug is displaced from the opening to inject or evacuate air from a container. An alternative embodiment utilizes a plug having air channels therein which can be sealed once air has been injected into or evacuated from a container. The devices are utilized with hose adaptors connected to vacuum or air hoses having specialized hose tips for coupling with the housing.

Abstract: A device comprising a plug positioned within a housing to regulate air within a container, for example, plastic storage containers or bags. The plug is positioned within the housing to occlude a port hole in the housing. The housing is positioned within a container so the port hole faces a wall of the container. A hole is created in said container above the port hole. To evacuate or inject air into the container, a hose adaptor with a specialized hose tip is connected to a vacuum or air hose. When inserted into the port hole, the hose tip temporarily displaces the plug from the port hole. Vents within the housing allow air to move through the housing and into or out of the hose tip. Removal of the hose tip allows the plug to resume position over the port hole to maintain the vacuum or air pressure within the container.

Abstract: A serviceability strategy is established that permits the definition of a plurality of service models for components, functions, subsystems and field replaceable units in a complex machine system, as well as the implementation of the models for rendering service as serviceable events and faults occur, and for improvement of the models over time. The models may be dedicated in such a manner as to be selectable for addressing detectable and isolatable root causes of serviceable events as they occur, and the proper models are selected as such events occur based upon predefined indicators. As service events arise over time and are addressed by recommendations made by each model, data is gathered and serves as the basis for evolving the models so as to more appropriately address root causes of serviceable events and faults, and to improve the selection of the models most apply suited to addressing serviceable events and faults.

Abstract: A technique is provided for designing and evaluating service models for components, functions, subsystems and field replaceable units in a complex machine system. At a component or item level, each model identifies various items, failure modes, and so forth which may be the root cause of anticipated serviceable events or faults. The design tools permit numerous interfaces to be used in the design of service models, and in the evaluation of the degree to which the models address detectability and isolation capabilities for the root causes of serviceable events and faults.