Verification information sending method, device, storage medium and electronic device

Abstract

The embodiment of the present application discloses a verification information sending method, device, storage medium and electronic device, and relates to the field of computer technology. The verification information sending method provided by the present application includes: receiving a verification information sending request from a target IP address, detecting whether the number of verification information sending requests received in a historical time period meets a preset condition; when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, sending a human-machine verification request to a user device corresponding to the target IP address; receiving human-machine verification information sent by the user device in response to the human-machine verification request, and determining whether the user device has passed the human-machine verification according to the human-machine verification information; when it is determined that the user device has passed the human-machine verification, sending verification information to the receiving address carried by the verification information sending request in response to the verification information sending request, and the verification information is used to verify the identity of the user associated with the address.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a verification information sending method, device, storage medium and electronic device. Background Art

[0002] Currently, the method for verifying the user device of the login system is to verify the user's identity by sending a text message verification code or an email verification code to the user device, so that the user can log in to the system through the user device and perform operations such as querying and deleting data in the system.

[0003] CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) is the full name of the Completely Automated Public Turing test to tell Computers and Humans Apart. It is a fully automatic program for verifying user identity. While preventing malicious password cracking and ticket fraud, it also provides users with a non-password login method so that users can log in to the system when they forget their password or account.

[0004] For example, the system sends a verification SMS to the user's device, and confirms the user's identity by receiving a verification code included in the verification SMS so that the user can log in to the system.

[0005] In order to ensure system security, limiting users' frequent requests for verification SMS is the key to ensuring system security and effective resource utilization. There are many common methods to limit users' frequent requests for verification SMS, but there are still situations that affect user experience or cannot effectively limit users' frequent requests for verification SMS. Summary of the invention

[0006] The embodiments of the present application provide a verification information sending method, device, storage medium and electronic device, which can solve the above problems. The technical solution is as follows:

[0007] In a first aspect, an embodiment of the present application provides a method for sending verification information, the method comprising:

[0008] Receive a verification information sending request from a target IP address, and detect whether the number of times the verification information sending request is received within a historical time period meets a preset condition;

[0009] When it is determined that the number of times the verification information sending request is received within the historical time period meets the preset condition, sending a human-machine verification request to the user device corresponding to the target IP address;

[0010] Receiving human-machine verification information sent by the user equipment in response to the human-machine verification request, and determining whether the user equipment passes the human-machine verification according to the human-machine verification information;

[0011] When it is determined that the user device passes the human-machine verification, the verification information is sent to the receiving address carried by the verification information sending request in response to the verification information sending request, and the verification information is used to verify the identity of the user and / or device associated with the receiving address.

[0012] In a second aspect, an embodiment of the present application provides a verification information sending device, the device comprising:

[0013] A first sending module is used to receive a verification information sending request from a target IP address, and detect whether the number of times the verification information sending request is received within a historical time period meets a preset condition;

[0014] A second sending module, configured to send a human-machine verification request to a user device corresponding to the target IP address when it is determined that the number of times the verification information sending request is received within a historical time period meets the preset condition;

[0015] A third sending module is used to receive the human-machine verification information sent by the user equipment in response to the human-machine verification request, and determine whether the user equipment passes the human-machine verification according to the human-machine verification information;

[0016] The fourth sending module is used to send the verification information to the receiving address carried by the verification information sending request in response to the verification information sending request when it is determined that the user device passes the human-machine verification, and the verification information is used to verify the identity of the user and / or device associated with the receiving address.

[0017] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0018] In a fourth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0019] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0020] In the present application, a verification information request is received from a target IP address and verification information is sent to a receiving address. The verification information is used to verify the identity of the user associated with the receiving address. For example, the receiving address is a mailbox or mobile phone number, and the verification information is a verification code. Further, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. The preset condition represents whether the verification information sending request of the target IP address in a certain time period is sent too frequently. Further, when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, it is determined that the verification information sending request from the target IP address is abnormal, and a human-machine verification request is sent to the user device corresponding to the target IP address to verify whether the user device is a human-machine. Only when it is determined that the user device is not a human-machine, the verification information is sent to the receiving address in response to the verification information sending request.

[0021] In other words, in this embodiment, by verifying whether the number of verification information sending requests received from the target IP address within the historical time period meets the preset conditions, and verifying whether the user device corresponding to the target IP address can pass the human-machine verification, the problem of the target IP address frequently requesting to send verification information and causing the interface to crash is avoided, thereby ensuring the security of the interface without affecting the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0023] Figure 1 It is a schematic diagram of the architecture of a verification information sending method provided in an embodiment of the present application;

[0024] Figure 2 It is a flowchart of a verification information sending method provided in an embodiment of the present application;

[0025] Figure 3 This is a schematic diagram of a verification code for human-machine verification provided in an embodiment of the present application;

[0026] Figure 4 It is a flowchart of a verification information sending method provided in an embodiment of the present application;

[0027] Figure 5 It is a flowchart of a verification information sending method provided in an embodiment of the present application;

[0028] Figure 6It is a structural diagram of a verification information sending device provided in an embodiment of the present application;

[0029] Figure 7 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0031] In the description of the present application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In the description of the present application, it should be noted that, unless otherwise clearly specified and limited, "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood in specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are a kind of "or" relationship.

[0032] The present application is described in detail below with reference to specific embodiments.

[0033] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the features, information and data involved in this specification are all obtained with full authorization.

[0034] Currently, the method for verifying the user device of the login system is to verify the user's identity by sending a text message verification code or an email verification code to the user device, so that the user can log in to the system through the user device and perform operations such as querying and deleting data in the system.

[0035] CAPTCHA (Fully Automatic Turing Test to Tell Computers and Humans Apart) is a fully automatic program for verifying user identity. It prevents malicious password cracking, ticket fraud, and other problems while also providing users with a non-password login method so that users can log in to the system in the event that they forget their password or account.

[0036] For example, the system sends a verification SMS to the user's device, and confirms the user's identity by receiving a verification code included in the verification SMS so that the user can log in to the system.

