Domain name verification method, device and storage medium

Abstract

The application discloses a domain name verification method and device and a storage medium, relates to the technical field of digital information transmission, and discloses a domain name verification method, which comprises the following steps: determining the data processing result of a domain name according to domain name related information, wherein the domain name related information comprises at least one of domain name registration information, historical verification data and DNS resolution records, and the data processing result comprises a risk evaluation result and a policy evaluation result; determining the verification service node corresponding to the domain name and the domain name verification mode according to the data processing result, wherein the verification service node is used for executing the domain name verification mode; acquiring the single-node verification result returned by each verification service node executing the domain name verification mode, and determining the target verification result of the domain name according to the single-node verification result. The application improves the reliability of domain name verification.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of digital information transmission, and in particular to a domain name verification method, device and storage medium. BACKGROUND

[0002] In today's era of rapid digital development, the Internet has become an indispensable part of people's life and work, and the reliability and security of domain name verification are related to the stability and credibility of network communication.

[0003] The traditional domain name verification method has many drawbacks, mainly relying on fixed verification means, such as only checking the domain name registration information, which is extremely vulnerable to improper information management or network attacks. Once the relevant information is illegally tampered with or stolen, it may lead to low reliability of domain name verification. SUMMARY

[0004] The main purpose of the present application is to provide a domain name verification method, device and storage medium, which aims to solve the technical problem of low reliability of domain name verification.

[0005] To achieve the above purpose, the present application provides a domain name verification method, which comprises:

[0006] According to the domain name related information, the data processing result of the domain name is determined, the domain name related information includes at least one of domain name registration information, historical verification data and DNS resolution record, and the data processing result includes risk assessment result and policy assessment result;

[0007] According to the data processing result, the verification service node corresponding to the domain name and the domain name verification method are determined, and the verification service node is used to execute the domain name verification method;

[0008] Obtain the single-node verification result returned by each verification service node executing the domain name verification method, and determine the target verification result of the domain name according to the single-node verification result.

[0009] In an embodiment, the step of obtaining the single-node verification result returned by each verification service node executing the domain name verification method comprises:

[0010] According to the verification service node and the domain name verification method, a target verification path is determined, which is the path between the servers corresponding to the verification service node and the domain name verification method;

[0011] Obtain the single-node verification result based on the target verification path.

[0012] In an embodiment, the step of determining the target verification path according to the verification service node and the domain name verification mode comprises:

[0013] determining candidate verification paths according to the verification service node and the domain name verification mode;

[0014] obtaining real-time network states of each candidate verification path, the real-time network states comprising at least one of bandwidth, delay, and packet loss rate;

[0015] determining comprehensive scores of each candidate verification path according to the real-time network states;

[0016] determining the target verification path corresponding to the domain name in each candidate verification path according to the comprehensive scores.

[0017] In an embodiment, the verification service node is obtained by the following steps:

[0018] determining candidate service nodes according to the data processing result;

[0019] obtaining service indexes of each candidate service node, the service indexes comprising at least one of performance, reliability, and coverage range;

[0020] determining a verification service node in the candidate service nodes according to the service indexes, attribute information of the domain name, and user demand, the attribute information of the domain name comprising geographical distribution and / or business type.

[0021] In an embodiment, the domain name verification mode is obtained by the following steps:

[0022] determining a dynamic verification level according to user security demand and the data processing result;

[0023] determining a verification mode of the verification service node according to the dynamic verification level.

[0024] In an embodiment, the step of determining the verification mode of the verification service node according to the dynamic verification level comprises:

[0025] when the dynamic verification level is less than a preset level threshold, adopting a first risk level verification mode;

[0026] when the dynamic verification level is greater than or equal to the preset level threshold, adopting a second risk level verification mode, the first risk level being lower than the second risk level.

[0027] In an embodiment, the step of determining the data processing result of the domain name according to domain name related information comprises:

[0028] extracting a key feature of the domain name related information, the key feature including at least one of a domain name registration duration, DNS resolution stability, and historical verification success rate;

[0029] determining a weight parameter corresponding to the key feature, the weight parameter being generated according to an influence degree of the key feature on the domain name;

[0030] determining the data processing result of the domain name according to the key feature and the weight parameter.

[0031] In an embodiment, the method further comprises:

[0032] determining a validity period of the domain name according to the variation frequency of the domain name and the historical verification data;

[0033] determining a verification frequency of the domain name according to the validity period and the importance degree of the domain name;

[0034] performing the step of determining the data processing result of the domain name according to the domain name related information and related steps based on the verification frequency.

[0035] In addition, to achieve the above object, the present application further provides a domain name verification device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the domain name verification method as described above.

[0036] In addition, to achieve the above object, the present application further provides a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the domain name verification method as described above.

[0037] In addition, to achieve the above object, the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the domain name verification method as described above.

[0038] The one or more technical solutions provided by the present application have at least the following technical effects:

[0039] By analyzing domain name registration information, historical verification data, DNS resolution records and other multi-dimensional information, the risk status of the domain name and the verification strategy corresponding to the domain name can be more comprehensively evaluated, the best domain name verification service node and verification method can be dynamically selected according to the data processing result, the safety and reliability of the verification process are ensured, and the reliability of domain name verification is improved. BRIEF DESCRIPTION OF DRAWINGS

[0040] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.

[0041] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the accompanying drawings required to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, for those of ordinary skill in the art, the other drawings can also be obtained based on these drawings without any creative work.

