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 modification to domain name management; analyze metadata and registrant accounts associated with the request; determine whether related domain name activities indicate high or low risk of malicious behavior; if high risk, the request may be queued for manual review; on manual review, if the request is deemed high risk, an attempt to contact the registrant may be made; if unsuccessful, or if the registrant verifies an invalid request, the request may be cancelled. if the behavior or request is low risk, and/or if the registrant confirms the request is valid, the request may be approved and fulfilled.

Abstract: A system and method for modifying domain name system (DNS) templates are presented. A DNS template database is configured to store DNS templates. A DNS record database is configured to store a plurality of DNS records for a plurality of domain names. A host computer server is configured to receive an electronic signal encoding a request containing a modification to a DNS template from a user, the DNS template being stored in the DNS template database, access the DNS template database to modify the DNS template according to request containing the modification to create a modified DNS template, identify a plurality of domain names using the DNS template, and, for each domain name in the plurality of domain names, access the DNS record database to at least one of modify and create a DNS record for the domain name using the modified DNS template.

Abstract: A registrar may authenticate a registrant and allow the registrant to access a registrant customer account. The registrant customer account is private (accessible only by the registrant) and displays domain names and/or settings for the domain names registered to the registrant. The registrant may change domain name settings, such as renewals or DNS, from the registrant customer account. The registrar may generate one or more suggested domain names that are derived from the one or more domain names registered to the registrant. When the registrar detects an interest in a domain name registered to the registrant, the registrar may immediately thereafter display one or more suggested domain names that were derived from that domain name registered to the registrant for registration. If selected by the registrant, the registrar may register the selected suggested domain names to the registrant through a 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 modification to domain name management; analyze metadata and registrant accounts associated with the request; determine whether related domain name activities indicate high or low risk of malicious behavior; if high risk, the request may be queued for manual review; on manual review, if the request is deemed high risk, an attempt to contact the registrant may be made; if unsuccessful, or if the registrant verifies an invalid request, the request may be cancelled. if the behavior or request is low risk, and/or if the registrant confirms the request is valid, the request may be approved and fulfilled.

Abstract: A registrar may authenticate a registrant and allow the registrant to access a registrant customer account. The registrant customer account is private (accessible only by the registrant) and displays domain names and/or settings for the domain names registered to the registrant. The registrant may change domain name settings, such as renewals or DNS, from the registrant customer account. The registrar may generate one or more suggested domain names that are derived from the one or more domain names registered to the registrant. When the registrar detects an interest in a domain name registered to the registrant, the registrar may immediately thereafter display one or more suggested domain names that were derived from that domain name registered to the registrant for registration. If selected by the registrant, the registrar may register the selected suggested domain names to the registrant through a registry.

Abstract: A registrar may authenticate a registrant and allow the registrant to access a registrant customer account. The registrant customer account is private (accessible only by the registrant) and displays domain names and/or settings for the domain names registered to the registrant. The registrant may change domain name settings, such as renewals or DNS, from the registrant customer account. The registrar may generate one or more suggested domain names that are derived from the one or more domain names registered to the registrant. When the registrar detects an interest in a domain name registered to the registrant, the registrar may immediately thereafter display one or more suggested domain names that were derived from that domain name registered to the registrant for registration. If selected by the registrant, the registrar may register the selected suggested domain names to the registrant through a 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 modification to domain name management; analyze metadata and registrant accounts associated with the request; determine whether related domain name activities indicate high or low risk of malicious behavior; if high risk, the request may be queued for manual review; on manual review, if the request is deemed high risk, an attempt to contact the registrant may be made; if unsuccessful, or if the registrant verifies an invalid request, the request may be cancelled. if the behavior or request is low risk, and/or if the registrant confirms the request is valid, the request may be approved and fulfilled.

