Domain name management method, device and readable storage medium

By intercepting network request events in the browser plug-in, extracting key information and generating multi-parameter groups, the problem of complexity of traditional domain name resolution and forwarding methods is solved, and the simple domain name management in the browser is realized, reducing operation difficulty and technical requirements .

CN118646736BActive Publication Date: 2024-11-15SHENZHEN SMARTCITY TECH DEV GRP CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411118342.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-15
Publication Date
2024-11-15
Estimated Expiration
2044-08-15

AI Technical Summary

Technical Problem

Traditional domain name resolution and forwarding methods require configuration and processing at the network level or server level, and have the disadvantages of complex operations and are difficult to apply to ordinary users.

Method used

When monitoring network request events, intercept network request events, obtain event parameters, extract key information, generate multiple parameter groups, and determine the domain name configuration operations and parameters to be configured based on the preset domain name configuration file, and the network request events are requested according to the preset domain name configuration file. Modify and use browser plug-ins to manage domain names, avoiding complex operations of traditional methods.

Benefits of technology

Domain name management is realized through browser plug-ins. Users only need to install plug-ins and configurations in the browser, simplifying domain name resolution and forwarding operations, reducing technical thresholds, and improving operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118646736B_ABST
    Figure CN118646736B_ABST
Patent Text Reader

Abstract

The present application discloses a domain name management method, device and readable storage medium, belonging to the field of network communication technology. The present application is applied to a domain name management plug-in, which intercepts the network request event when a network request event is monitored, and obtains the event parameters of the network request event; extracts key information in the event parameters, and generates several groups of multi-parameter groups by combining the key information; determines the domain name configuration operations and parameters to be configured associated with each multi-parameter group according to the multi-parameter group and the preset domain name configuration file; modifies the network request event according to the domain name configuration operation and the parameters to be configured, and sends the modified network request event back to the browser. The browser plug-in is used for domain name management, and the user only needs to install the plug-in and configure the domain name in the browser, avoiding the complex operations of domain name resolution and forwarding at the network level required by the traditional domain name resolution and forwarding method.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of network communication technology, and in particular to a domain name management method, device and readable storage medium. Background Art

[0002] Domain name resolution and forwarding are two closely related operations in network communication. Domain name resolution refers to converting a domain name into a corresponding IP address so that the client can access the target server. Domain name forwarding refers to forwarding an access request from a domain name to another domain name or IP address.

[0003] In actual applications, domain name resolution and forwarding operations are usually used together to achieve more efficient and stable network communication. For example, internal domain name resolution is achieved by configuring DNS (Domain Name Server). At the same time, external access requests are forwarded by setting proxy servers or firewall rules.

[0004] That is, in order to achieve domain name resolution and forwarding, it is necessary to modify the configuration of network devices (such as routers, switches, etc.) or servers (such as DNS servers, proxy servers, etc.). These operations involve complex network technology and professional knowledge, which are difficult for ordinary users to apply.

[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0006] The main purpose of this application is to provide a domain name management method, device and readable storage medium, aiming to solve the technical problem that traditional domain name resolution and forwarding methods need to be configured and processed at the network level or server level, and have the disadvantage of complex operation.

[0007] To achieve the above object, the present application provides a domain name management method, which is applied to a domain name management plug-in and includes the following steps:

[0008] When a network request event is detected, the network request event is intercepted, and the domain name to be accessed of the network request event is obtained;

[0009] Determine an alternative domain name configuration operation associated with the domain name to be accessed, and an execution condition associated with the alternative domain name configuration operation;

[0010] Determining key information to be acquired according to the candidate domain name configuration operation and the execution condition;

[0011] Acquire the key information of the network request event, and determine the domain name configuration operation and parameters to be configured associated with the key information according to the key information and a preset domain name configuration file;

[0012] According to the domain name configuration operation and the parameters to be configured, the network request event is modified, and the modified network request event is sent back to the browser.

[0013] Optionally, before the step of intercepting the network request event and obtaining the event parameters of the network request event when the network request event is monitored, the method further includes:

[0014] When receiving a preset trigger operation, outputting a domain name management interaction interface, and receiving a domain name configuration action according to the domain name management interaction interface;

[0015] Acquire the configuration content associated with the domain name configuration action, and determine the domain name configuration operation corresponding to the configuration content, as well as the execution conditions and parameters to be configured associated with the domain name configuration operation;

[0016] According to the domain name configuration operation, the execution condition and the parameters to be configured, the preset domain name configuration file is updated and saved.

