Domain name ownership verification method, medium and electronic device

Abstract

The present invention provides a domain name verification method, medium and electronic device, the domain name verification method comprising: obtaining a domain name verification request sent by the domain name verification request end through the reverse proxy server, wherein the reverse proxy server is configured with an interception rule and is used to forward the domain name verification request directed to a target server to the server according to the interception rule; obtaining a domain name verification file matching the domain name verification request from the storage module as a response file; sending the response file to the reverse proxy server, so as to send the response file to the domain name verification request end through the reverse proxy server. The domain name verification method will not affect the running services.

Description

Technical Field

[0001] The present invention belongs to the field of network communication, and in particular relates to a domain name ownership verification method, medium and electronic equipment. Background Art

[0002] To ensure security, most current promotion channels (WeChat, Alipay, Byte, QQ, etc.) require domain name ownership verification when accessing the H5 page or server-side interface. The method for implementing domain name ownership verification in the prior art mainly includes the following steps: the verification party provides a domain name verification file to the access party; the access party uploads the domain name verification file to the server root directory corresponding to the domain name to be verified; the verification party obtains the domain name verification file under the domain name to be verified through a request and verifies the correctness of the file. However, the inventors have found in actual applications that for corporate users, if the prior art is used to verify the domain name ownership, then for each additional promotion channel or domain name to be verified, a technician is required to manually upload a domain name verification file to the root directory of the corresponding domain name server. This operation may bring risks to online services. Summary of the invention

[0003] In view of the above-mentioned shortcomings of the prior art, the purpose of the present invention is to provide a domain name ownership verification method, medium and electronic device to solve the problem that the existing domain name ownership verification method may bring risks to online services.

[0004] To achieve the above-mentioned purpose and other related purposes, the first aspect of the present invention provides a domain name verification method, which is applied to a server, wherein the server is communicatively connected to a domain name verification request terminal through a reverse proxy server, and at least one domain name verification file is stored in a storage module of the server, and the domain name verification method comprises: obtaining a domain name verification request sent by the domain name verification request terminal through the reverse proxy server, wherein the reverse proxy server is configured with an interception rule and is used to forward the domain name verification request directed to a target server to the server according to the interception rule; obtaining a domain name verification file matching the domain name verification request from the storage module as a response file; and sending the response file to the reverse proxy server, so as to send the response file to the domain name verification request terminal through the reverse proxy server.

[0005] In an embodiment of the first aspect, the server is configured to include a file query interface and a file save interface.

[0006] In an embodiment of the first aspect, the reverse proxy server sends the domain name ownership verification request to the server through the query file interface, and the server sends the response file to the reverse proxy server through the query file interface.

[0007] In an embodiment of the first aspect, the domain name ownership verification method further includes: acquiring the domain name verification file uploaded by the user through the file saving interface; and storing the domain name verification file in the storage module.

[0008] In an embodiment of the first aspect, the number of the target servers is at least one, and the server is one of the target servers, or is another server other than the target servers.

[0009] In an embodiment of the first aspect, the method for obtaining the domain name verification request through the reverse proxy server includes: intercepting the domain name verification request directed to the target server according to the interception rule through the reverse proxy server; and forwarding the intercepted domain name verification request to the server in a redirection manner through the reverse proxy server.

[0010] In an embodiment of the first aspect, forwarding the intercepted domain name verification request to the server in a redirection manner by the reverse proxy server includes: rewriting the URL of the intercepted domain name verification request into a format specified by the server by the reverse proxy server; and forwarding the domain name verification request after the URL is rewritten to the server by the reverse proxy server.

[0011] The second aspect of the present invention provides another domain name verification method, which is applied to a reverse proxy server. The reverse proxy server is configured with interception rules and is respectively communicated with the server and the domain name verification request end. The domain name verification method includes: intercepting a domain name verification request directed to a target server according to the interception rules, wherein the domain name verification request is sent by the domain name verification request end to the reverse proxy server; forwarding the domain name verification request to the server; obtaining a response file sent by the server, wherein the response file refers to a domain name verification file stored by the server that matches the domain name verification request; and forwarding the response file to the domain name verification request end.

[0012] The third aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the domain name ownership verification method described in any one of the first aspect of the present invention or the second aspect of the present invention.

[0013] The fourth aspect of the present invention provides an electronic device, comprising: a memory storing a computer program; a processor communicatively connected to the memory, and executing any one of the first aspect of the present invention or the domain name ownership verification method described in the second aspect of the present invention when calling the computer program.

