Abstract: Method and system for routing EPP requests over a network are provided. The EPP request can include XML namespace information and optionally XML sub-product information. A gateway can receive the request and analyze the namespace and in some instances, sub-product information to determine the service to which the request is directed. Thereupon, the gateway can route the request to the appropriate service by consulting a routing table that can have status and connectivity information for all the available services.

Abstract: A system, method, and computer-readable medium, is described that enables a registry recovery service to retrieve zone files from a target registry, archive the zone files, publish the zone files to a managed DNS server, reconcile ownership of the zone files, and publish the zone files to a provisioning DNS server. The registry recovery service may also implement a WHOIS server for the zone and ownership information and may also implement zone specific features particular to the target registry's TLD. The registry recovery service may also enable DNSSEC extensions on the recovered registry DNS services.

Abstract: Command performance may be monitored. In a monitoring transaction, a product may be selected from a plurality of products in one group of a plurality of groups of products. Execution performance of a command by the selected product may be monitored. The monitored execution performance may be provided for determining compliance with a service level agreement for the product based on the monitored executed performance.

Abstract: A system, method, and computer-readable medium, is described that enables a registry recovery service to retrieve zone files from a target registry, archive the zone files, publish the zone files to a managed DNS server, reconcile ownership of the zone files, and publish the zone files to a provisioning DNS server. The registry recovery service may also implement a WHOIS server for the zone and ownership information and may also implement zone specific features particular to the target registry's TLD. The registry recovery service may also enable DNSSEC extensions on the recovered registry DNS services.

Abstract: A stand for a bar of soap is provided. The stand is designed to be selectively attached to an off-the-shelf bar of soap, and to then support the bar of soap over a support surface such as a counter top or a soap dish. The stand defines a base having an upper surface and an opposing lower surface. The stand also includes a plurality of through-openings formed through the base. The stand additionally includes a plurality of spikes that are placed along the upper surface of the base. The spikes are dimensioned to extend into the bar of soap when the base is compressed against a substantially flat surface of the bar of soap, and to hold the plate adjacent to the bar of soap. Finally, that stand has one or more tabs residing along the lower surface of the base. The tabs are dimensioned to support the base and a connected bar of soap above a support surface. A method of supporting a bar of soap above a support surface is also provided herein.

Abstract: Systems and methods for performing DNSSEC signing are described in which digital signature operations may be performed by a network accessible signing server that is configured to interact with a separate client application. Exemplary methods may include receiving a signing request at the signing server from the client application to sign first data. The signing server may determine an active KSK and/or an active ZSK for the first data. The first data may then be transmitted by the signing server to a digital signature modules, which may include, for example, a hardware support module, or software signing applications. The signing server may receive a digitally signed version of the first data from the digital signature module, and provide the signed first data to the client application.

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 stand for a bar of soap is provided. The stand is designed to be selectively attached to an off-the-shelf bar of soap, and to then support the bar of soap over a support surface such as a counter top or a soap dish. The stand defines a base having an upper surface and an opposing lower surface. The stand also includes a plurality of through-openings formed through the base. The stand additionally includes a plurality of spikes that are placed along the upper surface of the base. The spikes are dimensioned to extend into the bar of soap when the base is compressed against a substantially flat surface of the bar of soap, and to hold the plate adjacent to the bar of soap. Finally, that stand has one or more tabs residing along the lower surface of the base. The tabs are dimensioned to support the base and a connected bar of soap above a support surface. A method of supporting a bar of soap above a support surface is also provided herein.

Abstract: Systems and methods for performing DNSSEC signing are described in which digital signature operations may be performed by a network accessible signing server that is configured to interact with a separate client application. Exemplary methods may include receiving a signing request at the signing server from the client application to sign first data. The signing server may determine an active KSK and/or an active ZSK for the first data. The first data may then be transmitted by the signing server to a digital signature modules, which may include, for example, a hardware support module, or software signing applications. The signing server may receive a digitally signed version of the first data from the digital signature module, and provide the signed first data to the client application.

Abstract: An apparatus and method that accelerates curing of resin in a liner for a buried pipe includes an air inversion unit connected to an air compressor. The apparatus include a curing cap having an inflation port, a curing port and a drainage port. A remote source of pressurized fluid is placed in fluid communication with the inflation port. The apparatus also includes a manifold having an outlet, a first inlet in valved fluid communication with a heated fluid source, a second inlet in valved fluid communication with a pressurized fluid source and a third inlet in valved fluid communication with the drainage port. A flexible tube is slidably received by the curing port while maintaining a substantially fluid-tight seal. The flexible tube has a first end in fluid communication with the outlet of the manifold and the second end has a substantially spherical guide thereon. The second end of the flexible tube also includes a plurality of perforations to allow fluids to pass there through.