[0037] In order to ensure system security, limiting users' frequent requests for verification SMS is the key to ensuring system security and effective resource utilization. There are many common methods to limit users' frequent requests for verification SMS, but there are still situations that affect user experience or cannot effectively limit users' frequent requests for verification SMS.

[0038] In view of the above problems, this application proposes a verification information sending method to solve them. Figure 1 As shown, Figure 1 It is a schematic diagram of the architecture of a verification information sending method provided in an embodiment of this specification. Figure 1 The plurality of electronic devices include at least a plurality of user devices and a login verification server 101. The plurality of user devices include at least a user device 1021, a user device 1022, and a user device 1023. It is understood that Figure 1 The number and structure of the user devices and login verification servers shown in the figure are for illustration only, and this application does not impose any limitation on this.

[0039] The verification information sending method provided in this application can be applied to scenarios such as spam registration, malicious login, account theft, data crawling, malicious order brushing, false reviews, false transactions, false flash sales, malicious cash withdrawal, stolen card payment, etc.

[0040] The login verification server 101 includes but is not limited to physical or virtual processors, mobile stations (MobileStation, MS), mobile terminals (Mobile Terminal), mobile phones (Mobile Telephone), handsets and portable equipment (portable equipment), Bluetooth headsets, smart watches and other types. The login verification server 101 can communicate with one or more core networks via a radio access network (Radio Access Network, RAN).

[0041] For example, the login verification server 101 is a plurality of physical servers, and the plurality of physical servers are independent in hardware. Alternatively, the login verification server 101 is a plurality of virtual servers, and the plurality of virtual servers are deployed in the same hardware resource pool, and the deployment methods of the virtual servers include but are not limited to: VMware, Virtual Box and Virtual PC.

[0042] It is understandable that the login verification server 101 also has other service capabilities and functions to complete the tasks in the following embodiments. For example, the login verification server 101 also provides portal services, resource management services, and CI / CD services.

[0043] In the embodiment of the present application, a display device may also be installed on user devices such as user device 1021, user device 1022 or user device 1023. The display device may be various devices that can realize a display function, for example, the display device may be a cathode ray tube display (Cathode ray tube display, referred to as CR), a light emitting diode display (Light-emitting diode display, referred to as LED), an electronic ink screen, a liquid crystal display (Liquid crystal display, referred to as LCD), a plasma display panel (Plasma display panel, referred to as PDP), etc.

[0044] For example, the user can interact with the application program by using the display device of the user device 1021, and send a request for sending verification information to the login verification server 101 through the user device 1021, so that the login verification server 101 executes the verification information of the embodiment of the present application. For another example, the user can view the verification information sent by the login verification server 101 executing the verification information sending method through the user device 1021, and send the login information corresponding to the verification information to the login verification server 101 through the user device 1021, so that the login verification server 101 verifies the identity of the user according to the login information.

[0045] Multiple user devices and the login verification server 101 can communicate through a communication link established by a communication protocol, such as the gRPC protocol. gRPC is a high-performance, general-purpose open source remote procedure call (RPC) framework, which is mainly designed for mobile application development and based on the HTTP / 2 protocol standard, based on the protocol buffer (PB) serialization protocol development, and supports many development languages. In addition, the communication link can also be a wireless communication link or a wired communication link, for example, a wired communication link includes an optical fiber, a twisted pair or a coaxial cable, and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link.

[0046] based on Figure 1 The schematic diagram of the structure of the verification information sending method shown in FIG. Figure 2 As shown, it is a schematic diagram of a verification information sending method provided by an embodiment of the present application, which can be implemented by a computer program and can be run on a verification information sending device based on the von Neumann system. The computer program can be integrated into an application or run as an independent tool application.

[0047] Specifically, the verification information sending method includes:

[0048] S101, receiving a verification information sending request from a target IP address, and detecting whether the number of verification information sending requests received within a historical time period meets a preset condition.

[0049] An IP address (Internet Protocol Address) is a digital label assigned to each electronic device connected to a network that uses the Internet Protocol for communication. This digital label is usually unique and is used to identify the sender or receiver during IP communication. An IP address consists of two parts: a network part and a host part. The network part is used to identify the network to which the device is connected, while the host part is used to identify the specific device in the network. This structure enables IP addresses to support hierarchical addressing and routing, thereby efficiently transmitting data packets from the source address to the destination address.

[0050] There are two main versions of IP addresses: IPv4 (Internet Protocol version 4) and IPv6 (Internet Protocol version 6). IPv4 is the most widely used version, which uses a 32-bit (4-byte) address length and can theoretically support about 4.3 billion addresses. However, with the rapid development of the Internet, IPv4 address resources are close to exhaustion. To solve this problem, people developed IPv6, which uses a 128-bit (16-byte) address length and can support an almost unlimited number of addresses, thus meeting the needs of future Internet development.

[0051] The allocation and management of IP addresses are the responsibility of specialized organizations, such as the Internet Corporation for Assigned Names and Numbers (ICANN) and Regional Internet Registries (RIRs). These organizations are responsible for maintaining records of IP address allocations and ensuring the uniqueness and legitimacy of each IP address.

[0052] In the present application, the target IP address can be any IP address. The verification information sending request from the target IP address indicates that the verification information sending request comes from a certain IP address, or it can be understood that the user equipment sending the verification information sending request has the target IP address.

[0053] The request for sending verification information can be understood as the login verification server receiving the request for sending verification information sending the verification information to the receiving address carried in the request for sending verification information. The verification information is used to verify the identity of the user corresponding to the receiving address. The receiving address can be any address associated with the sending method corresponding to the request for sending verification information, and the receiving address is used to receive the verification information. For example, the receiving address is an email address, a mobile phone number, a MAC address, etc.

[0054] The verification information may be any data identifier including characters. For example, when the verification information is a verification code with 5 characters, such as "a1A09 (Q1, Q1-1, Q1-2, Q1-3, Q1-4, Q1-5)", Q1 is the verification code identifier, indicating the initial verification code generated by the server for the first time, i.e., the first verification code, and Q1-1, Q1-2, Q1-3, Q1-4, Q1-5 are character identifiers corresponding to each character constituting the verification code. It is understandable that those skilled in the art may specifically set the content included in the verification information according to actual conditions.