[0017] Optionally, the key information includes mandatory key information and optional key information, and the step of determining the key information to be acquired according to the candidate domain name configuration operation and the execution condition includes:

[0018] Determining, according to the candidate domain name configuration operation, a multi-parameter group to be generated and required key information constituting each of the multi-parameter groups; and

[0019] Determining, according to the execution condition, optional key information constituting each of the multi-parameter groups;

[0020] The step of obtaining the key information of the network request event and determining the domain name configuration operation and parameters to be configured associated with the key information according to the key information and a preset domain name configuration file includes:

[0021] Acquire the mandatory key information and the optional key information of the network request event, and generate the multi-element parameter group according to the mandatory key information and the optional key information;

[0022] According to the multi-parameter group and the preset domain name configuration file, the domain name configuration operation and the parameters to be configured associated with each multi-parameter group are determined.

[0023] Optionally, after the step of obtaining the mandatory key information and the optional key information of the network request event, the step further includes:

[0024] Determining extraction paths of the mandatory key information and the optional key information;

[0025] Determine the event parameters to be obtained of the network request event according to the extraction path;

[0026] The event parameters of the network request event are obtained, and the required key information and the optional key information in the event parameters are extracted.

[0027] Optionally, the event parameter further includes a request method, and before the step of sending the modified network request event back to the browser, the step further includes:

[0028] Calling a preset data security engine to determine the data security measures corresponding to the request method;

[0029] Acquire a request environment of the network request event, and determine a safety factor of the network request event according to the request environment;

[0030] A data security policy for the network request event is generated according to the data security measure and the security factor, and the data security policy is sent back to the browser.

[0031] Optionally, before the step of generating the data security policy of the network request event according to the data security measure and the security factor, the step further includes:

[0032] Acquire a data type and a network environment of the network request event, and determine a security parameter of the network request event according to the data type and the network environment;

[0033] The step of generating a data security policy for the network request event according to the data security measure and the security factor includes:

[0034] Constructing a data safety matrix according to the safety factor and the safety parameter;

[0035] A data security policy is generated according to the data security matrix and the data security measures.

[0036] Optionally, the step of modifying the network request event according to the domain name configuration operation and the parameters to be configured includes:

[0037] Determining a request modification interval of the network request event according to the domain name configuration operation;

[0038] The request modification interval is modified according to the parameters to be configured, and the modified network request event is sent back to the browser.

[0039] In addition, to achieve the above-mentioned purpose, the present application also provides a domain name management device, which includes: a memory, a processor, and a domain name management program stored in the memory and executable on the processor, wherein the domain name management program is configured to implement the steps of the above-mentioned domain name management method.

[0040] In addition, to achieve the above-mentioned purpose, the present application also provides a readable storage medium, on which a domain name management program is stored, and when the domain name management program is executed by a processor, the steps of the above-mentioned domain name management method are implemented.

[0041] In this application, in order to solve the technical problem that the traditional domain name resolution and forwarding method needs to be configured and processed at the network level or server level, and has the disadvantage of complex operation, this application intercepts the network request event when a network request event is monitored, and obtains the event parameters of the network request event; extracts the key information in the event parameters, and generates several groups of multi-parameter groups by combining the key information; determines the domain name configuration operation and the parameters to be configured associated with each multi-parameter group according to the multi-parameter group and the preset domain name configuration file; modifies the network request event according to the domain name configuration operation and the parameters to be configured, and sends the modified network request event back to the browser. The browser plug-in is used for domain name management, and the user only needs to install the plug-in and configure the domain name in the browser, avoiding the complex operations of domain name resolution and forwarding at the network level required by the traditional domain name resolution and forwarding method. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 This is a flowchart of the first embodiment of the domain name management method of the present application;

[0043] Figure 2 This is a flowchart of the second embodiment of the domain name management method of the present application;

[0044] Figure 3 This is a flowchart of the third embodiment of the domain name management method of the present application;

[0045] Figure 4 This is a schematic diagram of the domain name management interaction interface of the third embodiment of the domain name management method of the present application;

[0046] Figure 5 A schematic diagram of the structure of a domain name management device in the hardware operating environment involved in the embodiment of the present application.

[0047] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0048] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0049] Domain name resolution and forwarding are two closely related operations in network communication. Domain name resolution refers to converting a domain name into a corresponding IP address so that the client can access the target server. Domain name forwarding refers to forwarding an access request from a domain name to another domain name or IP address.

[0050] In actual applications, domain name resolution and forwarding operations are usually used together to achieve more efficient and stable network communication. For example, internal domain name resolution is achieved by configuring DNS (Domain Name Server). At the same time, external access requests are forwarded by setting proxy servers or firewall rules.