Abstract: Command performance may be monitored. In a monitoring transaction, a product may be selected from a plurality of products in one group of a plurality of groups of products. Execution performance of a command by the selected product may be monitored. The monitored execution performance may be provided for determining compliance with a service level agreement for the product based on the monitored executed performance.

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: A system and method for establishing a chain of trust from a registrant to a registry. A registrant request to a registrar to change a domain name record includes at least one registrant factor, such as a one time password. The registrar can formulate an extended EPP command that includes the factor to effectuate the change and send it to a registry. The registry can verify the at least one factor using at least one validation server. If the factor is successfully verified, the EPP can be processed by the registry. If the factor is not verified, the EPP command may not be processed and an error message may be generated and sent to the registrar.

Abstract: Method and system for routing EPP requests over a network are provided. A routing system includes multiple frontend service interfaces, one or more gateways, a management server, and a backend service platform that provides multiple application services. The frontend service interfaces are addressable using virtual IP addresses (“VIP”) and can be provided by the gateways. The routing system defines a many-to-many mapping between the frontend service interfaces and a set of services provided by the backend service platform. A requestor can send a request over EPP to a targeted service interface to access one or more backend services, by sending the request to a target IP or domain name that corresponds to a VIP associated with the targeted service interface. Using the many-to-many mapping and the VIP of the targeted service interface, the routing system can identify backend services sought by the request and provide the requestor with access to the backend services.

Abstract: A device and method for repairing the junction of a main pipe line and a lateral pipe. The device uses a series of independently controlled bladders to adjust the timing and pressure exerted by the bladders on the pipes. The device also uses a liner assembly of resin absorbent material is formed, with a tubular lateral liner connected to a concentric circular main liner. The liner also includes an opening to facilitate loading of the liner in the device. Upon loading the bladders and resin-embedded liner into a train, the device is positioned and the bladders independently inflated, either concurrently or in sequence, installing the liner assembly onto the pipe. Once the resin is cured, the bladder assembly and launcher are removed from the sewer pipe.

Abstract: A system and method for more efficiently establishing a chain of trust from a registrant to a registry. A registrant credential is associated with a Shared Registration command and is sent by a registrar to a registry. Upon successful validation, a token is generated and bound to a registrant identifier. The token is included along with the registrant identifier in subsequent discrete Shared Registration commands submitted to the registry on behalf of the registrant. The registrant thus needs to submit its credential only once for changes that require several discrete commands. Also, it is more efficient for the Shared Registration System to validate a token for a set of commands than to validate different registrant credential for each discrete command.

Abstract: A system, method, and computer-readable medium, is described that enables a registry recovery service to retrieve zone files from a target registry, archive the zone files, publish the zone files to a managed DNS server, reconcile ownership of the zone files, and publish the zone files to a provisioning DNS server. The registry recovery service may also implement a WHOIS server for the zone and ownership information and may also implement zone specific features particular to the target registry's TLD. The registry recovery service may also enable DNSSEC extensions on the recovered registry DNS services.

Abstract: A switching mechanism for a vacuum cleaner having a vacuum generator and an agitator, comprising a vacuum generator switch, an agitator switch, and a coupler for coupling the agitator switch with the vacuum generator switch such that switching of the vacuum generator switch switches the agitator switch. The switching mechanism is configured such that, switching of at least one of the agitator switch and the vacuum generator switch uncouples the agitator switch from the vacuum generator switch. The switching mechanism is further configured such that, when the vacuum generator switch and the agitator switch are uncoupled from each other and the agitator switch is in its open state, switching of the vacuum generator switch from its closed state to its open state couples the agitator switch with the vacuum generator switch.

Abstract: A system, method, and computer-readable medium, is described that enables a registry recovery service to retrieve zone files from a target registry, archive the zone files, publish the zone files to a managed DNS server, reconcile ownership of the zone files, and publish the zone files to a provisioning DNS server. The registry recovery service may also implement a WHOIS server for the zone and ownership information and may also implement zone specific features particular to the target registry's TLD. The registry recovery service may also enable DNSSEC extensions on the recovered registry DNS services.

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.