[0014] As described above, the domain name ownership verification method, medium, and electronic device described in one or more embodiments of the present invention have the following beneficial effects:

[0015] The domain name verification method forwards the domain name verification request to the server through the forwarding mechanism of the reverse proxy service, and the server obtains the domain name verification file matching the domain name verification request through data query and sends it as a response file to the domain name verification request end. This process does not require the operation of the server, so it will not affect the running services.

[0016] Furthermore, the domain name ownership verification method can provide users with a unified domain name verification file management service through the storage module of the server. Specifically, users can upload domain name verification files to the storage module for centralized storage, thereby solving the problem of verification files being scattered across various servers and being inconvenient to manage in the related art, and avoiding the situation where domain name verification files are lost after the program is released. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1A Shown is an example diagram of the communication connection relationship between each end in a specific embodiment of the domain name ownership verification method described in the present invention.

[0018] Figure 1B Shown is a flow chart of a specific embodiment of the domain name ownership verification method of the present invention.

[0019] Figure 2 Shown is a flow chart of key steps in a specific embodiment of the domain name ownership verification method described in the present invention.

[0020] Figure 3A Shown is a flow chart of key steps in a specific embodiment of the domain name ownership verification method described in the present invention.

[0021] Figure 3B Shown is a detailed flow chart of step S32 of the domain name ownership verification method of the present invention in a specific embodiment.

[0022] Figure 4 Shown is a flow chart of a specific embodiment of the domain name ownership verification method of the present invention.

[0023] Figure 5 Shown is a flow chart of a specific embodiment of the domain name ownership verification method of the present invention.

[0024] Figure 6 Shown is a schematic structural diagram of the electronic device of the present invention in a specific embodiment.

[0025] Component number description

[0026] 11 Server

[0027] 12 Reverse Proxy Server

[0028] 13 Domain Name Verification Requester

[0029] 14 Target Server

[0030] 600 Electronic equipment

[0031] 610 Memory

[0032] 620 processor

[0033] 630 Display

[0034] Steps S11 to S13

[0035] Steps S21 to S22

[0036] Steps S31 to S32

[0037] Steps S321 to S322

[0038] Steps S41 to S44

[0039] Steps S51 to S56 DETAILED DESCRIPTION

[0040] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0041] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention. The illustrations only show the components related to the present invention rather than the number, shape and size of the components in actual implementation. The type, quantity and proportion of each component in actual implementation may be changed at will, and the component layout type may also be more complicated. In addition, in this article, relational terms such as "first", "second", etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0042] The method for implementing domain name ownership verification in the related technology mainly includes the following steps: the verification party provides the domain name verification file to the access party; the access party uploads the domain name verification file to the server root directory corresponding to the domain name to be verified; the verification party obtains the domain name verification file under the domain name to be verified through a request and verifies the correctness of the file. However, for corporate users, if the above method is used to verify the domain name ownership, then for each additional promotion channel or domain name to be verified, the technicians need to manually upload a domain name verification file to the root directory of the corresponding domain name server, and this operation may bring risks to the online services running.

[0043] At least to address the above-mentioned problem, the present invention provides a domain name ownership verification method, which will be described in detail below through specific embodiments combined with accompanying drawings.

[0044] See also Figure 1A and Figure 1B In one embodiment of the present invention, the domain name attribution verification method is applied to a server 11, and the server 11 is connected to a domain name attribution verification request terminal 13 through a reverse proxy server 12. In addition, the server 11 has a storage module, and the storage module stores at least one domain name verification file. Figure 1B As shown, the domain name ownership verification method described in this embodiment includes the following steps S11 to S13.

[0045] In step S11, the domain name verification request sent by the domain name verification request terminal 13 is obtained through the reverse proxy server 12. The reverse proxy server 12 is configured with an interception rule, and is used to forward the domain name verification request directed to the target server 14 to the server 11 according to the interception rule. In this embodiment, the domain name verification request directed to the target server 14 means that the original URL (Uniform Resource Locator) of the domain name verification request points to the target server 14.

[0046] In step S12, a domain name verification file matching the domain name ownership verification request is obtained from the storage module as a response file. The storage module may be configured to support operations such as writing file information and querying file information.

[0047] Optionally, a piece of information in the storage module may include two parts: a file name and file content. The file name refers to the name of the stored domain name verification file, which may be, for example, random characters ending with .txt. The file content refers to the content of the stored domain name verification file, which may be, for example, random characters. It should be noted that the information format in the above storage module is only one feasible way of this embodiment, but the present invention is not limited thereto.