[0051] That is, in order to achieve domain name resolution and forwarding, it is necessary to modify the configuration of network devices (such as routers, switches, etc.) or servers (such as DNS servers, proxy servers, etc.). These operations involve complex network technology and professional knowledge, which are difficult for ordinary users to apply.

[0052] In order to solve the above technical problems, the present application proposes a domain name management method, which is applied to a domain name management plug-in. When a network request event is detected, the network request event is intercepted and the event parameters of the network request event are obtained; key information in the event parameters is extracted, and several groups of multi-parameter groups are generated by combining the key information; the domain name configuration operation and the parameters to be configured associated with each multi-parameter group are determined according to the multi-parameter group and the preset domain name configuration file; the network request event is modified according to the domain name configuration operation and the parameters to be configured, and the modified network request event is sent back to the browser. The browser plug-in is used for domain name management. The user only needs to install the plug-in and configure the domain name in the browser, avoiding the complex operations of domain name resolution and forwarding at the network level required by the traditional domain name resolution and forwarding method.

[0053] In order to better understand the above technical solution, exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0054] The present application embodiment provides a domain name management method, referring to Figure 1 , Figure 1This is a flowchart of a first embodiment of a domain name management method of the present application.

[0055] In this embodiment, the domain name management method is applied to a domain name management plug-in, including:

[0056] Step S10: when a network request event is detected, the network request event is intercepted, and a domain name to be accessed of the network request event is obtained;

[0057] The domain name management plug-in in this embodiment is a software component used to assist users in managing and configuring domain name related settings. It is usually integrated into a browser, server or other application in the form of a plug-in to provide users with convenient domain name management functions. The domain name management functions in this embodiment mainly include domain name hiding, domain name resolution, domain name forwarding, redirection, returning custom content, executing JavaScript code and restricting access.

[0058] Domain name hiding means that in some cases, users may need to hide the real domain name, such as in a test or development environment, or when performing certain privacy protection operations. In this case, you can use a browser plug-in to replace the real domain name with another domain name or phrase to protect the privacy of the real domain name. For example, if the domain name of a website is "***.com", but the developer wants to hide this domain name during testing, you can use the domain name management to replace "***.com" with "test.***.com" or "dev.***.com". In addition, the browser plug-in can also replace the domain name with other phrases, such as replacing "***.com" with "aaa.com" or "bbb.com". The specific replacement content can be set by the user on the interactive interface provided by the domain name management plug-in according to their needs. By hiding the real domain name, you can prevent other users or third parties from tracking the user's behavior on the Internet. For example, when a user visits a website, if the website uses a third-party statistics service, then the statistics service may record the user's behavior. By hiding the domain name, you can prevent this tracking. It can also reduce the risk of users being attacked by malicious attacks. For example, some malicious websites may forge requests to allow users to visit other malicious websites. By hiding the domain name, you can reduce this risk. At the same time, in some cases, hiding the real domain name can improve the user's network security. For example, some websites may use insecure protocols (such as HTTP) for communication, which may cause the user's communication content to be eavesdropped. By hiding the domain name, this insecure communication can be prevented.

[0059] Domain name resolution is the process of mapping a domain name to a corresponding IP address or server. For example, the domain name ***.com is resolved to a local web server (IP address 192.xxx.1.2) for development and testing.

[0060] Domain forwarding refers to forwarding a network request for a domain name to another target address according to specific rules or configurations. When a user accesses a domain name, domain forwarding can forward the user's request to the specified target address to achieve request forwarding and proxying. For example, if there is a website with a domain name of www.***.com, the user can forward the request of the domain name to a server with a target address of 192.xxx.0.100 through the domain name management plug-in of this embodiment.

[0061] Redirect to another domain name: Redirect the domain name to be accessed to another domain name, that is, the browser will display the website content of another domain name. For example, redirect ***.com to ***.net.

[0062] Return custom content: For the domain name to be accessed, return a custom content or page instead of the actual parsed website content.

[0063] Execute JavaScript code: When accessing the domain name to be visited, execute a specified JavaScript code to achieve a specific function or effect.

[0064] Restrict access: Based on execution conditions, prohibit users from accessing the domain name during certain time periods or when specific conditions are met.

[0065] In this embodiment, the domain name management plug-in will register a listener when it is started to monitor network request events, including HTTP requests, WebSocket connections, etc. Among them, the listener can be a callback function, which will be called every time a network request is issued. Taking the Chrome browser as an example, the webRequest API can be used to intercept requests. This API provides an onBeforeRequest event, which is triggered when a network request is issued. The domain name management plug-in can register a callback function for this event to process the request.