[0055] For example, user device 1021 has a target IP address. Login verification server 101 receives a verification information sending request from the target IP address, the verification information sending request carries a mobile phone number as a receiving address, and the content of the verification information is "Login / registration email verification code: 480681, valid for 5 minutes. Do not disclose to anyone."

[0056] When receiving a verification information sending request from a target IP address, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. In other words, the preset condition is related to the frequency of receiving verification information sending requests in a historical time period.

[0057] For example, the historical time period is 24 hours, and the preset condition is that the number of verification information sending requests received from the same target IP address within 24 hours is 100. For another example, the historical time period is one week, and the preset condition is that the number of verification information sending requests received from the same target IP address within the past week is 1000.

[0058] It is understandable that the specific content of the preset conditions is set by those skilled in the art according to actual conditions, and the embodiments of the present application do not impose any limitation on this.

[0059] S102: When it is determined that the number of times the verification information sending request is received within the historical time period meets a preset condition, a human-machine verification request is sent to a user device corresponding to the target IP address.

[0060] The human-machine verification request is used to instruct the user device to perform human-machine verification. Human-machine verification is a computer program used to distinguish whether the user of the user device is a computer or a real person. It verifies the identity, behavior and other information of the user using the user device through a variety of technical means to determine whether the user using the user device is a real person and whether it meets specific security requirements or rules.

[0061] A human-machine verification request sent to the target IP address, which usually requires the user to enter a verification code through the user device. The verification code includes character verification code, sliding verification code, text point verification code, nine-square point verification code, three-dimensional spherical verification code, location verification code, etc.

[0062] Among them, character-type verification codes include English characters, Chinese characters or distorted characters. The sliding verification code is to dig out a slider shadow under a background image, requiring the user to drag the slider to the position of the shadow. The text click verification code is to embed English characters or Chinese characters on a background image, requiring the user to click the corresponding characters. The nine-square grid click verification code is to place 9 pictures in the nine-square grid, requiring the user to select the target picture. The three-dimensional spherical verification code is to project the verification code characters onto the three-dimensional spherical surface, and verify by identifying the characters on the three-dimensional sphere. The position verification code can require the user to select inverted clothes or models.

[0063] In this application, the login verification server includes a verification code generation system, which is used to generate a verification code for human-machine verification to send a human-machine verification request to the user device of the target IP address. The verification code generation system mainly includes three parts: a natural language processing (NLP) question-answering system, a verification code service center, and a generative adversarial network (GAN) center. The verification code generation process mainly includes the following steps:

[0064] The NLP question-answering system builds a common sense knowledge graph, and builds a question bank generator based on the common sense knowledge graph to generate questions and corresponding candidate answers. The questions and candidate answers generated by the question bank generator are stored, and when a verification code for human-machine verification needs to be generated, the questions and candidate answers are sent to the verification code service center;

[0065] The verification code service center includes an offline part and an online part. The online part is mainly used to provide external verification code services and complete the data interaction between the front-end, the judgment center and the user back-end; the offline part receives the questions and candidate answers sent by the above-mentioned NLP question-answering system, calls the GAN center, and sends the above-mentioned questions and candidate answers to the GAN center;

[0066] The GAN center generates adversarial images based on the received questions and candidate answers, and feeds them back to the CAPTCHA service center;

[0067] The verification code service center stores the adversarial image generated by the GAN center in the database. When a verification code is required for human-machine verification, the online part is called to send the stored adversarial image to the online part. The online part sends the adversarial image to the user device at the target IP address, receives the user's operation data on the adversarial image through the user device, sends the operation data to the decision center of the login verification server, and accepts the decision result of the decision center to determine whether the user device passes the human-machine verification.

[0068] like Figure 3 As shown, Figure 3 This is a schematic diagram of a verification code for human-machine verification provided by an embodiment of the present application. The adversarial image includes a background image, question information, and answer information. The candidate answer generated by the GAN center is the click order of the three vehicle icons shown in the background image.

[0069] After the login verification server generates the verification code for the user's human-machine verification based on the above process, it sends a human-machine verification request to the user device at the target IP address. The user device responds to the human-machine verification request and displays the result on the display device. Figure 3 The confrontation picture shown.

[0070] The above implementation method generates simple common sense questions and reasoning questions through the NLP question-answering system, effectively avoiding the machine's recognition of the click and drag target of the sliding and clicking behavior verification code, and improving the problem of long verification time and poor user experience in the related technology of using a large paragraph of verification code. In addition, the GAN center generates adversarial images based on the question and its candidate answers, which greatly increases the difficulty of determining the question and its answer by identifying the adversarial image. Whether it is OCR or deep learning, it is difficult to identify the question and candidate answer in the adversarial image, thereby greatly increasing the security of the verification code. In addition, the question stem does not include the answer, the attack is difficult, the question is short, and the user experience is improved.

[0071] The technical solution of the embodiment of the present application can be implemented using the Javascript programming language, wherein rendering the adversarial image can use technologies such as Javascript canvas (canvas technology), CSS3 (Cascading StyleShee3, third-generation cascading style sheets) and 3D transform (three-dimensional transformation).

[0072] S103: Receive human-machine verification information sent by the user equipment in response to the human-machine verification request, and determine whether the user equipment passes the human-machine verification according to the human-machine verification information.

[0073] The user device displays a verification code for human-machine verification on a display device in response to the human-machine verification request. The user enters the answer corresponding to the verification code through the display device of the user device, so that the user device sends the answer as human-machine verification information to the login verification server.

[0074] As shown in 3, based on the Figure 3 The verification code for human-machine verification is shown. The user device receives the instruction of the user clicking on the three vehicle icons on the picture in sequence, and sends the above multiple instructions to the human-machine verification information to the login verification server.

