IP Library Granted Patent US 9,779,125
Granted Patent B2
US 9,779,125 · App. 14/541,659 · Granted Oct 3, 2017

Ensuring accurate domain name contact information

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 9,779,125
App. No.
14/541,659
Granted
Oct 3, 2017
Kind
B2
Abstract

Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: identify a first contact data and a second contact data associated with at least one domain name stored in a database communicatively coupled to the network; a user interface may be displayed, allowing a user to select the first contact data or a second contact data, and the server may then: receive a selection of the first contact data to be associated with the at least one domain name; disassociate the second contact data from the at least one domain name; and update a plurality of domain names, comprising the first domain name, to be associated with the first contact data.

Claims (71)

1. A method, comprising the steps of:

executing, by a server hardware computing device coupled to a network and comprising at least one processor executing specific computer-executable instructions within a memory, a first database command selecting, from a database coupled to the network:

a first contact data within a first contact data record and a second contact data within a second contact data record each associated in the database with a user account identifier; and

at least one domain name within at least one domain name data record, associated in the database with the user account identifier;

identifying, by the server hardware computing device:

a character string common to the first contact data and the second contact data; and

at least one difference between the first contact data and the second contact data;

transmitting, by the server hardware computing device, to a client hardware computing device coupled to the network, a graphical user interface (GUI) displaying the first contact, the second contact, and the at least one domain name;

decoding, by the server hardware computing device:

a first user input, from at least one GUI selection control displayed on the client hardware computing device, indicating a selection of the first contact data in association with the at least one domain name; and

a second user input, from a GUI deselection control displayed on the client hardware computing device, indicating a deselection of the second contact data; and

executing, by the server hardware computing device, a second database command updating the database to:

associate the at least one domain name with the first contact data; and

disassociate the second contact data from the at least one domain name.

2. The method of claim 1 , wherein the first contact data comprises a unique data record mapped to the at least one domain name.

3. The method of claim 1 , wherein the second contact data comprises:

a new user contact data record generated by a user; or

a data record generated during a domain name registration or transfer and comprising a user contact data.

4. The method of claim 1 , further comprising the steps of:

rendering, by the server hardware computing device, the GUI comprising:

a list of a plurality of contact data comprising the first contact data and the second contact data; and

a list of a plurality of domain names including the at least one domain name;

receiving, by the server hardware computing device, a selection via the GUI, comprising:

the first contact data; and

the at least one domain name.

5. The method of claim 1 , wherein the first contact data comprises a social media contact data.

6. The method of claim 1 , further comprising the step of generating, by the server hardware computing device, the GUI comprising the at least one difference and configured to receive the selection of the first contact data.

7. The method of claim 1 , further comprising the steps of:

identifying, by the server hardware computing device, the user account identifier associated with the first contact data; and

associating, by the server hardware computing device, the at least one domain name with the user account identifier.

8. A system, comprising:

a database communicatively coupled to a network and storing, in association with a user account identifier:

a first contact data within a first contact data record and a second contact data within a second contact data record;

at least one domain name within at least one domain data record;

a server hardware computing device coupled to a network and comprising at least one processor executing specific computer-executable instructions within a memory, that, when executed, cause the system to:

identify:

a character string common to the first contact data and the second contact data; and

at least one difference between the first contact data and the second contact data;

transmit, to a client hardware computing device coupled to the network, a graphical user interface (GUI) displaying the first contact, the second contact, and the at least one domain name;

decode:

a first user input from at least one GUI selection control displayed on the client hardware computing device indicating a selection of the first contact data in association with the at least one domain name; and

a second user input from a GUI deselection control displayed on the client hardware computing device indicating a deselection of the second contact data; and

execute a second database command updating the database to:

associate the at least one domain name with the first contact data; and

disassociate the second contact data from the at least one domain name.

9. A method, comprising the steps of:

executing, by a server hardware computing device coupled to a network and comprising at least one processor executing specific computer-executable instructions within a memory, at least one database command storing in association, within a database communicatively coupled to the network:

a user account identifier;

a stored contact data stored in the database;

a monitored contact data available through the network; and

at least one domain name within at least one domain name data record;

responsive to the sever hardware computing device decoding an update to the monitored contact data, transmit, to a client hardware computing device coupled to the network, a graphical user interface (GUI) displaying the stored contact data and the monitored contact data;

decoding, by the server network computing device:

a first user input from a GUI selection control displayed on the client hardware computing device indicating a selection of the monitored contact data to be associated with the at least one domain name; and

a second user input from a GUI deselection control displayed on the client hardware computing device indicating a deselection of the stored contact data; and

executing, by the server hardware computing device, a second database command updating the database to:

associate the at least one domain name with the monitored contact data; and

disassociate the stored contact data from the at least one domain name.

10. The method of claim 9 , wherein the monitored contact data comprises:

a social media contact data associated with a social media account; or

a postal contact monitored by a postal service.

11. The method of claim 10 , wherein the postal contact comprises:

an application programming interface comprising a user address; or

a postcard or letter sent to the user address.

12. The method of claim 11 , wherein the postcard or letter comprises a personal identification number to be entered into the GUI to verify the stored contact.

13. The method of claim 12 , wherein, responsive to the update, the postcard or letter is sent to the user address.

14. The method of claim 13 further comprising the steps of:

sending the postcard or the letter to the user address at regular intervals;

responsive to the personal identification number being entered into the GUI, changing a status for the stored address to a verified status; and

responsive to the personal identification number not being entered into the GUI after a designated time period, changing the status for the stored address to a verification pending status.

15. The method of claim 14 further comprising the step of inserting the verification status into a domain name related record.

Assignments (3)
SECURITY AGREEMENT Recorded Feb 17, 2023
From: GO DADDY OPERATING COMPANY, LLC; GD FINANCE CO, LLC; GODADDY MEDIA TEMPLE INC.; GODADDY.COM, LLC; LANTIRN INCORPORATED; POYNT, LLC
To: ROYAL BANK OF CANADA
Reel/Frame 062782/0489 →
SECURITY AGREEMENT Recorded May 9, 2017
From: GO DADDY OPERATING COMPANY, LLC
To: BARCLAYS BANK PLC, AS COLLATERAL AGENT
Reel/Frame 042426/0045 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 24, 2014
From: GUPTA, NITIN
To: GO DADDY OPERATING COMPANY, LLC
Reel/Frame 034433/0635 →