Time based authentication codes

• US 9,479,533 B2
• Filed: 12/18/2014
• Issued: 10/25/2016
• Est. Priority Date: 12/18/2014
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Inventors: Gupta, Nitin, Beadnall, Charles
• Primary Examiner(s): HERZOG, MADHURI R
• Application Number:
  US14/575,982
• Publication Number:
  US 20160182562A1
• Time in Patent Office: 677 Days
• Field of Search: 726 1- 10, 726 26- 30, 713155-159, 713168-173, 709217-229
• US Class Current: 1/1
• CPC Class Codes: G06F 21/45 Structures or tools for the administration of authentication
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0846 using time-dependent-passwords, e.g. periodically changing passwords
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/1466 Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/0869 involving random numbers or seeds
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying

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 from a registrant of the domain name; generate the change key comprising a random string not stored on the server computer; identify the timeout period within the database; transmit the change key to: a contact for the registrant; and a domain name registry; determine whether the change key is received by the server computer during the timeout period; and if so, update the domain name.

Claims

1. A system, comprising:

a network configured to provide a plurality of transmissions between a registry, a registrar and a registrant associated with a domain name;

a database communicatively coupled to the network and storing a timeout period during which a change key authorizing an update to a domain name is valid, the update comprising a modification of at least one attribute of the domain name;

a server computer communicatively coupled to the network and configured to;

receive a request from a registrant of the domain name operating a client computer coupled to the network requesting the change key;

generate the change key comprising a randomized text string, wherein the change key is not stored on the server computer;

identify the timeout period within the database;

transmit the change key to;

a contact of the registrant; and

a domain name registry;

determine whether the change key is received by the server computer during the timeout period from the registrant, thereby authorizing the registrant to modify the at least one attribute of the domain name; and

responsive to a determination that the change key is received by the server computer during the timeout period, update the domain name.

2. The system of claim 1, wherein the timeout period is stored within a user setting in the database.

3. The system of claim 1, wherein the randomized text string comprises a random set of alphanumeric characters.

4. The system of claim 1, wherein the randomized text string is generated by a domain name registrar.

5. The system of claim 1, wherein the timeout period during which the change key is valid is set by a requestor requesting the change key.

6. The system of claim 1, wherein the timeout period during which the change key is valid is calculated from an average time between receiving the change key and updating the domain name.

7. The system of claim 1, wherein the server computer is further configured to reset the change key at the end of the timeout period.

8. The system of claim 1, wherein the server computer is further configured to delete the change key at the end of the timeout period.

9. The system of claim 1, wherein the server computer is further configured to:

render, for a display on a client computer communicatively coupled to the network;

the change key; and

the timeout period; and

remove, the change key at the end of the timeout period.

10. A method, comprising the steps of:

receiving, by a server computer communicatively coupled to a network, from a registrant of a domain name operating a client computer coupled to the network, a request requesting a change key authorizing an update to the domain name, the update comprising a modification of at least one attribute of the domain name;

generating, by the server computer, the change key comprising a randomized text string, wherein the change key is not stored on the server computer;

identifying, by the server computer, in a database communicatively coupled to the network, a timeout period during which the change key is valid;

transmitting, by the at least one server computer, the change key to;

a contact of the registrant; and

a domain name registry;

determining, by the a server computer, whether the change key is received by the server computer during the timeout period from the registrant, thereby authorizing the registrant to modify the at least one attribute of the domain name; and

responsive to a determination that the change key is received by the server computer during the timeout period, updating, by the server computer, the domain name.

11. The method of claim 10, wherein the timeout period is stored within a user setting in the database.

12. The method of claim 10, wherein the randomized text string comprises a random set of alphanumeric characters.

13. The method of claim 10, wherein the randomized text string is generated by a domain name registrar.

14. The method of claim 10, wherein the timeout period during which the change key is valid is set by a requestor requesting the change key.

15. The method of claim 10, wherein the timeout period during which the change key is valid is calculated from an average time between receiving the change key and updating the domain name.

16. The method of claim 10, further comprising the step of resetting the change key at the end of the timeout period.

17. The method of claim 10, further comprising the step of deleting the change key at the end of the timeout period.

18. The method of claim 10, further comprising the steps of:

rendering, by the server computer, for a display on a client computer communicatively coupled to the network;

the change key; and

the timeout period; and

removing, by the server computer, the change key at the end of the timeout period.