[0075] The login verification server receives the human-machine verification information sent by the user device in response to the human-machine verification request, and determines whether the user device has passed the human-machine verification according to the human-machine verification information. Specifically, the verification code service center included in the login verification server stores the adversarial image generated by the GAN center in the database, and when a verification code is required for human-machine verification, calls the online part, sends the stored adversarial image to the online part, and the online part sends the adversarial image to the user device at the target IP address, receives the user's operation data on the adversarial image through the user device, sends the operation data to the decision center of the login verification server, and accepts the decision result of the decision center to determine whether the user device has passed the human-machine verification.

[0076] like Figure 3As shown, when the login verification server receives the human-machine verification information sent by the user device, including the sequence information of the user selecting three vehicle icons in sequence, it determines whether the user device has passed the human-machine verification based on the sequence information. When it is determined that the sequence information of the user selecting three vehicle icons in sequence matches the correct answer to the verification code, it is determined that the user device has passed the human-machine verification and the user device is operated by a real person. When it is determined that the sequence information of the user selecting three vehicle icons in sequence does not match the correct answer to the verification code, it is determined that the user device has not passed the human-machine verification and the user device is not operated by a real person.

[0077] S104: When it is determined that the user equipment passes human-machine authentication, in response to the authentication information sending request, authentication information is sent to a receiving address carried in the authentication information sending request.

[0078] When the number of verification information sending requests received from the target IP address during the detection history time period meets the preset conditions, and the user device of the target IP address is determined to have passed the human-machine verification through the human-machine verification request, the verification information is sent to the receiving address carried in the verification information sending request in response to the verification information sending request. The receiving address can be any address associated with the sending method corresponding to the verification information sending request, and the receiving address is used to receive the verification information. For example, the receiving address is an email address, a mobile phone number, a MAC address, etc.

[0079] For example, the login verification server 101 sends a verification message to the mobile phone number as the receiving address carried in the verification message sending request, and the content of the verification message is "Login / registration email verification code: 480681, valid for 5 minutes. Do not disclose to anyone." Further, the user device corresponding to the receiving address sends the verification code "480681" included in the verification message to the login verification server, so that the login verification server verifies the user identity based on the verification code and determines the user account logged in to the login verification server.

[0080] When it is determined that the user equipment has not passed the human-machine authentication, the verification information sending request is rejected and the verification information is stopped from being sent to the receiving address.

[0081] In the present application, a verification information request is received from a target IP address and verification information is sent to a receiving address. The verification information is used to verify the identity of the user associated with the receiving address. For example, the receiving address is a mailbox or mobile phone number, and the verification information is a verification code. Further, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. The preset condition represents whether the verification information sending request of the target IP address in a certain time period is sent too frequently. Further, when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, it is determined that the verification information sending request from the target IP address is abnormal, and a human-machine verification request is sent to the user device corresponding to the target IP address to verify whether the user device is a human-machine. Only when it is determined that the user device is not a human-machine, the verification information is sent to the receiving address in response to the verification information sending request.

[0082] In other words, in this embodiment, by verifying whether the number of verification information sending requests received from the target IP address within the historical time period meets the preset conditions, and verifying whether the user device corresponding to the target IP address can pass the human-machine verification, the problem of the target IP address frequently requesting to send verification information and causing the interface to crash is avoided, thereby ensuring the security of the interface without affecting the user experience.

[0083] In one embodiment, Figure 4 As shown, it is a schematic diagram of a verification information sending method provided by an embodiment of the present application, which can be implemented by a computer program and can be run on a verification information sending device based on the von Neumann system. The computer program can be integrated into an application or run as an independent tool application.

[0084] Specifically, the verification information sending method includes:

[0085] S201. Receive a verification information sending request from a target IP address.

[0086] See the above S101, which will not be repeated here.

[0087] S202: Check whether the number of times verification information sending requests are received within a historical time period meets a preset condition.

[0088] See the above S101, which will not be repeated here.

[0089] S203: When the number of times the verification information sending request is received within the detection history time period meets a preset condition, a human-machine verification request is sent to the user device corresponding to the target IP address.

[0090] See the above S102, which will not be described again here.

[0091] S204: Receive human-machine verification information sent by the user equipment in response to the human-machine verification request.

[0092] See the above S103, which will not be described again here.

[0093] S205: Determine whether the user device has passed the human-machine verification according to the human-machine verification information?

[0094] See the above S103, which will not be described again here.

[0095] S206: When it is determined that the user equipment passes the human-machine authentication, obtain first authentication information associated with the receiving address carried in the authentication information sending request from the cache server.

[0096] A cache server is a server that stores frequently accessed web content in a system that is closer to the user and has a faster access speed to improve the access speed of the content. There are many types of cache server systems, each with its own unique characteristics and advantages, such as: Memcached: A commonly used memory cache system that is widely used to reduce database access pressure. It is a distributed cache system that can store any type of data. Redis: Not only a cache system, but also a data structure server that supports a variety of data structures such as strings, lists, collections, etc. Compared with Memcached, Redis provides richer data structures and functions, such as transaction processing and persistent storage. EhCache: A Java-based distributed cache system suitable for Java applications. It is fast, reliable and easy to use, and can effectively reduce the number of database accesses. Caffeine: An advanced cache library on the Java platform with flexible loading and expiration strategies that can realize automatic loading and expiration processing of data. In the embodiment of the present application, the type of cache server is set by relevant technical personnel according to needs.

[0097] The verification information includes the first verification information. The first verification information is the verification information cached in the cache server during the historical time period, and the verification information is associated with the receiving address carried in the verification information sending request. For example, the verification information sending request from the target IP address is divided into the verification information sending request for receiving address 1 and the verification information sending request for receiving address 2, and the first verification information associated with receiving address 1 and the first verification information associated with receiving address 2 are stored in the cache server. This is because the user may request verification information for two receiving addresses through the same user device, so the verification information cached in the cache server, that is, the first verification information, is associated with the receiving address.

