# US 12,003,606 B2 · Systems and methods for providing secure access to shared registration systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,606 B2 - Document ID: US12003606B2 - Status: Granted - Kind: B2 - Application number: 17/549,223 - Filed: 2021-12-13 - Published: 2022-03-31 - Granted: 2024-06-04 - Earliest claimed: 2015-09-03 - Assignees: VeriSign, Inc. - Applicants: Verisign, Inc. - Inventors: James F. Gould; Scott Hollenbeck; Patrick Kane; Joseph Waldron - Web page: https://patentgrep.com/patent/US12003606B2 ## CPC - H04L 67/63: Routing a service request depending on the request content or context - H04L 61/302: {Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]} - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04W 12/08: Access security - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Embodiments relate to systems, devices, and computer-implemented methods for providing secure access to a shared registration system of a domain name registry by generating authorization information associated with a domain name, storing the authorization information in an archive, receiving, from a non-registrar service provider, a request for access to functionality of a shared registration system of the domain name registry, where the request is associated with the domain name and includes authorization information, determining whether the received authorization information is valid using the archived authorization information, and allowing the non-registrar service provider access to the functionality of the SRS based on a determination that the second authorization information is valid. ## Claims ### Claim 1 A computer-implemented method, comprising: receiving, at a registry, a request for access to a domain management function, wherein the request includes authorization information to allow a non-registrar service provider to provide a specified service for a domain name; determining whether the authorization information is valid based on the authorization information and an electronically stored authorization information associated with the domain name; and allowing the non-registrar service provider access to the domain management function based on a determination that the authorization information is valid, wherein the domain management function is based on the specified service, wherein the registry is a domain name registry configured to publish zone information used to resolve a domain name query. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the request for access to the domain management function comprises a request for access to a shared registration system (SRS) of the domain name registry. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein access to the domain management function is through an Extensible Provisioning Protocol (EPP). ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein the request originates from the non-registrar service provider. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, wherein the request originates from a registrant of the domain name. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein the authorization information is unique to the specified service. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein the specified service includes publishing Domain Name System (DNS) records and does not include updating domain name data, creating domain data, deleting domain data, and renewing domain data. ### Claim 8 A computer server system comprising: a processing system of a device comprising one or more processors; and a memory system comprising one or more computer-readable media, wherein the one or more computer-readable media contain instructions that, when executed by the processing system, cause the processing system to perform operations comprising: receiving, at a registry, a request for access to a domain management function, wherein the request includes authorization information to allow a non-registrar service provider to provide a specified service for a domain name; determining whether the authorization information is valid based on the authorization information and an electronically stored authorization information associated with the domain name; and allowing the non-registrar service provider access to the domain management function based on a determination that the authorization information is valid, wherein the domain management function is based on the specified service, wherein the registry is a domain name registry configured to publish zone information used to resolve a domain name query. ### Claim 9 (depends on 8) The computer server system of claim 8, wherein the request for access to the domain management function is a request for access to a shared registration system (SRS) of the domain name registry. ### Claim 10 (depends on 8) The computer server system of claim 8, wherein access to the domain management function is through an Extensible Provisioning Protocol (EPP). ### Claim 11 (depends on 8) The computer server system of claim 8, wherein the request originates from the non-registrar service provider. ### Claim 12 (depends on 8) The computer server system of claim 8, wherein the request originates from a registrant of the domain name. ### Claim 13 (depends on 8) The computer server system of claim 8, wherein the authorization information is unique to the specified service. ### Claim 14 (depends on 8) The computer server system of claim 8, wherein the specified service includes publishing Domain Name System (DNS) records and does not include updating domain name data, creating domain data, deleting domain data, and renewing domain data. ### Claim 15 A non-transitory computer readable storage medium comprising instructions for causing one or more processors of at least one server computer to: receive, at a registry, a request for access to a domain management function, wherein the request includes authorization information to allow a non-registrar service provider to provide a specified service for a domain name; determine whether the authorization information is valid based on the authorization information and an electronically stored authorization information associated with the domain name; and allow the non-registrar service provider access to the domain management function based on a determination that the authorization information is valid, wherein the domain management function is based on the specified service, wherein the registry is a domain name registry configured to publish zone information used to resolve a domain name query. ### Claim 16 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the request for access to the domain management function is a request for access to a shared registration system (SRS) of the domain name registry. ### Claim 17 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein access to the domain management function is through an Extensible Provisioning Protocol (EPP). ### Claim 18 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the request originates from the non-registrar service provider. ### Claim 19 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the request originates from a registrant of the domain name. ### Claim 20 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the authorization information is unique to the specified service.