Domain Name Hijack Protection

• US 20140259118A1
• Filed: 04/29/2014
• Published: 09/11/2014
• Est. Priority Date: 08/30/2002
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Inventors: Parsons, Robert R.
• Granted Patent: US 9,245,136 B2
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 61/302 Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
• 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 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

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.

Claims

1. A method, executed on one or more computers, comprising the steps of:

registering a domain name to a registrant,

storing a proxy email address associated with said domain name in a WHOIS database, receiving a domain name transfer request, and

ignoring said domain name transfer request without forwarding said domain name transfer request to said registrant of said domain name.

2. The method of claim 1, further comprising a steps of:

determining whether said domain name has a private registration service, and

ignoring said domain name transfer request only if said domain name has said private registration service.

3. The method of claim 1, further comprising a step of:

offering a domain name hijack protection service prior to receiving said domain name transfer request.

4. The method of claim 3, further comprising a step of:

applying said domain name hijack protection service to said domain name.

5. The method of claim 3, further comprising a step of:

providing an ability to turn said domain name hijack protection service on or off.

6. The method of claim 1, further comprising a step of:

applying a private registration to said domain name prior to receiving said domain name transfer request.

7. The method of claim 1, wherein each step is performed by a domain name registering entity.

8. The method of claim 1, wherein each step is performed by a proxy registration service provider.

9. The method of claim 1, wherein said ignoring comprises deleting said domain name transfer request.

10. The method of claim 1, further comprising a step of:

informing said registrant that said domain name transfer request was ignored.

11. A method, executed on one or more computers, comprising the steps of:

offering a domain name private registration service,

receiving a request from a customer for said domain name private registration service, applying said domain name private registration service to a domain name by storing a proxy email address associated with said domain name in a WHOIS database,

receiving a domain name transfer request for said domain name, and ignoring said domain name transfer request.

12. The method of claim 13, further comprising the step of:

notifying said customer that said domain name transfer request was ignored.