[0098] For example, during the historical time period, the login verification server sends verification information to the mobile phone number that is carried as the receiving address in the verification information sending request, and the content of the verification information is "Login / registration email verification code: 480681, valid for 5 minutes. Do not disclose to anyone". Further, the login verification server caches the verification information as the first verification information in association with the receiving address to the cache server. When the login verification server receives the verification information sending request carrying the mobile phone number that is carried as the receiving address again, it obtains the first verification information stored in association with the receiving address from the cache server.

[0099] S208. In response to the verification information sending request, send first verification information to a receiving address.

[0100] When a user device of a certain IP address requests verification information, and the number of verification information sending requests received in the historical time period meets the preset conditions and the user device passes the human-machine verification, or the number of verification information sending requests received in the historical time period does not meet the preset conditions, the login verification service area first checks whether a copy of the verification information, i.e., the first verification information, has been saved in the cache of the cache server. If so, it is directly returned to the user device; if not, verification information is generated and associated with the receiving address and saved in the cache server, and then returned to the user device. Therefore, this embodiment can save network bandwidth and server resources and improve user access speed.

[0101] S209: When it is determined that the user device has not passed the human-machine authentication, refuse to send the authentication information.

[0102] After receiving the human-machine verification information sent by the user device in response to the human-machine verification request, and determining whether the user device has passed the human-machine verification according to the human-machine verification information, the method further includes: when it is determined that the user device has not passed the human-machine verification, refusing to send the verification information to the receiving address. In other words, when it is determined that the user device has not passed the human-machine verification, refusing to respond to the verification information sending request, and stopping sending the verification information to the receiving address, thereby protecting the interface security of the login verification server.

[0103] In the present application, a verification information request is received from a target IP address and verification information is sent to a receiving address. The verification information is used to verify the identity of the user associated with the receiving address. For example, the receiving address is a mailbox or mobile phone number, and the verification information is a verification code. Further, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. The preset condition represents whether the verification information sending request of the target IP address in a certain time period is sent too frequently. Further, when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, it is determined that the verification information sending request from the target IP address is abnormal, and a human-machine verification request is sent to the user device corresponding to the target IP address to verify whether the user device is a human-machine. Only when it is determined that the user device is not a human-machine, the verification information is sent to the receiving address in response to the verification information sending request.

[0104] In other words, in this embodiment, by verifying whether the number of verification information sending requests received from the target IP address within the historical time period meets the preset conditions, and verifying whether the user device corresponding to the target IP address can pass the human-machine verification, the problem of the target IP address frequently requesting to send verification information and causing the interface to crash is avoided, thereby ensuring the security of the interface without affecting the user experience.

[0105] In one embodiment, Figure 5 As shown, it is a schematic diagram of a verification information sending method provided by an embodiment of the present application, which can be implemented by a computer program and can be run on a verification information sending device based on the von Neumann system. The computer program can be integrated into an application or run as an independent tool application.

[0106] Specifically, the verification information sending method includes:

[0107] S301. In response to a historical verification information sending request from a target IP address to send verification information to a receiving address, first verification information is sent to a receiving address.

[0108] The historical verification information sending request can be understood as the verification information sending request received from the target IP address in the historical time period and sending verification information to the receiving address. The historical time period can be understood as the time period before the start time when the verification information sending request from the target IP address is received this time.

[0109] In response to the historical verification information sending request, the first verification information is sent to the receiving address of the historical verification information sending request. In the above process, the steps of detecting whether the number of receiving the historical verification information sending request in the historical time period meets the preset condition based on the historical verification information sending request and determining whether the user device passes the human-machine verification may be included.

[0110] S302: Associating the first verification information with the receiving address and caching them in a cache server.

[0111] The first verification information is associated with the receiving address and cached in the cache server. For example, during the historical time period, a historical verification information sending request from the target IP address and carrying the receiving address 1 and a historical verification information sending request carrying the receiving address 2 are received. After sending different first verification information to the receiving address 1 and the receiving address 2 respectively in response to the historical verification information sending request, the first verification information of the receiving address 1 and the receiving address 1 are associated and stored in the cache server, and the first verification information of the receiving address 2 and the receiving address 2 are associated and stored.

[0112] In this embodiment, when the storage time of the first verification information and the receiving address stored in the cache server for association reaches a preset time, the cache server is instructed to delete the first verification information. The preset time can be any time, for example, the preset time is 5 minutes. In other words, the cache server only associates and stores the first verification information and the receiving address for the preset time.

[0113] S303: Receive a verification information sending request from the target IP address.

[0114] See the above S101, which will not be repeated here.

[0115] S304: Check whether the number of times verification information sending requests are received within a historical time period meets a preset condition.

[0116] See the above S101, which will not be repeated here.

[0117] S305: When the number of times the verification information sending request is received within the detection history time period meets a preset condition, a human-machine verification request is sent to the user device corresponding to the target IP address.

[0118] See the above S102, which will not be described again here.

[0119] When it is determined that the number of times a verification information sending request is received within a historical time period does not meet a preset condition, third verification information associated with a receiving address carried by the verification information sending request is obtained from a cache server, and the verification information includes the third verification information; in response to the verification information sending request, the third verification information is sent to the receiving address.

[0120] It is worth noting that in this embodiment, the third verification information, that is, the first verification information, is the first verification information cached to the cache server in response to a historical verification information sending request from the target IP address and sending verification information to the receiving address, and after sending the first verification information to the receiving address.

[0121] S306: Receive human-machine verification information sent by the user equipment in response to the human-machine verification request.

[0122] See the above S103, which will not be described again here.

[0123] S307: Determine whether the user device has passed the human-machine verification according to the human-machine verification information?

[0124] See the above S103, which will not be described again here.

[0125] S308: When it is determined that the user device has passed the human-machine verification, check whether there is first verification information stored in association with the receiving address carried in the verification information sending request in the cache server?