[0048] In step S13 , the response file is sent to the reverse proxy server 12 , so that the response file is sent to the domain name ownership verification requester 13 through the reverse proxy server 12 .

[0049] According to the above description, the domain name verification method of this embodiment forwards the domain name verification request to the server 11 through the forwarding mechanism of the reverse proxy service 12, and the server 11 obtains the domain name verification file matching the domain name verification request through data query and sends it as a response file to the domain name verification request terminal 13. This process does not require the operation of the target server 14, so it will not affect the services running in the target server 14.

[0050] In one embodiment of the present invention, the server is configured to include a query file interface and a save file interface, wherein the query file interface is located between the server 11 and the reverse proxy server 12, and the save file interface is located between the server 11 and the user.

[0051] Optionally, the reverse proxy server 12 may send the domain name verification request to the server 11 through the query file interface. The server 11 may send the response file to the reverse proxy server 12 through the query file interface. For example, the domain name verification request may include a target file name, and the target file name refers to the file name of the domain name verification file that the domain name verification requester 13 expects to obtain. The server 11 performs a query operation in the storage module based on the target file name to obtain the domain name verification file that matches the domain name verification request.

[0052] Optionally, see Figure 2 The domain name ownership verification method may further include the following steps S21 and S22.

[0053] In step S21, the domain name verification file uploaded by the user is obtained through the file saving interface. Optionally, the user can upload the domain name verification file by uploading the file name and file content.

[0054] In step S22, the domain name verification file is stored in the storage module.

[0055] Next, the above process will be introduced by taking a domain name verification file in txt format as an example. Specifically, the user can upload the domain name verification file to the server 11 through the file saving interface, and the server 11 performs a data insertion operation in the storage module with the file name and file content of the domain name verification file as parameters to save the domain name verification file to the storage module.

[0056] Optionally, the domain name ownership verification method may further include: displaying an operation interface through a display, wherein the operation interface is used to prompt the user to upload the domain name verification file. It should be noted that, in some embodiments, the display may be included in the server 11; in other embodiments, the display may not be included in the server 11, in which case the display is communicatively connected to the server 11.

[0057] Optionally, the operation interface may include a file selection interface, through which the user may select a domain name verification file to be uploaded.

[0058] Optionally, after the user selects the domain name verification file to be uploaded, the domain name ownership verification method may further include: parsing the domain name verification file selected by the user to obtain its file name and file content.

[0059] Optionally, the domain name ownership verification method may further include: displaying the file name and file content of the domain name verification file selected by the user through the display for the user to perform secondary confirmation.

[0060] Optionally, after the domain name verification file is uploaded, the domain name attribution verification method may further include: displaying a saving result of the user through the display, the saving result being, for example, a successful saving or a failed saving.

[0061] In an embodiment of the present invention, the number of the target server 14 is at least one, and the server 11 may be one of the target servers 14 , or a server other than the target server 14 .

[0062] Optionally, Figure 3A The flowchart of obtaining the domain name ownership verification request through the reverse proxy server 12 in this embodiment is shown. Figure 3AAs shown, in this embodiment, the process of obtaining the domain name ownership verification request through the reverse proxy server 12 includes the following steps S31 to S32.

[0063] In step S31, the reverse proxy server 12 intercepts the domain name attribution verification request directed to the target server according to the interception rule. The interception rule may be, for example, a URL matching rule, which is used to specify the request format that needs to be intercepted. When the domain name verification file is a file in txt format, a request format configured in this embodiment may be, for example, all file resources in the root directory of the current domain name that are requested and the file name ends with .txt.

[0064] Preferably, the interception rule is configured in the form of a regular expression. Among them, a regular expression is a logical formula for string operations. Specifically, some specific characters and combinations of these specific characters are defined in advance to form a "rule string", and this "rule string" is used to express a filtering logic for the string. For example, if the domain name of one of the target servers 14 is https: / / www.abc.com, an interception rule in the form of a regular expression can be: https: / / abc.com / [A-Za-z0-9]{1,}\.txt. By adopting the regular expression method, the interception of a specific domain name attribution verification request can be implemented in an extremely simple way in this embodiment.

[0065] In step S32, the intercepted domain name verification request is forwarded to the server in a redirection manner through the reverse proxy server.