[0042] Figure 1 A flowchart provided for the domain name verification method embodiment one of the present application;

[0043] Figure 2 A flowchart provided for the domain name verification method embodiment two of the present application;

[0044] Figure 3 A flowchart provided for the domain name verification method embodiment three of the present application;

[0045] Figure 4 A flowchart provided for the domain name verification method embodiment four of the present application;

[0046] Figure 5 A flowchart provided for the domain name verification method embodiment five of the present application;

[0047] Figure 6 A flowchart provided for the domain name verification method embodiment six of the present application;

[0048] Figure 7 A device structure schematic diagram of the hardware running environment involved in the domain name verification method in the embodiments of the present application.

[0049] The purpose implementation, functional features and advantages of the present application will be further explained with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application, and are not used to limit the present application.

[0051] In order to better understand the technical solutions of the present application, the following will be described in detail in combination with the drawings in the specification and the specific embodiments.

[0052] The main solution of the embodiment of the application is: determining a data processing result of a domain name according to domain name related information, the domain name related information including at least one of domain name registration information, historical verification data and DNS resolution records, the data processing result including a risk assessment result and a policy assessment result; determining a verification service node corresponding to the domain name and a domain name verification mode according to the data processing result, the verification service node being used to execute the domain name verification mode; obtaining a single-node verification result returned by each verification service node executing the domain name verification mode, and determining a target verification result of the domain name according to the single-node verification result.

[0053] In the embodiment, the following is described taking a domain name verification device as an execution subject for convenience of description.

[0054] Since the traditional domain name verification mode mainly relies on fixed verification means, such as only simple checking of domain name registration information, this mode is extremely susceptible to improper information storage or network attacks, and once the related information is illegally tampered with or stolen, the reliability of domain name verification may be low.

[0055] The application provides a solution, which can more comprehensively evaluate the risk status of a domain name and a verification policy corresponding to the domain name by analyzing multi-dimensional information such as domain name registration information, historical verification data and DNS resolution records, dynamically select the best domain name verification service node and verification mode according to a data processing result, ensure the security and reliability of the verification process, and effectively prevent misjudgment caused by single-point failure or network attacks through simultaneous verification of multiple nodes, thereby improving the reliability of domain name verification.

[0056] It should be noted that the execution subject of the embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a domain name verification device, etc. capable of realizing the above functions. The following takes a domain name verification device as an example to describe the embodiment and each of the following embodiments.

[0057] Based on this, the embodiment of the application provides a domain name verification method, which refers to Figure 1 , Figure 1 The flowchart of the first embodiment of the domain name verification method of the application is shown in FIG. 1.

[0058] In the embodiment, the domain name verification method includes steps S10-S30:

[0059] Step S10, determining a data processing result of a domain name according to domain name related information, the domain name related information including at least one of domain name registration information, historical verification data and DNS resolution records, the data processing result including a risk assessment result and a policy assessment result.

[0060] Optionally, the domain name related information includes domain name registration information, historical verification data, and DNS (Domain Name System) resolution records, and also includes domain name recordal information, domain name SSL (Secure Sockets Layer) certificate information, and domain name traffic information, and the domain name related information is not limited to the above information.

[0061] The domain name related information can be uniformly stored in a database and standardized.

[0062] In this embodiment, the domain name registration information is detailed information related to a registered domain name. Optionally, the domain name registration information includes information of the domain name itself, information of a registrant, information of a registration service agency, domain name server information, domain name status information, registration time, expiration time, and the like.

[0063] The historical verification data refers to various records generated in previous verification processes of the domain name, including time, manner, result, and related details of the verification. Optionally, the historical verification data includes records of previous verifications, records of abnormal situations, and records of changes in the status of the domain name, wherein the records of previous verifications contain time of each verification of the domain name, verification manner adopted, and result of whether the verification is passed. The records of abnormal situations are detailed records of reasons for failure of the domain name verification or abnormal situations, such as inaccurate verification information, DNS resolution abnormality, and mailbox hijacking. The records of changes in the status of the domain name are records of changes in the status of the domain name, for example, time of change in the status and reasons.

[0064] DNS resolution records are records generated by DNS servers in the process of resolving domain names to IP (Internet Protocol) addresses or other resource records, which store various configuration information of domain names. Optionally, the DNS resolution records include at least one or more of the following: A record (Address Record), which is used to map a domain name to an IPv4 (Internet Protocol version 4) address. AAAA record (IPv6 Address Record), which is used to map a domain name to an IPv6 (Internet Protocol version 6) address. MX record (Mail Exchange Record), which is used to specify a mail server that receives email. CNAME record (Canonical Name Record), which is used to alias one domain name to another domain name. NS record (Name Server Record), which is used to specify the authoritative DNS server of a domain name. TXT record (Text Record), which is used to store text information, commonly used to verify domain ownership or store SPF (Sender Policy Framework) records. PTR record (Pointer Record), which is used for reverse DNS query, i.e. mapping IP (Internet Protocol) address to domain name. SRV record (Service Record), which is used to specify the server address and port of a specific service.

[0065] Optionally, a machine learning algorithm is used to build a comprehensive evaluation model, such as decision tree, neural network, etc. The processed multi-source domain name related information is input into the comprehensive evaluation model, and the data processing result of the domain name is output through the processing of the comprehensive evaluation model.