[0126] When it is determined that the user device has passed the human-machine authentication, a query request is sent to the cache server to detect whether the cache server has the first authentication information stored in association with the receiving address carried in the authentication information sending request. In this embodiment, in order to prevent other users from impersonating a user to log in to the system through the authentication information, the cache server only associates and stores the first authentication information and the receiving address for a preset time period. Therefore, when it is determined that the number of times the authentication information sending request is received within the historical time period meets the preset condition and the user device has passed the human-machine authentication, it is necessary to first detect whether the cache server has the first authentication information stored in association with the receiving address carried in the authentication information sending request.

[0127] S309: When it is determined that the first verification information exists in the detection cache server, obtain the first verification information from the cache server.

[0128] See the above S206, which will not be described again here.

[0129] S310: In response to a request to send verification information, send first verification information to a receiving address.

[0130] See the above S207, which will not be described again here.

[0131] S311. When it is determined that the first verification information does not exist in the cache server, generate second verification information in response to a verification information sending request, and send the second verification information to a receiving address.

[0132] The type and format of the second verification information and the first verification information may be the same or different. For example, the second verification information may be any data identifier including characters. The content of the first verification information is "Login / registration email verification code: 480681, valid for 5 minutes. Do not disclose to anyone". After the cache server deletes the first verification information associated with the receiving address, the login verification server generates the second verification information in response to the verification information sending request. The second verification information is "Login / registration email verification code: 854912, valid for 5 minutes. Do not disclose to anyone".

[0133] S312: When it is determined that the user device has not passed the human-machine authentication, refuse to send the authentication information.

[0134] See the above S208, which will not be repeated here.

[0135] In the present application, a verification information request is received from a target IP address and verification information is sent to a receiving address. The verification information is used to verify the identity of the user associated with the receiving address. For example, the receiving address is a mailbox or mobile phone number, and the verification information is a verification code. Further, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. The preset condition represents whether the verification information sending request of the target IP address in a certain time period is sent too frequently. Further, when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, it is determined that the verification information sending request from the target IP address is abnormal, and a human-machine verification request is sent to the user device corresponding to the target IP address to verify whether the user device is a human-machine. Only when it is determined that the user device is not a human-machine, the verification information is sent to the receiving address in response to the verification information sending request.

[0136] In other words, in this embodiment, by verifying whether the number of verification information sending requests received from the target IP address within the historical time period meets the preset conditions, and verifying whether the user device corresponding to the target IP address can pass the human-machine verification, the problem of the target IP address frequently requesting to send verification information and causing the interface to crash is avoided, thereby ensuring the security of the interface without affecting the user experience.

[0137] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0138] See also Figure 6, which shows a schematic diagram of the structure of a verification information sending device provided by an exemplary embodiment of the present application. The verification information sending device can be implemented as all or part of the device through software, hardware or a combination of both. The device includes a first sending module 401, a second sending module 402, a third sending module 403 and a fourth sending module 404.

[0139] The first sending module 401 is used to receive a verification information sending request from a target IP address, and detect whether the number of times the verification information sending request is received within a historical time period meets a preset condition;

[0140] The second sending module 402 is used to send a human-machine verification request to the user equipment corresponding to the target IP address when it is determined that the number of times the verification information sending request is received within the historical time period meets the preset condition;

[0141] The third sending module 403 is used to receive the human-machine verification information sent by the user equipment in response to the human-machine verification request, and determine whether the user equipment passes the human-machine verification according to the human-machine verification information;

[0142] The fourth sending module 404 is used to send the verification information to the receiving address carried by the verification information sending request in response to the verification information sending request when it is determined that the user device passes the human-machine verification. The verification information is used to verify the identity of the user and / or device associated with the receiving address.

[0143] In one embodiment, the fourth sending module 404 includes:

[0144] A first human-machine verification unit, configured to obtain, when determining that the user equipment passes the human-machine verification, first verification information associated with the receiving address carried in the verification information sending request from a cache server, wherein the verification information includes the first verification information;

[0145] The second human-machine verification unit is used to send the first verification information to the receiving address in response to the verification information sending request.

[0146] In one embodiment, the verification information sending device further includes:

[0147] A fifth sending module, configured to send the first verification information to the receiving address in response to a historical verification information sending request from the target IP address to send the verification information to the receiving address;

[0148] The sixth sending module is used to associate the first verification information with the receiving address and cache it in the cache server.

[0149] In one embodiment, the verification information sending module further includes:

[0150] The seventh sending module is used to instruct the cache server to delete the first verification information when detecting that the storage time of the first verification information and the receiving address stored in association with each other by the cache server reaches a preset time.

[0151] In one embodiment, the first human-machine verification unit includes:

[0152] A first verification subunit is used to detect whether there is first verification information stored in association with the receiving address carried in the verification information sending request in the cache server when it is determined that the user equipment passes the human-machine verification;

[0153] The second verification subunit is configured to obtain the first verification information from the cache server when it is determined that the first verification information exists in the cache server.

[0154] In one embodiment, the fourth sending module 404 further includes:

[0155] The third human-machine verification unit is used to generate second verification information in response to the verification information sending request when it is determined that the first verification information does not exist in the cache server, and send the second verification information to the receiving address, wherein the verification information includes the second verification information.

[0156] In one embodiment, the verification information sending device further includes:

[0157] an eighth sending module, configured to obtain, when it is determined that the number of times the verification information sending request is received within a historical time period does not meet a preset condition, third verification information associated with a receiving address carried in the verification information sending request from a cache server, wherein the verification information includes the third verification information;

[0158] A ninth sending module is configured to send the third verification information to the receiving address in response to the verification information sending request.

[0159] In one embodiment, the verification information sending device further includes:

[0160] The tenth sending module is used to refuse to send the verification information to the receiving address when it is determined that the user equipment has not passed the human-machine verification.

[0161] In the present application, a verification information request is received from a target IP address and verification information is sent to a receiving address. The verification information is used to verify the identity of the user associated with the receiving address. For example, the receiving address is a mailbox or mobile phone number, and the verification information is a verification code. Further, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. The preset condition represents whether the verification information sending request of the target IP address in a certain time period is sent too frequently. Further, when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, it is determined that the verification information sending request from the target IP address is abnormal, and a human-machine verification request is sent to the user device corresponding to the target IP address to verify whether the user device is a human-machine. Only when it is determined that the user device is not a human-machine, the verification information is sent to the receiving address in response to the verification information sending request.

