Domain name hijack protection
View Patent ↗A domain name registering entity (such as a domain registry, registrar, or reseller) or an independent proxy registration service may offer a domain name hijack protection to their actual or potential customers. When a domain name transfer request or notice is received, the domain name registering entity or the proxy registration service may ignore or decline it. Customers may be given an ability to turn the domain name hijack protection service on and off, as well as an ability to adjust a variety of settings associated with the service.
1. A system comprising a computing device coupled to a network and executing instructions causing the computing device to:
execute a database query storing, within a WHO IS database, a proxy email address associated with a registered domain name;
receive an electronic message at the proxy email address stored in the WHOIS database, a content of the electronic message comprising a domain name transfer request;
automatically forward the electronic message from the proxy email address to a registrant email address by:
executing a delete command to automatically delete the encoded electronic message; or
transmitting an electronic response message to a Uniform Resource Locator link within the content of the electronic message, the electronic response message declining the domain name transfer request.
2. The system of claim 1 , wherein the computing device is operated by a domain name registering entity or a proxy registration service provider.
3. The system of claim 1 , wherein the instructions further cause the computing device, prior to receiving the electronic message, to:
receive, from a user interface element on a Hypertext Markup Language (HTML) form on a web page, a request to apply a domain name private registration service to the registered domain name;
transmit request to a second computing device operated by a proxy registration service provider, the request comprising a proxy registration service provider contact data request;
receive a proxy registration service provider contact data;
execute a database query storing, in association, the registered domain name and the proxy registration service provider contact data; and
execute a database query storing, within the WHOIS database, the proxy registration service provider contact data.
4. The system of claim 3 , wherein the instructions further cause the computing device, prior to receiving the electronic message, to:
receive, from a user interface element on an HTML form on a web page, a proxy email request to receive at least one email message addressed to a proxy email address for the proxy registration service provider;
transmit request to a second computing device operated by a proxy registration service provider, the request comprising:
a registrant email address; and
instructions causing the second computing device to execute a database query storing, in association, the proxy email address, the registrant email address and the registered domain name;
receive the at least one email message; and
transmit the at least one email message from the proxy email address to the registrant email address.
5. The system of claim 3 , wherein the instructions executed on the computing device automatically forward the electronic message only if the instructions have executed the database query storing, within the WHOIS database, the proxy registration service provider contact data.
6. The system of claim 1 , wherein the instructions further cause the computing device to receive, from a user interface element on an HTML form on a web page, a request to automatically forward the electronic message.
7. The system of claim 1 , wherein the instructions further cause the computing device to receive, from a user interface element on an HTML form on a web page, a request to disable forwarding the electronic message.
8. The system of claim 1 , wherein the instructions further cause the computing device to transmit a notification to a client computer operated by the registrant, the notification including a message that the electronic message has been deleted or declined.
9. A method comprising the steps of:
executing, by a computing device coupled to a network, a database query storing, within a WHOIS database, a proxy email address associated with a registered domain name;
receiving, by the computing device, an electronic message at the proxy email address stored in the WHOIS database, a content of the electronic message comprising a domain name transfer request;
automatically forwarding, by the computing device, the electronic message from the proxy email address to a registrant email address by:
executing a delete command to automatically delete the electronic message; or
transmitting an electronic response message to a Uniform Resource Locator link within the content of the electronic message, the electronic response message declining the domain name transfer request.
10. The method of claim 9 , wherein the computing device is operated by a domain name registering entity or a proxy registration service provider.
11. The method of claim 9 , further comprising the steps, prior to receiving the electronic message, of:
receiving, by the computing device, from a user interface element on an HTML form on a web page, a request to apply a domain name private registration service to the registered domain name;
transmitting, by the computing device, request to a second computing device operated by a proxy registration service provider, the request comprising a proxy registration service provider contact data request;
receiving, by the computing device, a proxy registration service provider contact data;
executing, by the computing device, a database query storing, in association, the registered domain name and the proxy registration service provider contact data; and
executing, by the computing device, a database query storing, within the WHOIS database, the proxy registration service provider contact data.
12. The method of claim 11 , further comprising the steps, prior to receiving the electronic message, of:
receiving, by the computing device, from a user interface element on an HTML form on a web page, a proxy email request to receive at least one email message addressed to a proxy email address for the proxy registration service provider;
transmitting, by the computing device, a request to a second computing device operated by a proxy registration service provider, the request comprising:
a registrant email address; and
instructions causing the second computing device to execute a database query storing, in association, the proxy email address, the registrant email address and the registered domain name;
receiving, by the computing device, the at least one email message; and
transmitting, by the computing device, the at least one email message from the proxy email address to the registrant email address.
13. The method of claim 11 , wherein the instructions executed on the computing device automatically forward the electronic message only if the instructions have executed the database query storing, within the WHOIS database, the proxy registration service provider contact data.
14. The method of claim 9 , further comprising the step of receiving, by the computing device, from a user interface element on an HTML form on a web page, a request to automatically forward the electronic message.
15. The method of claim 9 , further comprising the step of receiving, by the computing device, from a user interface element on an HTML form on a web page, a request to disable forwarding the electronic message.
16. The method of claim 9 , further comprising the step of transmitting, by the computing device, a notification to a client computer operated by the registrant, the notification including a message that the electronic message has been deleted or declined.