Domain name hi-jack prevention
View Patent ↗A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.
1. A method, comprising:
receiving a request to move a domain name from a first account to a second account, wherein the domain name is registered to a registrant;
sending a confirmation request by a preferred contact method designated by the registrant to the registrant, wherein the confirmation request identifies the domain name; and
upon receiving an affirmative response in response to the confirmation request, moving the domain name from the first account to the second account.
2. The method of claim 1 , wherein the preferred contact method is via a mobile device of the registrant.
3. The method of claim 1 , wherein the preferred contact method is to an email account registered to the registrant.
4. The method of claim 1 , further comprising upon not receiving the affirmative response in response to the confirmation request before a predetermined time limit, sending a notification message by the preferred contact method.
5. The method of claim 1 , further comprising upon receiving the affirmative response before a predetermined time limit, sending a message by the preferred contact method to the registrant that the domain name was moved from the first account to the second account.
6. The method of claim 1 , further comprising upon receiving instructions from the registrant to enable a hi-jack prevention service, preventing the domain name from being moved from the first account to the second account until after a Registrar sends the confirmation request to the registrant by the preferred contact method and the Registrar receives the affirmative response in response to the confirmation request before a predetermined time limit.
7. A method, comprising:
receiving a request to transfer a domain name from a Losing Registrar to a Gaining Registrar, wherein the domain name is registered to a registrant;
sending an authentication code by a preferred contact method of the registrant to the registrant; and
upon not receiving the authentication code from the registrant before a predetermined time limit, not transferring the domain name from the Losing Registrar to the Gaining Registrar.
8. The method of claim 7 , further comprising upon receiving the authentication code from the registrant, transferring the domain name from the Losing Registrar to the Gaining Registrar.
9. The method of claim 7 , wherein the preferred contact method is via a mobile device.
10. The method of claim 7 , wherein the preferred contact method is to an email account.
11. The method of claim 7 , further comprising upon not receiving the authentication code before the predetermined time limit, sending a message by the preferred contact method to the registrant that the domain name was not transferred.
12. The method of claim 7 , further comprising upon receiving the authentication code before the predetermined time limit, sending a message by the preferred contact method to the registrant that the domain name was transferred.
13. The method of claim 7 , further comprising upon receiving instructions from the registrant to enable a hi-jack prevention service, preventing, by the Losing Registrar, the domain name from being transferred from the Losing Registrar to the Gaining Registrar until after a third party platform sends the authentication code to the registrant and the Gaining Registrar receives the authentication code from the registrant before the predetermined time limit.
14. A system, comprising:
a first server computer configured to:
receive a request to transfer a domain name from a Losing Registrar to a Gaining Registrar, wherein the domain name is registered to a registrant, and
sending an authentication code to the registrant; and
a second server computer configured to:
upon receiving the authentication code from the registrant, transfer the domain name from the Losing Registrar to the Gaining Registrar.
15. The system of claim 14 , wherein the second server computer is configured to, upon not receiving the authentication code before a predetermined time limit, not transfer the domain name from the Losing Registrar to the Gaining Registrar.
16. The system of claim 14 , wherein the first server computer is configured to send the authentication code via a mobile device.
17. The system of claim 14 , wherein the first server computer is configured to send the authentication code to an email account.
18. The system of claim 14 , wherein the second server computer is further configured to, upon not receiving the authentication code before a predetermined time limit, send a message to the registrant that the domain name was not transferred.
19. The system of claim 14 , wherein the second server computer is further configured to, upon receiving the authentication code, send a message to the registrant that the domain name was transferred.
20. The system of claim 14 , wherein the first server computer is further configured to, upon receiving instructions from the registrant to enable a hi-jack prevention service, prevent the domain name from being transferred from the Losing Registrar to the Gaining Registrar until after the Gaining Registrar receives the authentication code.