[0162] In other words, in this embodiment, by verifying whether the number of verification information sending requests received from the target IP address within the historical time period meets the preset conditions, and verifying whether the user device corresponding to the target IP address can pass the human-machine verification, the problem of the target IP address frequently requesting to send verification information and causing the interface to crash is avoided, thereby ensuring the security of the interface without affecting the user experience.

[0163] It should be noted that the verification information sending device provided in the above embodiment only uses the division of the above functional modules as an example when executing the verification information sending method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the verification information sending device provided in the above embodiment and the verification information sending method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0164] 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.

[0165] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 1 - Figure 5 The verification information sending method of the embodiment shown in the figure can be specifically executed by referring to Figure 1 - Figure 5 The specific description of the illustrated embodiment will not be repeated here.

[0166] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figure 1 - Figure 5 The verification information sending method of the embodiment shown in the figure can be specifically executed by referring to Figure 1 - Figure 5 The specific description of the illustrated embodiment will not be repeated here.

[0167] See also Figure 7 , is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 7 As shown, the electronic device 500 may include: at least one processor 501 , at least one network interface 504 , a user interface 503 , a memory 505 , and at least one communication bus 502 .

[0168] The communication bus 502 is used to realize the connection and communication between these components.

[0169] The user interface 503 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 503 may also include a standard wired interface and a wireless interface.

[0170] The network interface 504 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0171] Among them, the processor 501 may include one or more processing cores. The processor 501 uses various interfaces and lines to connect various parts within the entire server 500, and executes various functions and processes data of the server 500 by running or executing instructions, programs, code sets or instruction sets stored in the memory 505, and calling data stored in the memory 505. Optionally, the processor 501 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 501 can integrate one or a combination of a processor (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 501, and it can be implemented separately through a chip.

[0172] Among them, the memory 505 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 505 includes a non-transitory computer-readable storage medium. The memory 505 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 505 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 505 may also be optionally at least one storage device located away from the aforementioned processor 501. As Figure 7 As shown, the memory 505 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a verification information sending application.

[0173] exist Figure 7 In the electronic device 500 shown, the user interface 503 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 501 can be used to call the verification information sending application stored in the memory 505, and specifically perform the following operations:

[0174] Receive a verification information sending request from a target IP address, and detect whether the number of times the verification information sending request is received within a historical time period meets a preset condition;

[0175] When it is determined that the number of times the verification information sending request is received within the historical time period meets the preset condition, sending a human-machine verification request to the user device corresponding to the target IP address;

[0176] Receiving human-machine verification information sent by the user equipment in response to the human-machine verification request, and determining whether the user equipment passes the human-machine verification according to the human-machine verification information;

[0177] When it is determined that the user device passes the human-machine authentication, the verification information is sent to the receiving address carried in the verification information sending request in response to the verification information sending request, and the verification information is used to verify the identity of the user associated with the receiving address.

[0178] In one embodiment, the processor 501 executes, when determining that the user equipment passes the human-machine verification, sending the verification information to the receiving address carried by the verification information sending request in response to the verification information sending request, specifically executing:

[0179] When it is determined that the user equipment passes human-machine authentication, obtaining first authentication information associated with the receiving address carried in the authentication information sending request from a cache server, where the authentication information includes the first authentication information;

[0180] In response to the verification information sending request, the first verification information is sent to the receiving address.

[0181] In one embodiment, before the processor 501 executes, when determining that the user equipment passes the human-machine authentication, obtaining, from the cache server, the first authentication information associated with the receiving address carried in the authentication information sending request, further executes:

[0182] In response to a historical verification information sending request from the target IP address to send the verification information to the receiving address, sending the first verification information to the receiving address;

[0183] The first verification information is associated with the receiving address and cached in the cache server.

[0184] In one embodiment, after the processor 501 executes the step of associating the first verification information with the receiving address and caching the first verification information to the cache server, the processor 501 further executes:

[0185] When it is detected that the storage time for which the cache server associates and stores the first verification information with the receiving address reaches a preset time, the cache server is instructed to delete the first verification information.

[0186] In one embodiment, the processor 501 executes, when determining that the user equipment passes the human-machine verification, obtaining, from the cache server, the first verification information associated with the receiving address carried by the verification information sending request, specifically performing:

[0187] When it is determined that the user equipment passes human-machine authentication, detecting whether there is first authentication information stored in association with the receiving address carried in the authentication information sending request in the cache server;

[0188] When it is determined that the first verification information exists in the cache server, the first verification information is obtained from the cache server.

[0189] In one embodiment, after the processor 501 executes, when determining that the user equipment passes the human-machine verification, detecting whether there is first verification information stored in association with the receiving address carried by the verification information sending request in the cache server, further executes:

[0190] When it is determined that the first verification information does not exist in the cache server, second verification information is generated in response to the verification information sending request, and the second verification information is sent to the receiving address, where the verification information includes the second verification information.

[0191] In one embodiment, after the processor 501 executes the receiving of the verification information sending request from the target IP address and detects whether the number of times the verification information sending request is received within a historical time period meets a preset condition, it further executes:

[0192] When it is determined that the number of times the verification information sending request is received within the historical time period does not meet the preset condition, obtaining third verification information associated with the receiving address carried in the verification information sending request from the cache server, the verification information including the third verification information;

[0193] In response to the verification information sending request, the third verification information is sent to the receiving address.

[0194] In one embodiment, after the processor 501 executes the receiving of the human-machine verification information sent by the user device in response to the human-machine verification request and determines whether the user device passes the human-machine verification according to the human-machine verification information, it further executes:

[0195] When it is determined that the user equipment has not passed the human-machine authentication, the authentication information is refused to be sent to the receiving address.

[0196] In the present application, a verification information request is received from a target IP address and verification information is sent to a receiving address. The verification information is used to verify the identity of the user associated with the receiving address. For example, the receiving address is a mailbox or mobile phone number, and the verification information is a verification code. Further, it is detected whether the number of verification information sending requests received in a historical time period meets a preset condition. The preset condition represents whether the verification information sending request of the target IP address in a certain time period is sent too frequently. Further, when it is determined that the number of verification information sending requests received in a historical time period meets the preset condition, it is determined that the verification information sending request from the target IP address is abnormal, and a human-machine verification request is sent to the user device corresponding to the target IP address to verify whether the user device is a human-machine. Only when it is determined that the user device is not a human-machine, the verification information is sent to the receiving address in response to the verification information sending request.

[0197] In other words, in this embodiment, by verifying whether the number of verification information sending requests received from the target IP address within the historical time period meets the preset conditions, and verifying whether the user device corresponding to the target IP address can pass the human-machine verification, the problem of the target IP address frequently requesting to send verification information and causing the interface to crash is avoided, thereby ensuring the security of the interface without affecting the user experience.

[0198] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0199] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0200] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A verification information sending method, characterized in that: The method comprises: Receive a verification information sending request from a target IP address, and detect whether the number of times the verification information sending request is received within a historical time period meets a preset condition; When it is determined that the number of times the verification information sending request is received within the historical time period meets the preset condition, sending a human-machine verification request to the user device corresponding to the target IP address; Receiving human-machine verification information sent by the user equipment in response to the human-machine verification request, and determining whether the user equipment passes the human-machine verification according to the human-machine verification information; When it is determined that the user equipment passes human-machine authentication, in response to the authentication information sending request, sending the authentication information to a receiving address carried in the authentication information sending request, where the authentication information is used to verify the identity of the user associated with the receiving address; Wherein, when it is determined that the user equipment passes the human-machine verification, sending the verification information to the receiving address carried in the verification information sending request in response to the verification information sending request includes: When it is determined that the user equipment passes human-machine authentication, obtaining first authentication information associated with the receiving address carried in the authentication information sending request from a cache server, where the authentication information includes the first authentication information; In response to the verification information sending request, sending the first verification information to the receiving address; Wherein, before obtaining the first verification information associated with the receiving address carried in the verification information sending request from the cache server when determining that the user equipment passes the human-machine verification, it also includes: In response to a historical verification information sending request from the target IP address to send the verification information to the receiving address, sending the first verification information to the receiving address; Associating the first verification information with the receiving address and caching the same in the cache server; Wherein, after receiving the verification information sending request from the target IP address and detecting whether the number of times the verification information sending request is received within a historical time period meets a preset condition, the method further includes: When it is determined that the number of times the verification information sending request is received within the historical time period does not meet the preset condition, obtaining third verification information associated with the receiving address carried in the verification information sending request from the cache server, the verification information including the third verification information; In response to the verification information sending request, the third verification information is sent to the receiving address.