[0066] Optionally, Figure 3B The flowchart of this embodiment is shown as follows: the reverse proxy server forwards the intercepted domain name verification request to the server in a redirection manner. Figure 3B As shown, the above forwarding process includes the following steps S321 and S322.

[0067] In step S321, the reverse proxy server 12 rewrites the URL of the intercepted domain name verification request into the format specified by the server 11, and passes the file name as a parameter. Specifically, the reverse proxy server 12 obtains the file name of the domain name verification file according to the intercepted domain name verification request, and rewrites the URL of the intercepted domain name verification request according to the file name and the format specified by the server 11. For example, if the file name of the domain name verification file is sss.txt, the intercepted domain name verification request is https: / / www.abc.com / sss.txt, and the format specified by the server 11 is https: / / www.def.com / file? name=[file name], then, in step S321, the reverse proxy server 12 can obtain the file name sss.txt of the domain name verification file according to the intercepted domain name verification request, and rewrite the intercepted domain name verification request into https: / / www.def.com / file? name=sss.txt according to the file name and the format specified by the server 11.

[0068] In step S322, the reverse proxy server 12 forwards the domain name verification request after rewriting the URL to the server 11. For example, the reverse proxy server 12 may forward the request https: / / www.def.com / file?name=sss.txt after rewriting the URL to the server 11.

[0069] The present invention also provides a domain name ownership verification method applied to the reverse proxy server 12, wherein the reverse proxy server 12 is configured with an interception rule. Figure 4 In one embodiment of the present invention, the domain name ownership verification method includes the following steps S41 to S44.

[0070] In step S41 , the domain name ownership verification request directed to the target server 14 is intercepted according to the interception rule, wherein the domain name ownership verification request is sent from the domain name ownership verification request terminal 11 to the reverse proxy server 12 .

[0071] In step S42 , the domain name ownership verification request is forwarded to the server 11 .

[0072] In step S43, a response file sent by the server 11 is obtained, where the response file refers to a domain name verification file stored in a storage module of the server 11 and matching the domain name ownership verification request.

[0073] In step S44, the response file is forwarded to the domain name ownership verification requesting end 14.

[0074] It should be noted that Figure 4 The domain name ownership verification method applied to the reverse proxy server 12 corresponds to the domain name ownership verification method applied to the server 11 mentioned above. In order to save space in the specification, it will not be elaborated here.

[0075] Figure 5 The flowchart of the domain name attribution method in a preferred embodiment of the present invention is shown, wherein the domain name attribution verification method is applied to a system including a reverse proxy server 12 and a server 11, and the server 11 is configured to include a query file interface and a save file interface. It should be noted that the content of the preferred embodiment is not necessary for the present invention, and in some embodiments, all the content of the preferred embodiment may not be included. Figure 5 As shown, the domain name ownership verification method described in the preferred embodiment includes the following steps S51 to S56.

[0076] In step S51, the reverse proxy server 12 is configured according to the received configuration instruction. The user can configure the first matching rule and the second matching rule in the reverse proxy server 12 through the configuration instruction according to actual needs.

[0077] In step S52, the server 11 obtains the domain name verification file uploaded by the user and saves it in the storage module.

[0078] In step S53, when the reverse proxy server 12 receives the domain name verification request sent by the domain name verification request terminal 13, the reverse proxy server 12 forwards the domain name verification request to the query file interface of the server 11, wherein the domain name verification request carries the target file name.

[0079] In step S54, the server 11 searches the storage module for a domain name verification file that matches the domain name verification request as a response file according to the target file name carried in the domain name verification request.

[0080] In step S55, the server 11 forwards the response file to the reverse proxy server 12 through the query file interface.

[0081] In step S56 , the reverse proxy server 12 forwards the response file to the domain name ownership verification requester 13 .

[0082] It should be noted that the above-mentioned labels S51 to S56 are only used to identify different steps instead of limiting the execution order of the steps. In practical applications, the execution order of the above-mentioned steps can be determined according to requirements. For example, step S51 can be executed first and then step S52, or step S52 can be executed first and then step S51, or step S51 and step S52 can be executed at the same time.

[0083] Based on the above description of the domain name ownership verification method, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement Figure 1B , Figure 4 or Figure 5 In some embodiments, the computer-readable storage medium may be one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, kernel memory, disk storage medium, optical storage medium, flash memory device and / or other machine-readable medium for storing information.