[0066] Comprehensive consideration of domain name registration information, historical verification data and DNS resolution records can comprehensively evaluate the risk status of domain names, timely discover abnormalities and potential threats, such as whether the domain name is maliciously registered, whether there is DNS hijacking, etc., so as to effectively identify high-risk domain names and prevent users from suffering from network fraud, data leakage and other security threats.

[0067] Optionally, the data processing result comprises a risk assessment result and a strategy assessment result. Optionally, the risk assessment result comprises whether the domain name is at risk, a risk level, a risk value, whether the domain name is malicious, etc. Optionally, the strategy assessment result comprises a strategy selection of a verification service node and / or a domain name verification method, including how to select a verification service node, such as selecting a certain region, and how to select a domain name verification method executable by the verification service node, such as selecting either a domain name verification method A or a domain name verification method B supported by the verification service node.

[0068] In an optional embodiment, the validity period of the domain name is determined according to the frequency of change of the domain name and the historical verification data; the verification frequency of the domain name is determined according to the validity period and the importance of the domain name; and the step of determining the data processing result of the domain name according to the domain name related information and related steps are performed based on the verification frequency.

[0069] The frequency of change of the domain name can reflect the activity level of the domain name and possible abnormal situations. If the domain name frequently changes, such as frequently changing IP addresses, registration information, etc., it may mean that the domain name has unstable factors or potential malicious behavior. Combined with historical verification data, the historical state of the domain name can be traced back, including whether there has been a violation in the past, whether it has been tampered with, etc. These comprehensive factors make the process of determining the validity period of the domain name more comprehensive and scientific, and can more accurately determine whether the domain name is still valid, thereby avoiding mistakenly determining that a domain name that has expired or has potential risks is valid.

[0070] For domain names with high importance, a higher verification frequency can be set to timely discover possible problems, such as attacks or tampering of key enterprise domain names. For domain names with relatively low importance, the verification frequency can be reasonably reduced to reasonably allocate management resources. Optionally, the importance is determined by the type of the domain name. This automated management mechanism can effectively reduce manual intervention, reduce management costs, improve management efficiency, and ensure timely updating and accurate processing of domain name information.

[0071] Accurate determination of the validity period of the domain name and reasonable verification frequency can prevent the use of malicious domain names. For example, some malicious users may exploit the vulnerability of the validity period of the domain name to carry out attack behavior. By strictly controlling the validity period and verification frequency of the domain name, these malicious domain names can be discovered and processed in a timely manner, thereby protecting the safety of network users. At the same time, reasonable management of normal domain names can also enhance the stability of the network and reduce network failures and security vulnerabilities caused by domain name problems.

[0072] Step S20, determining the verification service node corresponding to the domain name and the domain name verification mode according to the data processing result, the verification service node being used for executing the domain name verification mode.

[0073] Optionally, when the data processing result comprises a risk assessment result, the risk assessment result comprises a risk level, and different risk levels correspond to different numbers of verification service nodes. For example, a low risk level corresponds to one verification service node, a medium risk level corresponds to two verification service nodes, and a high risk level corresponds to three domain name verification service nodes.

[0074] Optionally, when the data processing result comprises a strategy assessment result, a target region is determined according to the region where the server of the domain name is located, and a verification service node in the target region is selected. Optionally, when the data processing result comprises a strategy assessment result, the type of the verification service node is selected according to the type of the domain name.

[0075] In this embodiment, different domain name verification service nodes can adopt different domain name verification modes. For example, the domain name verification node A can adopt domain name verification modes a and b, and the domain name verification node B can adopt domain name verification modes a, b and c.

[0076] Optionally, the domain name verification mode can be selected by a user.

[0077] Optionally, according to the data processing result, the verification service node corresponding to the domain name and the domain name verification mode are determined, the domain name verification mode is output on a management interface, and the domain name verification mode selected by a user based on the management interface is taken as the final domain name verification mode.

[0078] Optionally, the domain name verification mode includes DNS verification, mailbox verification, file verification and the like. The DNS verification is to prove the control right of the domain name by using DNS record. The mailbox verification is to confirm the domain name ownership by sending a verification email to the mailbox associated with the domain name. When the domain name is registered or related operations are involved, a mail containing a verification link or a verification code is sent to the mailbox address filled in the domain name registration information. The domain name owner needs to log in to the mailbox, click the verification link or input the verification code to complete the verification process. This verification mode uses the association between the mailbox and the domain name, and considers that the user who can access the mailbox associated with the domain name is the legal owner of the domain name. The mailbox verification is often used for the confirmation of the domain name registration information by the domain name registrar, and the preliminary verification of the domain name owner identity in some network services. The file verification is to upload a specific verification file to the root directory of the website to realize the domain name verification. When the domain name needs to be verified, the domain name verification device provides a verification file containing a specific file name and file content, and the domain name owner needs to upload the file to the root directory of the website. This mode is often used in some scenarios with certain authority of website content management, such as some website management tools or services, which use the file verification mode to confirm the ownership of the domain name when associated with the domain name.

[0079] In step S30, a single-node verification result returned by each verification service node performing the domain name verification mode is acquired, and a target verification result of the domain name is determined according to the single-node verification result.

[0080] Optionally, the target verification result includes the control right of the domain name, and the target verification result can also be verification success or verification failure. The target verification result facilitates the domain name administrator and user to quickly understand the security state of the domain name and timely take corresponding measures, such as further investigation or access restriction on high-risk domain names, thereby improving the decision efficiency of domain name management. Only the domain name passing the verification can be trusted and accessed, the spread of malicious domain names is blocked, the risk of network attack is reduced, and the network asset security of users and enterprises is protected.