[0066] When the callback function is called, that is, when the listener receives a network request event, the domain name management plug-in intercepts the network request event, that is, prevents the browser from directly sending the network request event, and instead passes the network request event to the domain name management plug-in for processing.

[0067] The domain name management plug-in extracts the requested URL (Uniform ResourceLocato, a method of indicating the location of information on the Internet's WWW service program) from the intercepted network request event, such as https: / / ***.com / path / to / resource. By parsing the URL, the requested domain name ***.com can be obtained.

[0068] Step S20: determining an alternative domain name configuration operation associated with the domain name to be accessed, and an execution condition associated with the alternative domain name configuration operation;

[0069] The alternative domain name configuration operation refers to the domain name configuration operation pre-set by the user for the domain name to be accessed according to the domain name management plug-in. The domain name configuration operation includes domain name hiding, domain name resolution, domain name forwarding, redirection, returning custom content, executing JavaScript code and restricting access. The execution condition is the condition pre-set by the user to trigger the execution of the domain name configuration operation, mainly including the execution time and execution environment.

[0070] It should be understood that for the same domain name to be accessed, different types of domain name configuration operations can be performed under different execution conditions. For example, for ***.com, it can be set to resolve ***.com to 192.xxx.1.2 during 9:00-18:00 on weekdays. It can also be set to hide ***.com at other times. The same type of domain name configuration operations can also be performed under different execution conditions. For example, for ***.com, it can be set to resolve ***.com to 192.xxx.1.2 during 9:00-18:00 on weekdays. It can also be set to resolve ***.com to 192.xxx.1.3 during 12:00-18:00 on weekends. It can also be performed under the same execution condition. Several domain name configuration operations can also be performed at the same time. For example, for ***.com, it can be set to resolve ***.com to 192.xxx.1.2 every day. It can also be set to hide the ***.com domain name every day.

[0071] For different combinations of candidate domain name configuration operations and different execution conditions, the key information that needs to be obtained is not exactly the same. Moreover, the more combinations of candidate domain name configuration operations and different execution conditions, the more key information needs to be obtained, otherwise it is difficult to accurately match domain name configuration operations and domain name configuration parameters for network request events.

[0072] Therefore, after step S20, the number of the candidate domain name configuration operations and the execution conditions can be counted, and when the domain name configuration operation is unique and the number of the execution conditions is 0, the domain name configuration operation and domain name configuration parameters of the network request event can be determined directly according to the domain name to be accessed. Otherwise, step S30 is executed.

[0073] Step S30: determining key information to be acquired according to the candidate domain name configuration operation and the execution condition;

[0074] Step S40: Acquire the key information of the network request event, and determine the domain name configuration operation and parameters to be configured associated with the key information according to the key information and a preset domain name configuration file;

[0075] The key information in this embodiment includes preset query parameters, request time and request environment. Among them, according to the operation type of the alternative domain name configuration operation, it can be determined whether it is necessary to obtain the preset query parameters, according to whether the execution condition contains the execution time, it can be determined whether it is necessary to obtain the request time, and according to whether the execution condition contains the execution environment, it can be determined whether it is necessary to obtain the request environment.

[0076] For example, the alternative domain name configuration operation includes domain name resolution. The execution conditions of the domain name resolution include: during 9:00-18:00 on weekdays, and during 12:00-18:00 on weekends. The key information to be obtained includes preset query parameters and request time. The preset query parameters are used to determine whether the network request event needs to perform a domain name resolution operation, and the request time is used to determine whether the domain name resolution operation can be performed, and how to perform it. Different execution times determine different parameters to be configured when modifying network request events. For example, the user presets that ***.com will be resolved to 192.xxx.1.2 during 9:00-18:00 on weekdays. And ***.com will be resolved to 192.xxx.1.3 during 12:00-18:00 on weekends. Both perform domain name resolution operations on ***.com, but different execution times determine different resolution addresses.

[0077] Key information comes from the event parameters of the network request event, such as the requested URL, request method, request header information, response status code, request time, and the context in which the request was initiated. Among them, the URL, such as https: / / ***.com / path / to / resource. By parsing the URL, you can get the domain name of the request, such as ***.com, as well as the path and parameters of the request. Request methods such as GET, POST, etc. The request header information usually contains more information about the request, such as a string indicating the meaning of the browser type, operating system, user agent, etc. The response status code, such as 200, 404, 500, etc., can reflect the result of the request. The request time can help determine the time point when the request occurred. The context in which the request was initiated, such as the page URL, page title, etc., can help determine the environment in which the request is located.

[0078] This application does not need to obtain all event parameters, but determines the event parameters to be obtained by determining the extraction path of the key information to be obtained. The specific key information extraction path includes: extracting the domain name to be accessed from the URL; and extracting preset query parameters and preset query parameters from the request header information; and extracting the request environment from the context of the request initiation, and the request environment includes the development environment, the test environment and the application environment.

[0079] For example, the key information to be obtained includes preset query parameters, request time, and request environment. For the network request time, the request URL is "http: / / ***.com / foo / bar?param1=value1", the request header information includes "User-Agent" and "Authorization", the request time is "2022-01-01 12:00:00", and the context (environment) of the request is "production environment". The key information obtained includes: preset query parameters: param1; request time: 2022-01-01 12:00:00; request environment: production environment.

[0080] After obtaining the key information, the domain name configuration operation and the parameters to be configured associated with the key information are determined according to the key information and the preset domain name configuration file. The preset domain name configuration file may be a defined set of rules. For example, a rule may be defined to replace all requested target domain names with a specified backup server IP address. The preset domain name configuration file may also be a blacklist and a whitelist. For example, the whitelist is used to record the parameters to be configured, such as the IP address to be resolved. Script-based modification: A scripting language (such as JavaScript) may be used to implement custom modification logic. The preset domain name configuration file may also be a script file. The script file may contain code for processing network request events, and the domain name configuration operation and the parameters to be configured may be dynamically determined according to the key information. The preset domain name configuration file may also be a mapping table. The mapping table may be regarded as a data structure for storing the correspondence between the domain name to be accessed, the domain name management operation, the execution condition and the parameters to be configured.

[0081] In this embodiment, the hierarchical query design of first querying the domain name to be accessed and then querying the key information can obtain parameters in stages according to actual needs, thereby avoiding the large amount of data processing and computing overhead that may be caused by querying all parameters at one time. Through hierarchical query, the required parameters can be obtained at a lower computing cost, improving the query efficiency. At the same time, the complex parameter organization structure can be divided into multiple levels, making parameter management clearer and easier to understand.

[0082] As an optional implementation method for querying a domain name configuration file, key information is processed into several multi-parameter groups, and the domain name configuration file is queried by inputting the multi-parameter groups. The specific process is as follows: according to the alternative domain name configuration operation, the multi-parameter group to be generated and the mandatory key information constituting each of the multi-parameter groups are determined; and according to the execution condition, the optional key information constituting each of the multi-parameter groups is determined; according to the mandatory key information and the optional key information, the multi-parameter group is generated. For example, if the domain name to be accessed is associated with a domain name resolution operation and a domain name forwarding operation, the number of multi-parameter groups to be generated is 2. The mandatory key information includes a preset query parameter to distinguish whether to perform domain name resolution or domain name forwarding. If there is an associated execution condition according to the alternative domain name configuration operation, the optional key information constituting the multi-parameter group is determined. For example, if the execution condition of the above-mentioned domain name resolution operation only includes time, the optional key information of the multi-parameter group includes request time. The two parameter groups finally generated are as follows: domain name resolution parameter group (domain name to be accessed, preset query parameter, request time); domain name forwarding parameter group (domain name to be accessed, preset query parameter). Compared with the implementation method of directly querying key information, this implementation method can split the key information into several smaller parameter groups, each parameter group only contains key information related to a specific domain name configuration operation. In this way, when querying the domain name configuration file, each parameter group can be quickly retrieved, thereby improving the query efficiency. At the same time, the query by parameter group can determine the composition of each parameter group according to the alternative domain name configuration operation and execution conditions, thereby ensuring that the key information in each parameter group is related to a specific domain name configuration operation. In this way, when querying the domain name configuration file, the required configuration information can be matched more accurately.

[0083] Step S50: modify the network request event according to the domain name configuration operation and the parameters to be configured, and send the modified network request event back to the browser.

[0084] According to the domain name configuration operation, determine the network request event attribute that needs to be modified. For example, if the domain name configuration operation is domain name replacement, the network request event attribute that needs to be modified is the target domain name; if the domain name configuration operation is domain name resolution, the network request event attribute that needs to be modified is the backup server IP address.

[0085] According to the parameter to be configured, the modified network request event attribute value is determined. For example, if the parameter to be configured is a new target domain name, the modified target domain name attribute value is the new target domain name; if the parameter to be configured is a new backup server IP address, the modified backup server IP address attribute value is the new backup server IP address.

[0086] Request the modification interval through the network request event attribute that needs to be modified. For example, if the target domain name that needs to be modified is in the request header, then the request modification interval is the request header; if the backup server IP address that needs to be modified is in the request body, then the request modification interval is the request body.

[0087] The request modification interval is modified according to the modified network request event attribute value. In the browser plug-in, the attributes of the network request event can be modified by programming languages ​​such as JavaScript.

[0088] Send the modified network request event back to the browser so that the browser can continue to process the modified network request.

[0089] In this embodiment, a domain name management method is proposed, which is applied to a domain name management plug-in. When a network request event is detected, the network request event is intercepted and the event parameters of the network request event are obtained; key information in the event parameters is extracted, and several groups of multi-parameter groups are generated by combining the key information; domain name configuration operations and parameters to be configured associated with each multi-parameter group are determined according to the multi-parameter groups and the preset domain name configuration files; the network request event is modified according to the domain name configuration operations and the parameters to be configured, and the modified network request event is sent back to the browser. The domain name management is performed using the browser plug-in, and the user only needs to install the plug-in and configure the domain name in the browser, avoiding the complex operations of domain name resolution and forwarding at the network level required by the traditional domain name resolution and forwarding methods.

[0090] Further, refer to Figure 2 , Figure 2 The second embodiment of the domain name management method of the present application is provided as a flow chart of the second embodiment of the present application, and the step S50 and the following steps are included:

[0091] Step S51: calling a preset data security engine to determine the data security measures corresponding to the request method;

[0092] Use the pre-configured data security engine to determine data security measures for different request methods. These measures may include data encryption, data integrity verification, access control, data privacy protection, and other aspects.

[0093] For example, for the GET method, the request parameters are directly exposed in the URL, which may lead to data leakage or tampering. Therefore, data security measures include: encrypting the request and response content through the HTTPS protocol to ensure the security and integrity of the data during transmission. When sending a request, encrypt the parameters to prevent data leakage or tampering. When performing domain name hiding or domain name resolution, these parameters need to be decrypted. When performing domain name hiding or domain name resolution, the request parameters need to be verified to ensure that they conform to the expected format and range to prevent malicious attacks.

[0094] For the POST method, the request parameters are usually in the request body, which is relatively safe. However, when performing domain name hiding or domain name resolution, it is still necessary to ensure the verification and security of the request content. Therefore, data security measures include: encrypting the request and response content through the HTTPS protocol to ensure the security and integrity of the data during transmission. When performing domain name hiding or domain name resolution, it is necessary to verify the request content to ensure that they conform to the expected format and range to prevent malicious attacks.

[0095] Step S52: obtaining a request environment of the network request event, and determining a safety factor of the network request event according to the request environment;

[0096] Step S53: Generate a data security policy for the network request event based on the data security measure and the security factor, and send the data security policy back to the browser.

[0097] A safety factor is calculated based on the request environment (such as development environment, test environment, or application environment) where the network request event is located. This safety factor can reflect the security level of the request environment and is used to guide the subsequent formulation of data security policies. For example, in a development environment, the safety factor may be low because developers need to debug and test conveniently; in an application environment, the safety factor should be high because user data security needs to be ensured.

[0098] Optionally, the data type and network environment of the network request event can also be obtained, and a set of security parameters can be calculated based on the data type, such as sensitive information, personal data, etc., and the network environment, such as a public network, an enterprise intranet, etc. These parameters can reflect the security requirements of the data and the security level of the network environment, and are used to guide the subsequent formulation of data security policies. For example, for sensitive information, security parameters may require the use of high-intensity encryption algorithms and strict access control measures; for personal data, security parameters may require compliance with relevant privacy laws and standards.

[0099] A data security matrix is ​​constructed based on the security factors and security parameters. This matrix can intuitively display the security requirements and security measures in different request environments, data types, and network environments, providing a basis for the subsequent formulation of data security policies. Combine the security requirements and data security measures in the data security matrix to formulate data security policies for current network request events. For example, for a network request event that transmits sensitive information in an application environment, the data security matrix may recommend the use of high-strength encryption algorithms (such as AES-256) and strict access control measures (such as SSL certificate verification). Based on these recommendations, we can configure corresponding data security policies, such as enforcing encryption and access control measures, to ensure the security of data during transmission.

[0100] The corresponding data security policy is sent to the browser together with the modified network request event. In this way, the browser can process and transmit the data in the network request event according to the data security policy, ensuring that the data can be fully protected during transmission and processing.

[0101] In this embodiment, a suitable data security policy is formulated according to factors such as the request method, request environment, data type and network environment of the network request event to ensure that the data in the network request event can be fully protected during transmission and processing. In addition, the data security policy of this embodiment can be adjusted and optimized according to different business scenarios, request environments and data types, and has strong adaptability.

[0102] Further, refer to Figure 3 , Figure 3 The third embodiment of the domain name management method of the present application is provided as a flowchart of the third embodiment of the domain name management method of the present application. Before step S10, the method further includes:

[0103] Step S00: when a preset trigger operation is received, a domain name management interaction interface is output, and a domain name configuration action is received according to the domain name management interaction interface;

[0104] When receiving the preset trigger operation, the domain name management interactive interface is output. Figure 4 , Figure 4 This is a schematic diagram of the domain name management interactive interface of the third embodiment of the domain name management method of this application. The interface includes elements such as a selection box for domain name configuration actions, an input box for execution conditions, and an input box for parameters to be configured, so that users can operate. And use mechanisms such as event listeners to monitor user input operations. When the user enters a domain name configuration action, the action can be obtained.

[0105] As an optional triggering method for outputting the domain name management interactive interface, a button can be set in the browser interface, and when the user clicks the button, the output of the domain name management interactive interface is triggered.

[0106] As another optional triggering method for outputting the domain name management interactive interface, one or more shortcut keys are set. When the user presses these shortcut keys, the output of the domain name management interactive interface is triggered.

[0107] As another optional triggering method for outputting the domain name management interactive interface, when the browser plug-in is started, the domain name management interactive interface can be automatically output and the domain name configuration action can be received.

[0108] As another optional triggering method for outputting the domain name management interactive interface, a scheduled task is set to trigger the output of the domain name management interactive interface at a specific time interval or a specific time point.

[0109] In addition, other events can be set to trigger the output of the domain name management interactive interface and the reception of domain name configuration actions according to actual needs, for example, when the network status changes, when a user logs in to a specific website, etc.

[0110] Step S01: obtaining configuration content associated with the domain name configuration action, and determining the domain name configuration operation corresponding to the configuration content, as well as the execution conditions and parameters to be configured associated with the domain name configuration operation;

[0111] Based on the user's input, the configuration content associated with the domain name configuration action can be obtained, such as the selected domain name configuration operation, the execution conditions of the domain name configuration operation, such as only executing at a specific time and in a specific network environment, etc., as well as the target domain name to be configured, the backup server IP address, etc.

[0112] Step S02: updating and saving a preset domain name configuration file according to the domain name configuration operation, the execution condition and the parameters to be configured.

[0113] According to the domain name configuration operation, the execution condition and the parameters to be configured, the preset domain name configuration file is updated. Programming languages ​​such as JavaScript can be used to write new configuration content, execution conditions and parameters to be configured into the domain name configuration file. Then, the storage function of the browser plug-in can be used to save the updated domain name configuration file locally. Or use the browser's cache mechanism to save the domain name configuration file in the user's browser cache. Or use HTML5's Web Storage technology to save the domain name configuration file in the browser's memory. This method can achieve persistent storage of data with fast reading and writing speeds. Or use HTML5's IndexedDB technology to save the domain name configuration file in the browser's database in the form of key-value pairs. This method can achieve persistent storage of data and support index queries. Or upload the domain name configuration file to the server and save it in the server's hard disk. This method can achieve data security and privacy protection, and there is no limit on the data size.

[0114] In this embodiment, compared with the traditional domain name resolution and forwarding method that needs to be configured and processed at the network level or server level, in this embodiment, the user can perform domain name configuration operations through an intuitive visual interface, which reduces the difficulty of operation and improves the operation efficiency. In addition, the user can modify and update the domain name configuration at any time through the visual operation interface according to actual needs, which improves the flexibility of configuration. At the same time, through the visual operation interface, the user can perform domain name configuration operations without professional technical knowledge, which reduces the technical threshold and expands the user range.

[0115] In addition, an embodiment of the present application also proposes a domain name management device.

[0116] Reference Figure 5 , Figure 5 A schematic diagram of the domain name management device structure of the hardware operating environment involved in the embodiment of the present application.

[0117] like Figure 5As shown, the domain name management device may include: a processor 1001, such as a core processor (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0118] Those skilled in the art will understand that Figure 5 The structure shown in the figure does not constitute a limitation on the domain name management device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0119] like Figure 5 As shown, the memory 1005 as a readable storage medium may include an operating system, a data storage module, a network communication module, a user interface module and a domain name management program.