Abstract: A system and method for domain name system (DNS) restore points are presented. A DNS record database is configured to store a plurality of DNS records for a plurality of domain name. A host computer server is configured to detect a change in a DNS record for a domain name, and, upon detecting the change in the DNS record, encode, without any user input, at least one DNS setting from the DNS record for the domain name into a data storage file. The host computer server is configured to prompt a user to provide a description, and store the data storage file containing the at least one DNS setting in a database in association with the description.

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: A method is provided to programmatically configure a Registrar to register domain names having different TLDs. The Registrar may store business rules, such as a minimum and a maximum registration period and a registration grace period, for one and only one top-level domain (TLD), in one and only one electronic record. The Registrar may have a plurality of different electronic records, each with businesses rules for a different TLD. The Registrar may programmatically use one of the electronic records to update or add TLD registration capabilities for the TLD associated with the electronic record used. In this manner, business rules for a single TLD may be updated or added in a single electronic record, which reduces the chance of corrupting the registration capabilities of the Registrar regarding the registration of domain names having other TLDs.

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: 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: A system and method for domain name system (DNS) templates are presented. A DNS template database stores DNS templates. A DNS record database stores a plurality of DNS records for a plurality of domain names. A host computer server receives an electronic signal encoding a request to create a DNS template from a user. The request identifies a domain name. The host computer server is configured to access the DNS record database to retrieve a DNS record for the domain name identified in the request, parse the DNS record into a plurality of DNS settings, display the plurality of DNS settings on a user interface for the user, receive, via the user interface, a selection of at least one of the DNS settings by the user, construct a DNS template using the selection of the at least one of the DNS settings, and store the DNS template in the DNS template database.

Abstract: A system and method for modifying domain name system (DNS) templates are presented. A DNS template database is configured to store DNS templates. A DNS record database is configured to store a plurality of DNS records for a plurality of domain names. A host computer server is configured to receive an electronic signal encoding a request containing a modification to a DNS template from a user, the DNS template being stored in the DNS template database, access the DNS template database to modify the DNS template according to request containing the modification to create a modified DNS template, identify a plurality of domain names using the DNS template, and, for each domain name in the plurality of domain names, access the DNS record database to at least one of modify and create a DNS record for the domain name using the modified DNS template.

Abstract: A system and method for domain name system (DNS) restore points are presented. A DNS record database is configured to store a plurality of DNS records for a plurality of domain name. A host computer server is configured to detect a change in a DNS record for a domain name, and, upon detecting the change in the DNS record, encode, without any user input, at least one DNS setting from the DNS record for the domain name into a data storage file. The host computer server is configured to prompt a user to provide a description, and store the data storage file containing the at least one DNS setting in a database in association with the description.

Abstract: A system and method are presented. A domain name registration website is provided by at least one server communicatively coupled to a network. The domain name registration website including a user interface. A query being entered by a requester into the user interface of the domain registration website is monitored. When the query being entered by the requester matches a predefined pattern, the query is used to identify a plurality of candidate domain names, and the candidate domain names are displayed for selection by the requester on the domain name registration website.

Abstract: A request is received from a requester by at least one server communicatively coupled to a network. The request is used to identify a plurality of candidate domain names. For each one of the plurality of candidate domain names, a determination is made as to whether the candidate domain name is registered. When the candidate domain name is registered, the candidate domain name is displayed in a result listing on a domain registration website hosted by the at least one server in response to the request, and a first user interface enabling the requester to submit an offer to purchase the candidate domain name is displayed. When the candidate domain name is not registered, the candidate domain name is displayed in the result listing on the domain registration website in response to the request, and a second user interface enabling the requester to purchase the candidate domain name is displayed.

Abstract: A request is received from a requester by at least one server communicatively coupled to a network. The request is used to identify a plurality of candidate domain names. For each one of the plurality of candidate domain names, a determination is made as to whether the candidate domain name is registered. When the candidate domain name is registered, the candidate domain name is displayed in a result listing on a domain registration website hosted by the at least one server in response to the request, and a first user interface enabling the requester to submit an offer to purchase the candidate domain name is displayed. When the candidate domain name is not registered, the candidate domain name is displayed in the result listing on the domain registration website in response to the request, and a second user interface enabling the requester to purchase the candidate domain name is displayed.