[0081] Optionally, the target verification result of the domain name is determined according to each single-node verification result and a weight parameter, and the weight parameter is a preset parameter.

[0082] Optionally, the node weight of the verification service node is determined according to the reliability of the verification service node performing the domain name verification mode in historical verification data, and the target verification result is determined according to the node weight and the single-node verification result. For example, the single-node verification result of the verification service node A is verification success, the single-node verification result of the verification service node B is verification failure, the node weight of the verification service node A is greater than the node weight of the verification service node B, and therefore the target verification result is verification success.

[0083] Optionally, after step S10, the method further comprises: storing the target verification result of the domain name as historical verification data; and storing the historical verification data to a blockchain. Optionally, in response to a query operation of a user on the blockchain, the historical verification data of the domain name is outputted.

[0084] It should be noted that the blockchain has the characteristic of being tamper-proof, and storing the historical verification data of the domain name to the blockchain can ensure that these data are difficult to be tampered maliciously once written. This provides a highly trusted data environment for the verification process of the domain name, because any illegal modification of the data will be discovered by the verification mechanism of the blockchain. For example, for some key and high-value domain names, after their historical verification data are stored on the blockchain, competitors or malicious attackers can be prevented from interfering with the validity judgment of the domain name by tampering with the historical data.

[0085] By allowing users to query the historical verification data of the domain name on the blockchain, the transparency of the data is achieved. Users can clearly understand all the verification situations of the domain name from registration to now, including the time of verification, the verification result and other information. This is very helpful for the transaction and management of the domain name. The above verification information uses a transparent mechanism, which can let the domain name owner know whether there is illegal verification record of the domain name.

[0086] The embodiment proposes an innovative verification mechanism, which changes from one-time verification in the past industry to decision verification after comprehensive analysis, wherein the comprehensive analysis combines multi-dimensional information such as registration information, historical data, real-time data, etc., which can make the domain name verification more reliable, safer, more efficient and more transparent.

[0087] In the technical solution of the embodiment, by analyzing multi-dimensional information such as domain name registration information, historical verification data and DNS resolution record, the risk status of the domain name and the verification strategy corresponding to the domain name can be more comprehensively evaluated, the best domain name verification service node and verification mode are dynamically selected according to the data processing result, the safety and reliability of the verification process are ensured, and the simultaneous verification of multiple nodes can effectively prevent misjudgment caused by single point failure or network attack, thereby improving the reliability of domain name verification.

[0088] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be described hereinafter. On this basis, please refer to Figure 2 , step S30 comprises:

[0089] Step S31, according to the verification service node and the domain name verification mode, determining a target verification path, the target verification path is a path between servers corresponding to the verification service node and the domain name verification mode;

[0090] At step S32, the single-node verification result is obtained based on the target verification path.

[0091] In this embodiment, the candidate verification paths are verification paths supporting the verification service nodes and the domain name verification manners. Optionally, the comprehensive scores of the candidate verification paths are determined according to at least one of the bandwidth, the delay, and the packet loss rate and the corresponding weights. The target verification path with a high comprehensive score is selected to obtain a verification path with good stability and high speed for domain name verification, thereby improving the efficiency and reliability of domain name verification.

[0092] Optionally, a network path evaluation model is established, which is used to calculate the comprehensive scores of the verification paths from different domain name verification service nodes to the DNS server to which the domain name belongs according to real-time network conditions. The target verification path with a high comprehensive score is selected to obtain a verification path with good stability and high speed for domain name verification, thereby improving the efficiency and reliability of domain name verification.

[0093] In an optional embodiment, step S31 includes: determining candidate verification paths according to the verification service nodes and the domain name verification manners; obtaining real-time network states of the candidate verification paths, the real-time network states including at least one of the bandwidth, the delay, and the packet loss rate; determining comprehensive scores of the candidate verification paths according to the real-time network states; and determining the target verification path corresponding to the domain name from the candidate verification paths according to the comprehensive scores.

[0094] The candidate verification paths are determined by considering the verification service nodes and the domain name verification manners, which can find multiple possible paths for domain name verification. In the numerous candidate paths, the target verification path is determined according to the real-time network states, which can avoid sending the verification request to a path with poor network conditions. For example, if the bandwidth of a path is low, the delay is high, or the packet loss rate is high, selecting such a path for domain name verification may result in a slow or even failed verification process. By this way, the path with good network conditions can be preferentially selected for verification, thereby improving the overall efficiency of domain name verification and reducing the time required for verification.

[0095] Real-time acquisition of network state information and determination of target verification path according to the same can reduce the risk of domain name verification failure caused by network failure or unstable factors. For example, when the network is congested or some nodes fail, it can automatically switch to other verification paths with better network conditions to ensure that the domain name verification process can proceed smoothly. This makes the domain name verification service more reliable and reduces domain name verification errors or failure caused by network problems. For paths with good network conditions, the load of verification requests can be appropriately increased; for paths with poor network conditions, the sending of verification requests can be reduced to avoid wasting network resources. For example, for paths with sufficient bandwidth and low delay, more domain name verification requests can be allocated to the path to fully utilize its good network conditions, thereby optimizing the configuration of network resources.