[0120] exist Figure 5 In the domain name management device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the domain name management device of the present application can be set in the domain name management device, and the domain name management device calls the domain name management program stored in the memory 1005 through the processor 1001, and executes the domain name management method provided in the embodiment of the present application.

[0121] In addition, an embodiment of the present application also provides a readable storage medium.

[0122] The readable storage medium of the present application stores a domain name management program, and when the domain name management program is executed by a processor, the steps of the domain name management method described above are implemented.

[0123] Among them, the specific embodiments of the domain name management program stored in the readable storage medium of the present application being executed by the processor are basically the same as the embodiments of the above-mentioned domain name management method, and will not be repeated here.

[0124] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, the elements defined by the sentence "including a domain name management" do not exclude the existence of other identical elements in the process, method, article or system including the element.

[0125] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0126] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, including a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0127] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A domain name management method, It is characterized in that The domain name management method is applied to a domain name management plug-in, and includes the following steps: When receiving a preset trigger operation, outputting a domain name management interaction interface, and receiving a domain name configuration action according to the domain name management interaction interface; Acquire the configuration content associated with the domain name configuration action, and determine the domain name configuration operation corresponding to the configuration content, as well as the execution conditions and parameters to be configured associated with the domain name configuration operation; According to the domain name configuration operation, the execution condition and the parameters to be configured, updating and saving a preset domain name configuration file; When a network request event is detected, the network request event is intercepted, and the domain name to be accessed of the network request event is obtained; Determine an alternative domain name configuration operation associated with the domain name to be accessed, and an execution condition associated with the alternative domain name configuration operation, wherein the domain name configuration operation includes domain name hiding, domain name resolution, domain name forwarding, redirection, returning custom content, executing JavaScript code, and restricting access; Determining key information to be acquired according to the candidate domain name configuration operation and the execution condition; Acquire the key information of the network request event, and determine the domain name configuration operation and parameters to be configured associated with the key information according to the key information and a preset domain name configuration file; Calling a preset data security engine to determine the data security measures corresponding to the request method included in the network request event, obtaining the request environment of the network request event, and determining the security factor of the network request event according to the request environment, generating a data security policy for the network request event according to the data security measures and the security factor, and sending the data security policy back to the browser; or, Acquire the data type and network environment of the network request event, determine the security parameters of the network request event according to the data type and the network environment, construct a data security matrix according to the security factor and the security parameters, generate a data security policy according to the data security matrix and the data security measures, and send the data security policy back to the browser; According to the domain name configuration operation and the parameters to be configured, the network request event is modified, and the modified network request event is sent back to the browser.

