Domain Name Contact Verification via Code Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for registering domain names face issues such as ambiguity in contact information, particularly with geographic-based domain names, due to a one-to-one relationship between registrant registration data and contact data, which can lead to domain hijacking and loss of control, and the use of privacy services that create ambiguity in physical addresses.

Innovation Solution

A system that verifies and updates unique contact data for each user, allowing selection and propagation across all domain registrations, includes generating a code to verify a correspondence address, and updating records with verification status and date, ensuring accurate and consistent contact information across all domain name records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a one-to-one relationship is maintained between registrant registration data and contact data, then the system structure is simple, but contact information accuracy and reliability deteriorate due to ambiguity

Engineering Contradiction:
Improvesystem structureVSAvoidcontact information accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the contact data management by introducing a verification code mechanism that separates the registrant data from the contact data validation process. Each contact data entry is independently verified through a code sent to the correspondence address, allowing the system to maintain simple structure while ensuring accuracy through discrete verification steps.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary verification by sending a code to the correspondence address before finalizing the contact data association. This preliminary action ensures that the contact information is accurate and belongs to the registrant before it is stored and used, preventing future ambiguity issues.

Inventive Principle:
Principle #10Preliminary action

2Object-affected harmful factors

If privacy services are used to protect registrant information, then registrant privacy is improved, but contact information reliability deteriorates due to address ambiguity

Engineering Contradiction:
Improveregistrant privacy protectionVSAvoidphysical address accuracy
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The patent introduces a verification code as an intermediary mechanism between the privacy-protected registrant data and the contact information validation. The code is sent to the correspondence address and must be entered by the registrant to confirm ownership, allowing privacy services to be used while still ensuring the contact information is accurate and authorized.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If contact data is not verified through code validation, then the process speed is fast, but domain security deteriorates due to potential hijacking

Engineering Contradiction:
Improveregistration process speedVSAvoiddomain security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system uses self-service verification where the registrant themselves confirms the contact data by entering the verification code received at the correspondence address. This self-service approach maintains security through direct registrant confirmation while minimizing the need for complex manual verification processes, balancing speed and security.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9785663B2Verifying a correspondence address for a registrant
Publication Date: 2017.10.10 GO DADDY OPERATING CO LLC
  • US9785663B2 patent drawing
  • US9785663B2 patent drawing
  • US9785663B2 patent drawing

AI summary

Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: generate a code to verify a correspondence address; store the code in association with a domain name; retrieve a correspondence address within a domain name record for the domain name; generate a correspondence to be sent to the correspondence address including the code and a URL for accessing a user interface for entering the code; determine whether the code has been entered into the user interface; and if so, update the domain name record to include a status reflecting a verification of the correspondence address and a date of the verification.