[0096] Optionally, the number of target verification paths is determined according to the data processing result. Optionally, when the risk level is less than a preset level threshold, a first number of target verification paths is used; when the risk level is greater than or equal to the preset level threshold, a second number of target verification paths is used, and the first number is less than the second number.

[0097] Optionally, when the number of target verification paths is greater than or equal to two, a path verification result is obtained based on each target verification path, and a single-node verification result is determined according to the path verification result.

[0098] Optionally, a risk level is determined according to the data processing result, a verification ratio is determined according to the risk level, when the consistency rate of the path verification result is greater than or equal to the verification ratio, the single-node verification result of the domain name is determined according to the path verification result with the largest proportion, and when the consistency rate of the path verification result is less than the verification ratio, it is determined that the verification fails. For example, target verification path 1 is verification success, target verification path 2 is verification success, target verification path 3 is verification failure, the consistency rate of the path verification result is 2 / 3, and the verification ratio is 1 / 2. The path verification result with the largest proportion is verification success, and the single-node verification result is verification success.

[0099] Optionally, when the risk value in the data processing result is greater than a preset first risk threshold, the verification ratio is a preset first ratio. When the risk value in the data processing result is less than the preset first risk threshold and greater than a preset second risk threshold, the verification ratio is a preset second ratio. When the risk value in the data processing result is less than the preset second ratio, the verification ratio is a preset third ratio, wherein the third ratio is less than the second ratio, and the second ratio is less than the first ratio. For example, when the risk value in the data processing result is >7.0, 100% of the path results are required to be consistent; when the risk value is <4.0, 70% of the path results are required to be consistent; and when the risk value is between 4.0 and 7.0, 85% of the path results are required to be consistent.

[0100] Based on the target verification path, the single-node verification result is obtained, which can avoid wasting verification resources on multiple irrelevant nodes or paths. The verification service node can directly send the verification request to the server corresponding to the adopted verification method, reducing unnecessary data transmission and processing steps. For example, for DNS-based domain name verification, the verification request is directly sent to the appropriate DNS server for verification, rather than being transmitted back and forth between multiple different types of servers, thereby shortening the verification time and improving the verification efficiency.

[0101] In the technical scheme of the embodiment, the target verification path is determined, i.e., the path from the verification service node to the server corresponding to the domain name verification method, so that the domain name verification process is more accurate. The verification process can be directly performed on the adopted verification method, reducing the interference of irrelevant factors and improving the pertinence of the verification, so that the validity of the domain name can be more accurately judged.

[0102] Based on any of the above embodiments of the present application, in the third embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be described in detail. On this basis, please refer to Figure 3 , step S20 comprises:

[0103] Step S21, determining a candidate service node according to the data processing result;

[0104] Step S22, obtaining a service index of each candidate service node, the service index comprising at least one of performance, reliability and coverage range;

[0105] Step S23, determining a verification service node in the candidate service node according to the service index, the attribute information of the domain name and the user demand, the attribute information of the domain name comprising geographical distribution and / or business type.

[0106] Optionally, according to the risk level in the data processing result, the candidate service node corresponding to the risk level is determined.

[0107] Optionally, according to the selection strategy in the data processing result, the candidate service node meeting the selection strategy is determined. Optionally, for a domain name facing global users, a verification service node with extensive global node coverage is preferentially selected; for a domain name of a specific industry, a verification service node with industry professional verification capability is selected to improve the efficiency and reliability of the verification.

[0108] In this embodiment, the performance index measures the speed and efficiency of the service node in processing requests and completing tasks. Optionally, the performance index includes latency or response time, throughput, processing time, resource utilization, etc. The reliability index measures the ability of the service node to continuously, stably and correctly provide the promised service. Optionally, the reliability index includes availability, failure rate, mean time between failures, mean time to repair, data consistency or correctness, fault tolerance, etc. The coverage index measures the service reachability and distribution breadth of the service node in terms of geographical area, network access point or target user group. Optionally, the coverage index includes geographical coverage, network coverage or access point, latency coverage, target user coverage, service range, etc.

[0109] The performance, reliability, coverage, etc. of the candidate service node are evaluated in real time. In combination with the attributes of the domain name, such as geographical distribution, business type, etc., and user demand, the most suitable verification service node is selected. Selecting the verification service node from the user demand can provide the user with more targeted and efficient domain name verification services, reduce user waiting time, reduce verification failure probability, and thus improve user satisfaction. According to the attribute information of the domain name such as geographical distribution and business type, the verification service node is accurately matched. For example, for domain names with a large number of users in a specific region or a specific business type, nodes close to the user group and familiar with the business can be allocated to reduce latency and improve response speed, making the service more suitable for the actual scenario.

[0110] In the technical solution of this embodiment, the verification service node is determined by comprehensively considering the service index, domain name attribute and user demand, which can select the node that best meets the requirements in terms of performance, reliability and coverage, thereby improving the verification quality and efficiency, ensuring the stability and reliability of the verification process, and meeting the individual needs of users.

[0111] Based on any of the above embodiments of the present application, in the fourth embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be described hereinafter. On this basis, please refer to Figure 4 , step S20 comprises:

[0112] Step S24, determining a dynamic verification level according to the security demand of the user and the data processing result;

[0113] Step S25, determining a verification mode of the verification service node according to the dynamic verification level.