2. The verification information sending method according to claim 1, characterized in that: After associating the first verification information with the receiving address and caching the first verification information to the cache server, the method further includes: When it is detected that the storage time for which the cache server associates and stores the first verification information with the receiving address reaches a preset time, the cache server is instructed to delete the first verification information.

3. The verification information sending method according to claim 1, characterized in that: The acquiring, from a cache server, first verification information associated with a receiving address carried in the verification information sending request when determining that the user equipment passes human-machine verification, comprises: When it is determined that the user equipment passes human-machine authentication, detecting whether there is first authentication information stored in association with the receiving address carried in the authentication information sending request in the cache server; When it is determined that the first verification information exists in the cache server, the first verification information is obtained from the cache server.

4. The verification information sending method according to claim 3, characterized in that: When determining that the user equipment passes the human-machine authentication, after detecting whether there is first authentication information stored in association with the receiving address carried in the authentication information sending request in the cache server, the method further includes: When it is determined that the first verification information does not exist in the cache server, second verification information is generated in response to the verification information sending request, and the second verification information is sent to the receiving address, where the verification information includes the second verification information.

5. The verification information sending method according to claim 1, characterized in that: After receiving the human-machine verification information sent by the user equipment in response to the human-machine verification request, and determining whether the user equipment passes the human-machine verification according to the human-machine verification information, the method further includes: When it is determined that the user equipment has not passed the human-machine authentication, the authentication information is refused to be sent to the receiving address.

6. A verification information sending device, characterized in that: The device comprises: A first sending module is used to receive a verification information sending request from a target IP address, and detect whether the number of times the verification information sending request is received within a historical time period meets a preset condition; A second sending module, configured to send a human-machine verification request to a user device corresponding to the target IP address when it is determined that the number of times the verification information sending request is received within a historical time period meets the preset condition; A third sending module is used to receive the human-machine verification information sent by the user equipment in response to the human-machine verification request, and determine whether the user equipment passes the human-machine verification according to the human-machine verification information; a fourth sending module, configured to send the verification information to a receiving address carried in the verification information sending request in response to the verification information sending request when it is determined that the user equipment passes the human-machine verification, wherein the verification information is used to verify the identity of the user and / or equipment associated with the receiving address; Wherein, the fourth sending module includes: A first human-machine verification unit, configured to obtain, when determining that the user equipment passes the human-machine verification, first verification information associated with the receiving address carried in the verification information sending request from a cache server, wherein the verification information includes the first verification information; A second human-machine verification unit, configured to send the first verification information to the receiving address in response to the verification information sending request; Wherein, the verification information sending device further includes: A fifth sending module, configured to send the first verification information to the receiving address in response to a historical verification information sending request from the target IP address to send the verification information to the receiving address; a sixth sending module, configured to associate the first verification information with the receiving address and cache the information to the cache server; Wherein, the verification information sending device further includes: an eighth sending module, configured to obtain, when it is determined that the number of times the verification information sending request is received within a historical time period does not meet a preset condition, third verification information associated with a receiving address carried in the verification information sending request from a cache server, wherein the verification information includes the third verification information; A ninth sending module is configured to send the third verification information to the receiving address in response to the verification information sending request.

7. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps as claimed in any one of claims 1 to 5.

8. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 5.

Images