2. The domain name management method according to claim 1, It is characterized in that The key information includes mandatory key information and optional key information. The step of determining the key information to be acquired according to the candidate domain name configuration operation and the execution condition includes: Determining, according to the candidate domain name configuration operation, a multi-parameter group to be generated and required key information constituting each of the multi-parameter groups; and Determining, according to the execution condition, optional key information constituting each of the multi-parameter groups; The step of obtaining the key information of the network request event and determining the domain name configuration operation and parameters to be configured associated with the key information according to the key information and a preset domain name configuration file includes: Acquire the mandatory key information and the optional key information of the network request event, and generate the multi-element parameter group according to the mandatory key information and the optional key information; According to the multi-parameter group and the preset domain name configuration file, the domain name configuration operation and the parameters to be configured associated with each multi-parameter group are determined.

3. The domain name management method according to claim 2, It is characterized in that After the step of obtaining the required key information and the optional key information of the network request event, the method further includes: Determining extraction paths of the mandatory key information and the optional key information; Determining event parameters to be obtained of the network request event according to the extraction path; The event parameters of the network request event are obtained, and the required key information and the optional key information in the event parameters are extracted.

4. The domain name management method according to claim 1, It is characterized in that The step of modifying the network request event according to the domain name configuration operation and the parameters to be configured includes: Determining a request modification interval of the network request event according to the domain name configuration operation; The request modification interval is modified according to the parameters to be configured, and the modified network request event is sent back to the browser.

5. A domain name management device, It is characterized in that The device comprises: a memory, a processor, and a domain name management program stored in the memory and executable on the processor, wherein the domain name management program is configured to implement the steps of the domain name management method according to any one of claims 1 to 4.

6. A readable storage medium, It is characterized in that The readable storage medium stores a domain name management program, and when the domain name management program is executed by the processor, the steps of the domain name management method according to any one of claims 1 to 4 are implemented.