[0114] Considering that different users have different security needs, a clear and demand-oriented verification service is provided for users. For ordinary users with low security demand, a relatively simple verification mode is adopted to reduce cumbersome operations in the verification process, improve verification efficiency, enable users to quickly complete domain name verification, and improve user experience.

[0115] According to the security requirements of the user and the data processing result, the verification level is dynamically adjusted, which can ensure that the domain name with high security requirements is verified more strictly. For example, for the domain name related to financial transactions, user sensitive information processing and other domain names with extremely high security requirements, and the risk level of the data processing result is greater than the preset level, a higher dynamic verification level is determined, which effectively prevents the domain name from being stolen and maliciously used, and other security threats.

[0116] According to the data processing result and the security requirements of the user, the verification level is dynamically adjusted. For the domain name with low risk level, the basic verification level is adopted to reduce the verification steps and resource consumption; for the domain name with high risk or related to important business, the verification level is improved, and the multi-dimensional dynamic domain name verification link such as extended identity verification is added to ensure the reliability and security of the verification.

[0117] In an optional embodiment, when the dynamic verification level is less than the preset level threshold, the verification method of the first risk level is adopted; when the dynamic verification level is greater than or equal to the preset level threshold, the verification method of the second risk level is adopted, and the first risk level is lower than the second risk level.

[0118] Optionally, the verification method of the first risk level includes DNS verification, mailbox verification, file verification, and the verification method of the second risk level includes enterprise information, physical address, legal qualification verification, application of OV SSL certificate (Organization Validation SSL Certificate, organization verification type SSL certificate) or EV SSL certificate (Extended Validation SSL Certificate, extended verification SSL certificate).

[0119] In an embodiment, according to the rules and algorithms of the multi-factor dynamic verification mechanism, the enterprise information is automatically verified, and after the enterprise information verification is passed, a verification token can also be automatically generated, which can be integrated into the automatic deployment service for use, and integrated into the application process of the certificate through the token mechanism.

[0120] Optionally, if the enterprise domain name wants to apply for OV SSL certificate, after sending a request to the system and obtaining the target verification result as verification success, the domain name control right verification is completed, and the entity legality of enterprise information, physical address, legal qualification and the like is also automatically verified. After passing the verification, a verification token can be automatically generated, and the OV SSL certificate can be applied through the token. This token generation mechanism is also part of the multi-dimensional verification method, which is applied to the automatic process of the domain name certificate to promote the automation of the certificate issuance.

[0121] Optionally, if the enterprise domain name applies for an EV SSL certificate, after sending a request to the system and obtaining a target verification result of verification success, i.e., after completing the domain name control verification, the system automatically verifies the entity legality of enterprise information, physical address, legal qualification, etc. After verification, a verification token can be automatically generated, and the EV SSL certificate can be applied through the token. The above verification method is part of the multi-dimensional verification method and is applied to the automatic process of the domain name certificate to promote the automation of certificate issuance.

[0122] The above-mentioned extension verification generates a verification token after completion. This mechanism is integrated into the automatic process and brings business innovation to the automatic verification scheme.

[0123] Optionally, when the dynamic verification level is less than the preset level threshold, a first number of verification methods are used; when the dynamic verification level is greater than or equal to the preset level threshold, a second number of verification methods are used, and the first number is less than the second number.

[0124] In the technical scheme of the embodiment, by determining the dynamic verification level, the resources of the verification service nodes can be reasonably allocated. Verification requests with high security levels are allocated to verification service nodes with higher security protection capabilities and resources, and complex verification methods are used; and for requests with low security levels, the corresponding normal nodes are allocated, so as to avoid excessive occupation of resources and improve the resource utilization efficiency of the entire system.

[0125] Based on any of the above embodiments of the present application, in the fifth embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be described in detail. On this basis, please refer to Figure 5 , step S10 includes:

[0126] Step S11, extracting key features of the domain name related information, the key features including at least one of domain name registration duration, DNS resolution stability, and historical verification success rate;

[0127] Step S12, determining a weight parameter corresponding to the key features, the weight parameter being generated by an influence degree of the key features on the domain name;

[0128] Step S13, determining the data processing result of the domain name according to the key features and the weight parameter.

[0129] The registration duration of a domain name is associated with the risk. When the registration duration of a domain name is within a suitable duration range, the risk is relatively small. When the registration duration of a domain name is outside the suitable duration range, the risk is relatively large. For example, newly registered domain names lack historical records and trustworthiness, and may be used for short-term malicious activities. These domain names may be frequently used for attacks in a short period of time and then quickly discarded. If a long-term registered domain name is not properly managed, it may be forgotten or ignored, resulting in outdated security configurations or failure to update in a timely manner, which may increase the risk of attack.

[0130] DNS resolution stability refers to the reliability and consistency of the DNS resolution process of a domain name within a period of time, reflecting the stability and availability of DNS servers in handling domain name resolution requests. Optionally, DNS resolution stability includes resolution success rate, resolution delay, resolution consistency, etc. If the DNS resolution success rate of a domain name is low, the resolution delay is high, or the resolution results are inconsistent, it may indicate that the domain name has technical problems or a high risk of attack.

[0131] Historical verification success rate refers to the proportion of the number of successful verifications to the total number of verifications in the past, reflecting the historical performance and reliability of domain name verification. Optionally, historical verification success rate includes verification pass rate, verification failure reason, and verification frequency, etc. Low verification pass rate or frequent verification failures may indicate that the domain name is poorly managed or has potential security risks.

