Abstract: A Domain Name System (DNS) provider that is not a registrar of a domain name may nonetheless request a registry (possibly via an API request from the registrar to the registry, or via a call directly to the registry) to alter a Delegation Signer (DS) record in a DNS parent zone or other data controlled by the registry. The registry preferably confirms that the DNS provider has control over a nameserver for the domain name. Using Public Key Infrastructure (PKI), the DNS provider may sign the request with a private key and store the public key in a location that confirms the DNS provider has control over the domain name or over the nameservers for the domain name. After successfully confirming the DNS provider, the registrar or registry may change the DS record so that the domain name supports Domain Name System Security Extensions (DNSSEC) or update other data with the registry.

Abstract: A registrar may determine a registration status for a domain names. The registrar may determine whether the domain name is in a zone file downloaded from a registry. Upon determining that the domain name is not in the zone file, the registrar may determine whether the domain name is in a DNS zone file created by the registrar. Upon determining that the domain name is not in the DNS zone file created by the registrar, the registrar may transmit an EPP <check> command for the domain name to the registry. The registrar may receive a first EPP <resData> element comprising an error indicating the domain name is available or a value indicating the domain name is not available. Upon receiving the value indicating the domain name is not available, the registrar may transmit an EPP <info> command for the domain name to the registry. The registrar may receive a second EPP <resData> element from the registry comprising an expiration date and a state of the domain name.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for a physical certificate authenticating a user to transfer a domain name, as well as a domain name and domain name transfer instructions; print the physical certificate, including a QR code encoding a user id, the domain name, an EPP key and the transfer instructions; lock the domain name account against modification; receive a request to execute a domain name transfer; scan the user id, the domain name, the EPP key and the transfer instructions encoded within the QR code; unlock an administrative function of the account; authenticate, via the EPP key, the domain name transfer; and execute the domain name transfer.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for a physical certificate authenticating a user to transfer a domain name, as well as a domain name and domain name transfer instructions; print the physical certificate, including a QR code encoding a user id, the domain name, an EPP key and the transfer instructions; lock the domain name account against modification; receive a request to execute a domain name transfer; scan the user id, the domain name, the EPP key and the transfer instructions encoded within the QR code; unlock an administrative function of the account; authenticate, via the EPP key, the domain name transfer; and execute the domain name transfer.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for a physical certificate authenticating a user to transfer a domain name, as well as a domain name and domain name transfer instructions and a request to register the domain name to a third party; register the domain name to the third party and update WHOIS; print the physical certificate, including a QR code encoding a user id, the domain name, an EPP key and the transfer instructions; lock the domain name account against modification; receive a request to execute a domain name transfer; scan the user id, the domain name, the EPP key and the transfer instructions encoded within the QR code; unlock an administrative function of the account; authenticate, via the EPP key, the domain name transfer; and execute the domain name transfer.

Abstract: A registrar may determine a registration status for a domain names. The registrar may determine whether the domain name is in a zone file downloaded from a registry. Upon determining that the domain name is not in the zone file, the registrar may determine whether the domain name is in a DNS zone file created by the registrar. Upon determining that the domain name is not in the DNS zone file created by the registrar, the registrar may transmit an EPP <check> command for the domain name to the registry. The registrar may receive a first EPP <resData> element comprising an error indicating the domain name is available or a value indicating the domain name is not available. Upon receiving the value indicating the domain name is not available, the registrar may transmit an EPP <info> command for the domain name to the registry. The registrar may receive a second EPP <resData> element from the registry comprising an expiration date and a state of the domain name.

Abstract: A Domain Name System (DNS) provider that is not a registrar of a domain name may nonetheless request a registry (possibly via an API request from the registrar to the registry, or via a call directly to the registry) to alter a Delegation Signer (DS) record in a DNS parent zone or other data controlled by the registry. The registry preferably confirms that the DNS provider has control over a nameserver for the domain name. Using Public Key Infrastructure (PKI), the DNS provider may sign the request with a private key and store the public key in a location that confirms the DNS provider has control over the domain name or over the nameservers for the domain name. After successfully confirming the DNS provider, the registrar or registry may change the DS record so that the domain name supports Domain Name System Security Extensions (DNSSEC) or update other data with the registry.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for a physical certificate authenticating a user to transfer a domain name, as well as a domain name and domain name transfer instructions and a request to register the domain name to a third party; register the domain name to the third party and update WHOIS; print the physical certificate, including a QR code encoding a user id, the domain name, an EPP key and the transfer instructions; lock the domain name account against modification; receive a request to execute a domain name transfer; scan the user id, the domain name, the EPP key and the transfer instructions encoded within the QR code; unlock an administrative function of the account; authenticate, via the EPP key, the domain name transfer; and execute the domain name transfer.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for a physical certificate authenticating a user to transfer a domain name, as well as a domain name and domain name transfer instructions; print the physical certificate, including a QR code encoding a user id, the domain name, an EPP key and the transfer instructions; lock the domain name account against modification; receive a request to execute a domain name transfer; scan the user id, the domain name, the EPP key and the transfer instructions encoded within the QR code; unlock an administrative function of the account; authenticate, via the EPP key, the domain name transfer; and execute the domain name transfer.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for the change key; generate the change key; separate the change key into a plurality of divisions; transmit each of the plurality of divisions to a designated contact; determine whether the plurality of divisions is received by the server computer; and if so, combine the plurality of divisions into the change key; and update the domain name.

Abstract: Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive a request for the change key; generate the change key; separate the change key into a plurality of divisions; transmit each of the plurality of divisions to a designated contact; determine whether the plurality of divisions is received by the server computer; and if so, combine the plurality of divisions into the change key; and update the domain name.

Abstract: A client computer in a communications network with a server computer assembles a record set that has a MIME declaration header with a multipart content type and a content sub-type indicative of a workflow media type. The first client computer also assembles a binary file having therein an encoded workflow specification. The record set is then transmitted with the binary file to the communications network. A second client computer on the communications network receives both the record set and the binary file and begins decoding the workflow specification. The second client computer uses an application program to execute the decoded workflow specification so as to perform all or a portion of the workflow process that is specified therein. The workflow specification is optionally written in eXtensible Mark-up Language (XML).

Abstract: A client computer in a communications network with a server computer assembles a record set that has a MIME declaration header with a multipart content type and a content sub-type indicative of a workflow media type. The first client computer also assembles a binary file having therein an encoded workflow specification. The record set is then transmitted with the binary file to the communications network. A second client computer on the communications network receives both the record set and the binary file and begins decoding the workflow specification. The second client computer uses an application program to execute the decoded workflow specification so as to perform all or a portion of the workflow process that is specified therein. The workflow specification is optionally written in extensible Mark-up Language (XML).

Abstract: A client computer in a communications network with a server computer assembles a record set that has a MIME declaration header with a multipart content type and a content sub-type indicative of a workflow media type. The first client computer also assembles a binary file having therein an encoded workflow specification. The record set is then transmitted with the binary file to the communications network. A second client computer on the communications network receives both the record set and the binary file and begins decoding the workflow specification. The second client computer uses an application program to execute the decoded workflow specification so as to perform all or a portion of the workflow process that is specified therein. The workflow specification is optionally written in Extensible Mark-up Language (XML).