[0084] Based on the above description of the domain name ownership verification method, the present invention also provides an electronic device. Figure 6 The structure diagram of the electronic device 600 in one embodiment of the present invention is shown. Figure 6 As shown, the electronic device 600 includes a memory 610 and a processor 620. The memory 610 stores a computer program. The processor 620 is connected to the memory 610 for executing the computer program when the computer program is called. Figure 1B , Figure 4 or Figure 5 The domain name ownership verification method shown.

[0085] In some embodiments, the memory 610 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory, on which a computer program is stored. The processor 620 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0086] Optionally, the electronic device 600 may further include a display 630, which is communicatively connected to the memory 610 and the processor 620, and is used to display a GUI interaction interface related to the domain name ownership verification method.

[0087] The protection scope of the domain name ownership verification method described in the present invention is not limited to the execution order of the steps listed in this embodiment. All solutions implemented by adding, reducing or replacing steps in the prior art based on the principles of the present invention are included in the protection scope of the present invention.

[0088] In summary, the domain name verification method of the present invention forwards the domain name verification request to the server through the forwarding mechanism of the reverse proxy service, and the server obtains the domain name verification file matching the domain name verification request through data query and sends it to the domain name verification request end as a response file. This process does not require the operation of the server, so it will not affect the running services. In addition, the domain name verification method can provide users with a unified domain name verification file management service through the storage module of the server. Specifically, users can upload multiple domain name verification files to the storage module, thereby solving the problem in the related art that the verification files are scattered on various servers and are inconvenient to manage, and can avoid the situation where the domain name verification file is lost after the program is released. Therefore, the present invention effectively overcomes the various shortcomings in the prior art and has a high industrial utilization value.

[0089] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A domain name ownership verification method, characterized in that: Applied to a server, the server is connected to a domain name verification requester through a reverse proxy server, and at least one domain name verification file is stored in a storage module of the server. The domain name verification method includes: Obtaining the domain name verification request sent by the domain name verification request end through the reverse proxy server, wherein the reverse proxy server is configured with an interception rule and is used to forward the domain name verification request directed to the target server to the server according to the interception rule; Acquire a domain name verification file matching the domain name ownership verification request from the storage module as a response file; The response file is sent to the reverse proxy server, so that the response file is sent to the domain name ownership verification requester through the reverse proxy server.

2. The domain name ownership verification method according to claim 1, characterized in that: The server is configured to include a file query interface and a file save interface.

3. The domain name ownership verification method according to claim 2, characterized in that: The reverse proxy server sends the domain name ownership verification request to the server through the query file interface, and the server sends the response file to the reverse proxy server through the query file interface.

4. The domain name ownership verification method according to claim 2, characterized in that: The domain name ownership verification method further includes: Obtain the domain name verification file uploaded by the user through the file saving interface; The domain name verification file is stored in the storage module.

5. The domain name ownership verification method according to claim 1, characterized in that: The number of the target servers is at least one, and the server is one of the target servers, or another server other than the target servers.

6. The domain name ownership verification method according to claim 1, characterized in that: The method for obtaining the domain name ownership verification request through the reverse proxy server includes: The reverse proxy server intercepts the domain name ownership verification request directed to the target server according to the interception rule; The intercepted domain name ownership verification request is forwarded to the server in a redirection manner through the reverse proxy server.

7. The domain name ownership verification method according to claim 6, characterized in that: Forwarding the intercepted domain name verification request to the server in a redirection manner through the reverse proxy server includes: Rewriting the intercepted URL of the domain name ownership verification request into a format specified by the server through the reverse proxy server; The domain name ownership verification request after rewriting the URL is forwarded to the server through the reverse proxy server.

8. A domain name ownership verification method, characterized in that: Applied to a reverse proxy server, the reverse proxy server is configured with interception rules and is respectively connected to the server and the domain name ownership verification requester for communication. The domain name ownership verification method includes: Intercepting a domain name ownership verification request directed to a target server according to the interception rule, wherein the domain name ownership verification request is sent by the domain name ownership verification request end to the reverse proxy server end; Forwarding the domain name ownership verification request to the server; Obtaining a response file sent by the server, wherein the response file refers to a domain name verification file stored by the server and matching the domain name ownership verification request; The response file is forwarded to the domain name ownership verification request end.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the domain name ownership verification method described in any one of claims 1 to 8 is implemented.

10. An electronic device, characterized in that: The electronic device comprises: A memory storing a computer program; A processor is communicatively connected to the memory and executes the domain name ownership verification method described in any one of claims 1-8 when calling the computer program.

Images