[0132] Optionally, according to the influence degree of different key features on the authenticity and security of the domain name, the weight parameters corresponding to the key features are set by using the analytic hierarchy process method, etc. The data processing result of the domain name is determined according to the weighted sum of the key features and the weight parameters.

[0133] By extracting key features to evaluate domain names, especially key factors such as domain name registration duration, DNS resolution stability, and historical verification success rate, the security of domain names can be more accurately judged. For example, domain names with longer registration duration may be more reliable, as malicious domain name owners may be less willing to register domain names for a long time to engage in illegal activities. Frequent DNS resolution instability may indicate that the domain name is at risk of being tampered with or used for attacks, such as domain name hijacking. Low historical verification success rate may indicate that the domain name has verification problems in its past use, and may be misused or improperly configured. By combining these key features, normal domain names and malicious domain names can be effectively distinguished, and the reliability of domain name security evaluation can be improved.

[0134] The weight parameter corresponding to the key feature is determined, so that the influence degree of each key feature on the domain name can be quantified. In this way, the domain name can be processed according to different business requirements and security policies. In the network security protection in the financial field, the weight of the domain name registration time can be set to be relatively high, because the financial transaction involves a large amount of fund safety, and the domain name with long registration time and stable operation can be more trustworthy. In the content distribution network business, the weight of DNS resolution stability can be more important to ensure that users can quickly and stably access the content. In this way, the domain name data processing result that meets the needs of different application scenarios can be provided.

[0135] After determining the data processing result of the domain name, domain names with different risk levels can be classified and managed. Domain names with low risk levels can be preferentially allocated to key businesses or high-value network applications; domain names that may have risks can be limited in use or further verified, and the overall domain name resource allocation strategy can be optimized.

[0136] In the embodiment, an intelligent comprehensive analysis and decision engine is integrated, including intelligent selection of network routing for domain names that need to be verified, considering the system state of the verification service node itself, such as task amount, network state, system processing capacity, etc., and adopting comprehensive analysis and decision of verification frequency and other progress, which greatly improves the verification efficiency and security.

[0137] In the technical solution of the embodiment, the security or risk level of the domain name can be more accurately judged by extracting key features to evaluate the domain name. The data processing result of the domain name is determined according to the key features and the weight parameter, and the comprehensiveness of domain name management is improved.

[0138] Based on any of the above embodiments of the present application, in the sixth embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be repeated hereinafter. On this basis, please refer to Figure 6The first step is responsible for collecting relevant data from multiple channels such as authoritative domain name registration agencies, SSL certificate issuing agencies, DNS resolution servers, and user behavior monitoring systems. The second step is to clean, analyze and process the collected data, extract key features, and conduct user behavior analysis and anomaly detection combined with machine learning algorithms. The third step is to evaluate the verification status of the domain name according to the rules and algorithms of the multi-factor dynamic verification mechanism, and make corresponding verification decisions, including the effective time of verification data, selecting multi-dimensional verification systems through global multiple independent best network nodes to check domain name resolution results simultaneously, and finally determining the verification result according to the verification strategy. The fourth step can automatically verify and obtain the information of the enterprise, and the verification result can be integrated into the automatic management platform through the token token, responsible for the verification and issuance of OV SSL or EV SSL certificates. Finally, the verification result will be stored in the blockchain, and the domain name verification status will be displayed through the visualization interface, and feedback and warning information will be sent to the domain name owner and security agencies.

[0139] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the domain name verification method of the present application. Based on this technical concept, more forms of simple changes are within the protection scope of the present application.

[0140] The present application provides a domain name verification device, which comprises at least one processor and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the domain name verification method in the above-mentioned embodiment one.

[0141] Reference will now be made to Figure 7 , which shows a structural schematic diagram of a domain name verification device suitable for implementing the embodiments of the present application. The domain name verification device in the embodiments of the present application can include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (PDA, Personal Digital Assistant), tablet computers (PAD, Portable Application Description), portable multimedia players (PMP, Portable Media Player), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and the like, as well as fixed terminals such as digital TVs, desktop computers, and the like. Figure 7 The domain name verification device shown is only an example and should not impose any limitations on the functions and use range of the embodiments of the present application.

[0142] As Figure 7As shown, the domain name verification device can include a processing apparatus 1001 (e.g., a central processor, a graphics processor, etc.) that can perform various appropriate actions and processes according to programs stored in a read only memory (ROM) 1002 or loaded from a storage apparatus 1003 into a random access memory (RAM) 1004. Various programs and data required for operation of the domain name verification device are also stored in the RAM 1004. The processing apparatus 1001, the ROM 1002, and the RAM 1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: input apparatuses 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output apparatuses 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; the storage apparatus 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication apparatus 1009. The communication apparatus 1009 can allow the domain name verification device to communicate with other devices wirelessly or by wire to exchange data. Although the domain name verification device with various systems is shown in the figure, it should be understood that all the shown systems are not required to be implemented or possessed. More or fewer systems can be alternatively implemented or possessed.

[0143] In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication apparatus, or installed from the storage apparatus 1003, or installed from the ROM 1002. When the computer program is executed by the processing apparatus 1001, the above-mentioned functions defined in the methods of embodiments of the present disclosure are performed.

