Hosted Service Domain Verification System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Third-party service providers face challenges in detecting and preventing domain hijacking and misuse of hosted services, as well as managing accounts and services for subscribers, while ensuring reliable and scalable service delivery.
Innovation Solution
The system implements a client-server network infrastructure that provides a limited set of hosted services initially, allowing applicants to test basic services while preventing spam and abuse, and verifies user authority through domain name updates and screening processes to ensure legitimate use, ultimately upgrading to complete services upon proper authorization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party service providers offer hosted services to subscribers, then service availability and convenience for subscribers is improved, but the risk of domain hijacking and service misuse increases
Solution Approach 1:
The system performs preliminary verification of subscriber authority over domain names before allowing service registration. The verification module checks whether the subscriber has legitimate rights to the domain name, and only allows service registration if verification passes. This preliminary action prevents domain hijacking before it can occur.
Solution Approach 2:
The system introduces an intermediary verification module between the service registration process and the actual service provisioning. This intermediary component authenticates the subscriber's authority over the domain name, acting as a mediator that prevents unauthorized users from registering services under fake or stolen domain names.
2Ease of operation
If the system provides complete hosted services immediately, then subscriber convenience is improved, but security and control over service usage deteriorates
Solution Approach 1:
The system performs preliminary verification of subscriber authority before allowing service registration. The verification module checks whether the subscriber has legitimate rights to the domain name, and only allows service registration if verification passes. This preliminary action prevents domain hijacking before it can occur.
Solution Approach 2:
The system introduces an intermediary verification module between the service registration process and the actual service provisioning. This intermediary component authenticates the subscriber's authority over the domain name, acting as a mediator that prevents unauthorized users from registering services under fake or stolen domain names.
3Reliability
If the system implements strict verification processes, then prevention of misuse is improved, but the complexity of service registration deteriorates
Solution Approach 1:
The verification module automatically checks subscriber authority over domain names using existing domain name registration databases and verification mechanisms. The process is automated and requires minimal manual intervention from subscribers, who simply need to provide their domain name and subscriber information. The system self-verifies authority without requiring complex manual procedures.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In a client-server environment providing hosted services, an application service server receives from a client a first request for hosted services associated with a user-specified domain name. If the server does not provide hosted services for that domain name, the server designates the first request as pending and provides a limited set of the hosted services in association with the first request. The server provides a complete set of the hosted services requested in the first request if it can be established that a first user associated with the first request has appropriate authority to make administrative changes for the network domain designated by the domain-name. In some embodiments, the server denies the first request and cancels the limited services if it is not shown within a predetermined period of time that the first user has the appropriate authority.