IP Library › Granted Patent US 12,323,384
Granted Patent B1
US 12,323,384 · App. 18/126,269 · Granted Jun 3, 2025

Systems and methods for secure authorization of registry functions

Inventors: James Gould (Reston, VA); Srikanth Veeramachaneni (Reston, VA); Matthew Pozun (Reston, VA)
Assignee: VeriSign, Inc.
H04L61/302H04L9/3247H04L61/3025H04L61/4511
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,323,384
App. No.
18/126,269
Granted
Jun 3, 2025
Kind
B1
Abstract

Systems, methods, and computer-readable storage media for enabling secure transfer of Internet domains between registrars. An example method can include receiving, at a registry, a request from a first registrar for information associated with an object recorded in the registry and registered by the first registrar, then generating, at the registry, an authorization code, the authorization code having an expiration. The registry can then transmit, to the first registrar, the authorization code, which in turn can be given to the registrant. The registrant can forward the authorization code to the second registrar, and the registry can receive, from a second registrar before the expiration has been reached: the authorization code and a transfer request for the object, the transfer request identifying a transfer of the object from the first registrar to the second registrar. At that point the registry can verify the authorization code authorize the transfer request of the object from the first registrar to the second registrar.

Claims (43)

1. A method for securely authorizing a registry operation comprising:

generating, at a registry, an authorization code, wherein the authorization code is configured to authorize a registry function;

transmitting, from the registry to a first registrar, the authorization code;

receiving, from a second registrar:

the authorization code; and

a request for the registry function on a first registry object;

verifying the authorization code; and

authorizing the registry function for the first registry object.

2. The method of claim 1 , wherein the authorization code comprises at least one attribute, wherein the at least one attribute comprises one or more predetermined registry functions.

3. The method of claim 2 , wherein the one or more predetermined registry functions are based on a request from the first registrar.

4. The method of claim 2 , wherein the one or more predetermined registry functions are based on content of a registry command.

5. The method of claim 4 , wherein the registry command is a domain info command.

6. The method of claim 2 , wherein the one or more predetermined registry functions defaults to a registrar transfer.

7. The method of claim 2 , wherein the one or more predetermined registry functions comprises registrar-transfer, re-sale transfer, or dnsprovider-transfer.

8. The method of claim 2 , wherein the at least one attribute further comprises an expiration of the authorization code.

9. The method of claim 8 , wherein the at least one attribute further comprises an identifier of a domain name.

10. The method of claim 1 , wherein the authorization code comprises at least one attribute, wherein the at least one attribute comprises an expiration of the authorization code, wherein the authorization code is received from the second registrar before the expiration of the authorization code.

11. A system comprising:

a processor; and

a non-transitory computer-readable storage medium having instructions stored which, when executed by the processor, cause the processor to perform operations comprising:

generating, at a registry, an authorization code, wherein the authorization code is configured to authorize a registry function;

transmitting, from the registry to a first registrar, the authorization code;

receiving, from a second registrar:

the authorization code; and

a request for the registry function on a first registry object;

verifying the authorization code; and

authorizing the registry function for the first registry object.

12. The system of claim 11 , wherein the authorization code comprises at least one attribute, wherein the at least one attribute comprises one or more predetermined registry functions.

13. The system of 12 , wherein the one or more predetermined registry functions are based on a request from the first registrar.

14. The system of claim 12 , wherein the one or more predetermined registry functions are based on content of a registry command.

15. The system of claim 12 , wherein the one or more predetermined registry functions defaults to a registrar transfer.

16. A non-transitory computer-readable storage medium having instructions stored which, when executed by a computing device, cause the computing device to perform operations comprising:

generating, at a registry, an authorization code, wherein the authorization code is configured to authorize a registry function;

transmitting, from the registry to a first registrar, the authorization code;

receiving, from a second registrar:

the authorization code; and

a request for the registry function on a first registry object;

verifying the authorization code; and

authorizing the registry function for the first registry object.

17. The non-transitory computer-readable storage medium of claim 16 , wherein the authorization code comprises at least one attribute, wherein the at least one attribute comprises one or more predetermined registry functions.

18. The non-transitory computer-readable storage medium of claim 17 , wherein the one or more predetermined registry functions are based on a request from the first registrar.

19. The non-transitory computer-readable storage medium of claim 17 , wherein one or more predetermined registry functions are based on content of a registry command.

20. The non-transitory computer-readable storage medium of claim 17 , wherein one or more predetermined registry functions defaults to a registrar transfer.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 2, 2023
From: GOULD, JAMES; VEERAMACHANENI, SRIKANTH; POZUN, MATTHEW
To: VERISIGN, INC.
Reel/Frame 063847/0224 →
Continuity (2)
Continuation 17720378 · Apr 14, 2022
Continuation 16399438 · Apr 30, 2019
References Cited (21)
US 8769655B2 · Gould et al. · 2014 [cited by applicant]
US 8904519B2 · Essawi et al. · 2014 [cited by applicant]
US 10402876B1 · Merdinger · 2019 [cited by examiner]
US 10542117B2 · Gould et al. · 2020 [cited by applicant]
US 10560427B2 · Waldron et al. · 2020 [cited by applicant]
US 11329951B2 · Gould et al. · 2022 [cited by applicant]
US 11616756B1 · Gould et al. · 2023 [cited by applicant]
US 20020057678A1 · Jiang et al. · 2002 [cited by applicant]
US 20080126097A1 · Sarid · 2008 [cited by examiner]
US 20140283106A1 · Stahura et al. · 2014 [cited by applicant]
US 20170187673A1 · Kaliski, Jr. et al. · 2017 [cited by applicant]
US 20180062856A1 · Kaliski, Jr. et al. · 2018 [cited by applicant]
US 20180063141A1 · Kaliski, Jr. et al. · 2018 [cited by applicant]
US 20200153938A1 · Gould et al. · 2020 [cited by applicant]
US 20200252371A1 · Ptalis · 2020 [cited by examiner]
US 20210234696A1 · Kaliski, Jr. et al. · 2021 [cited by applicant]
Gould et al., Extensible Provisioning Protocol (EPP) Secure Authorization Information for Transfer. draft-ietf-regext-secure-authinfo-transfer-06. Network Working Group. 30 pages, Mar. 8, 2021. [cited by applicant]
Gould, Verification Code Extension for the Extensible Provisioning Protocol (EPP). draft-ietf-regext-verificationcode-06. Network Working Group. 38 pages, Jan. 10, 2019. [cited by applicant]
Hollenbeck, Extensible Provisioning Protocol (EPP) Contact Mapping. Network Working Group. 41 pages, Aug. 2009. [cited by applicant]
Hollenbeck, Extensible Provisioning Protocol (EPP) Domain Name Mapping. Network Working Group. 44 pages, Aug. 2009. [cited by applicant]
Lozano, Mark and Signed Mark Objects Mapping. Internet Engineering Task Force (IETF). 24 pages, Jun. 2016. [cited by applicant]