[0144] The domain name verification device provided by the present disclosure adopts the domain name verification method in the above-mentioned embodiments, and can solve the technical problem of low reliability of domain name verification. Compared with the prior art, the domain name verification device provided by the present disclosure has the same beneficial effects as the domain name verification method provided by the above-mentioned embodiments, and other technical features in the domain name verification device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0145] It should be understood that various parts of the present application can be realized with hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0146] The above description is merely that of a specific implementation of the present application, and the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, and all such changes and replacements should be encompassed within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0147] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e., computer programs) for performing the domain name verification method in the above embodiments.

[0148] The computer readable storage medium provided by the present application may, for example, be a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, system, or device, or any combination thereof. More specific examples of the computer readable storage medium can include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), an optical fiber, a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present embodiment, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, a radio frequency (RF), and the like, or any suitable combination thereof.

[0149] The above computer readable storage medium can be contained in the domain name verification device; or can exist separately without being assembled into the domain name verification device.

[0150] The computer readable storage medium described above carries one or more programs, when the one or more programs are executed by the domain name verification device, the domain name verification device: by analyzing multi-dimensional information such as domain name registration information, historical verification data and DNS resolution records, the risk status of the domain name and the verification strategy corresponding to the domain name can be more comprehensively evaluated, the best domain name verification service node and verification mode are dynamically selected according to the data processing result, the safety and reliability of the verification process are ensured, the simultaneous verification of multiple nodes can effectively prevent misjudgment caused by single point failure or network attack, and the reliability of domain name verification is improved.

[0151] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0152] The flow diagrams and the block diagrams in the drawings are illustrations of possible architectures, functions, and operations for systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

[0153] The modules described in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the names of the modules do not constitute a limitation on the modules themselves.

[0154] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e., a computer program) for executing the domain name verification method described above, and can solve the technical problem of low reliability of domain name verification. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the domain name verification method provided by the above embodiments, and will not be described here.

[0155] The present application also provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the domain name verification method as described above.

[0156] The computer program product provided by the present application can solve the technical problem of low reliability of domain name verification. Compared with the prior art, the computer program product provided by the present application has the same beneficial effects as the domain name verification method provided by the above embodiments, and will not be described here.

[0157] The above only describes some embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structural transformation made by using the content of the present application specification and drawings, or direct / indirect application in other related technical fields is included in the patent protection scope of the present application.

Claims

1. A domain name verification method, characterized in that: The domain name verification method includes: Determine a data processing result of the domain name based on the domain name related information, the domain name related information including domain name registration information, historical verification data and DNS resolution records, and the data processing result including a risk assessment result and a policy assessment result; Determine, based on the data processing result, a verification service node corresponding to the domain name and a domain name verification method, wherein the verification service node is used to execute the domain name verification method; Obtaining a single-node verification result returned by each verification service node when executing the domain name verification method, and determining a target verification result of the domain name based on the single-node verification result; The verification service node is obtained through the following steps: Determine a candidate service node according to the data processing result; Obtaining a service indicator of each candidate service node, where the service indicator includes at least one of performance, reliability, and coverage; A verification service node is determined from the candidate service nodes according to the service indicator, attribute information of the domain name and user requirements, wherein the attribute information of the domain name includes geographical distribution and / or business type.

2. The domain name verification method according to claim 1, wherein: The step of obtaining the single-node verification result returned by each verification service node executing the domain name verification method includes: Determine a target verification path according to the verification service node and the domain name verification method, where the target verification path is a path between the verification service node and a server corresponding to the domain name verification method; The single-node verification result is obtained based on the target verification path.

3. The domain name verification method according to claim 2, wherein: The step of determining a target verification path according to the verification service node and the domain name verification method includes: Determining a candidate verification path according to the verification service node and the domain name verification method; Obtaining a real-time network status of each candidate verification path, wherein the real-time network status includes at least one of bandwidth, delay, and packet loss rate; Determining a comprehensive score of each candidate verification path based on the real-time network status; Among the candidate verification paths, the target verification path corresponding to the domain name is determined according to the comprehensive score.

4. The domain name verification method according to claim 1, wherein: The domain name verification method is obtained through the following steps: Determining a dynamic verification level based on the user's security requirements and the data processing results; The authentication mode of the authentication service node is determined according to the dynamic authentication level.

5. The domain name verification method according to claim 4, wherein: The step of determining the verification mode of the verification service node according to the dynamic verification level includes: When the dynamic verification level is lower than the preset level threshold, the verification method of the first risk level is adopted; When the dynamic verification level is greater than or equal to the preset level threshold, a second risk level verification method is adopted, and the first risk level is lower than the second risk level.

6. The domain name verification method according to claim 1, wherein: The step of determining the data processing result of the domain name according to the domain name related information includes: Extracting key features of the domain name related information, the key features including at least one of domain name registration duration, DNS resolution stability, and historical verification success rate; Determining a weight parameter corresponding to the key feature, where the weight parameter is generated based on the degree of influence of the key feature on the domain name; The data processing result of the domain name is determined according to the key feature and the weight parameter.

7. The domain name verification method according to claim 1, wherein: The method further comprises: Determining the validity period of the domain name based on the frequency of changes in the domain name and the historical verification data; Determining the verification frequency of the domain name based on the validity period and importance of the domain name; Based on the verification frequency, the step of determining the data processing result of the domain name according to the domain name related information and related steps are performed.

8. A domain name verification device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the domain name verification method according to any one of claims 1 to 7.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the domain name verification method according to any one of claims 1 to 7 are implemented.

Images