Landing page detection method and device, computer device and storage medium

Abstract

The application relates to the technical field of Internet advertisement, and discloses a landing page detection method and device, computer equipment and a storage medium. The landing page detection method obtains a web page address of a target landing page through timing; if it is determined that the target landing page has not been redirected according to the web page address, proxy address information and proxy browser information are obtained through a preset proxy distribution tool; the web page address of the target landing page is accessed and screenshot through the proxy address information and the proxy browser information, and a screenshot image of the target landing page is obtained; if it is determined that there is no image difference between the record image and the screenshot image of the target landing page, it is determined that the detection result of the target landing page is normal. The application can realize comprehensive detection from web page address analysis to landing page image comparison, accurately identify redirection risks based on web page address analysis, and perform image comparison on the basis of multi-region and multi-browser access screenshots, so that the comprehensiveness and detection effect of landing page detection are improved.

Description

Technical Field

[0001] This invention relates to the field of internet advertising technology, and in particular to a landing page detection method, apparatus, computer equipment, and storage medium. Background Technology

[0002] Internet advertising utilizes a Demand-Side Platform (DSP) delivery model. DSPs serve advertisers, helping them place ad landing pages online. Ad landing pages require approval before being displayed. Some advertisers, after approval, illegally modify the content of their landing pages, resulting in discrepancies between the actually displayed version and the approved version. To ensure the legality and compliance of ad landing pages, they need to be reviewed and approved.

[0003] Currently, there are two main methods for detecting ad landing pages: detection at the page content level and detection at the page code level. However, both methods still have some drawbacks. Detection at the page content level involves using automated screenshot comparison tools to perform programmatic, periodic checks on the ad landing page content. This method can only detect direct modifications to the ad landing page content. If the ad landing page has regional blocking, it may result in the inability to take screenshots or inconsistencies in screenshots taken by visitors from different regions, thus failing to detect the actual ad landing page. Detection at the page code level involves comparing and analyzing the differences in page code parameters. However, if the ad landing page contains intermediate page redirects, the detection can be bypassed by tampering with the redirect links, posing a potential risk.

[0004] Therefore, existing methods for detecting advertising landing pages are not comprehensive enough, are prone to detection vulnerabilities, cannot meet diverse detection needs, and have poor detection results. Summary of the Invention

[0005] Therefore, it is necessary to provide a landing page detection method, apparatus, computer equipment, and storage medium to address the aforementioned technical problems, thereby resolving the issues of insufficient detection coverage and poor detection results in existing technologies when detecting landing pages.

[0006] A landing page detection method includes:

[0007] Retrieve the web address of the target landing page periodically;

[0008] If it is determined from the webpage address that the target landing page has not been redirected, then the proxy address information and proxy browser information are obtained through a preset proxy allocation tool;

[0009] Based on the proxy address information and the proxy browser information, a screenshot of the target landing page is taken by accessing the webpage address of the target landing page to obtain a screenshot image of the target landing page;

[0010] If it is determined that there are no image differences between the filing image of the target landing page and the screenshot image, then the detection result of the target landing page is determined to be normal.

[0011] A landing page detection device, comprising:

[0012] The webpage address acquisition module is used to periodically obtain the webpage address of the target landing page;

[0013] The proxy information acquisition module is used to acquire proxy address information and proxy browser information through a preset proxy allocation tool if it is determined from the webpage address that the target landing page has not been redirected.

[0014] The screenshot image acquisition module is used to perform an access screenshot operation on the webpage address of the target landing page based on the proxy address information and the proxy browser information, and obtain a screenshot image of the target landing page;

[0015] The screenshot image comparison module is used to determine that the detection result of the target landing page is normal if it is determined that there is no image difference between the filing image of the target landing page and the screenshot image.

[0016] A computer device includes a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor implements the above-described landing page detection method when executing the computer-readable instructions.

[0017] A computer-readable storage medium storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the landing page detection method described above.

[0018] In the aforementioned landing page detection method, apparatus, computer equipment, and storage medium, the landing page detection method periodically acquires the webpage address of the target landing page to determine whether the target landing page has been redirected, accurately detecting tampering of webpage address links and reducing the risk of malicious landing page redirection. Simultaneously, when the target landing page has not been redirected, proxy address information and proxy browser information are obtained through a preset proxy allocation tool; based on the proxy address information and proxy browser information, a screenshot of the target landing page's webpage address is taken, resulting in a screenshot image of the target landing page. This enables multi-regional and multi-browser monitoring of landing pages, avoiding the inability to effectively detect landing pages due to regional blocking. Furthermore, the registered image and the screenshot image of the target landing page are compared; if there are no image differences between the registered image and the screenshot image, the detection result of the target landing page is determined to be normal. This invention can achieve comprehensive detection from webpage address analysis to landing page image comparison, improving the comprehensiveness and effectiveness of landing page detection. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating a landing page detection method according to an embodiment of the present invention;

[0021] Figure 2 This is a schematic diagram of a landing page detection device according to an embodiment of the present invention;

[0022] Figure 3 This is a schematic diagram of a computer device according to an embodiment of the present invention. Detailed Implementation

[0023] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] In one embodiment, such as Figure 1 As shown, a landing page detection method is provided, including the following steps S10-S40:

[0025] S10. Periodically obtain the web address of the target landing page.

[0026] Understandably, the landing page detection process is triggered periodically, meaning it retrieves the web address of the target landing page at preset time intervals. The preset time interval is a fixed duration pre-set to trigger the landing page detection process. The preset time interval can have a default value or can be adjusted as needed, for example, a default value of 10 minutes. The target landing page is the landing page to be detected; there can be one or more target landing pages. Each target landing page corresponds to a unique web address, which is the URL pointing to the landing page, i.e., the Uniform Resource Locator (URL) of the landing page.

[0027] In one specific embodiment, the detection of advertising landing pages is implemented based on a headless browser. A headless browser is a browser without a graphical user interface. It can run in the background and perform web page operations and data collection through a programming interface. Headless browsers are used in scenarios such as automated testing, web page screenshotting, and web scraping. Suitable headless browsers include Chrome Headless, PhantomJS, and Puppeteer.

[0028] S20. If it is determined from the webpage address that the target landing page has not been redirected, then the proxy address information and proxy browser information are obtained through a preset proxy allocation tool.

[0029] Understandably, after obtaining the target landing page's URL, it's necessary to determine whether a redirect has occurred. Redirection is a technique that automatically redirects users or search engines to a new webpage by changing the page's URL. For advertising landing pages, some advertisers may use redirection to tamper with approved landing pages, redirecting users from the approved landing page to a new, unapproved landing page that may contain prohibited content.

[0030] When determining whether a target landing page has been redirected based on its URL, you can use status codes or the URL itself. When using status codes, you can retrieve the "Location" field from the HTTP response header of the webpage to determine if a redirection has occurred. When a website redirects, the server returns an HTTP status code "3xx" (such as 301 or 302) and includes a "Location" field in the response header, indicating the redirected URL. Alternatively, you can use code analysis. For example, you can retrieve the code data corresponding to the target landing page's URL and analyze it using a smart code analysis tool to determine if there are external links. If external links are found, the target landing page has been redirected; if not, it has not.

[0031] After confirming that the target landing page has not redirected based on the webpage address, proxy address information and proxy browser information are obtained through a pre-set proxy allocation tool. The pre-set proxy allocation tool is software pre-configured to store and allocate proxy information and provide page access proxy services. Proxy address information refers to the parameter configuration information used to characterize the page access address, such as the Internet Protocol Address (IP) address. Proxy browser information refers to the parameter configuration information used to characterize the browser type accessing the page. For advertising landing pages, the landing pages displayed may differ depending on the IP address or the browser type of the client environment. For example, users with IP addresses in Shenzhen and Beijing may generate different advertising landing pages when accessing the same webpage address. Similarly, desktop browsers and mobile browsers may generate different advertising landing pages when accessing the same webpage address, with one of these landing pages differing from the approved landing page.

[0032] S30. Based on the proxy address information and the proxy browser information, perform an access screenshot operation on the webpage address of the target landing page to obtain a screenshot image of the target landing page.

[0033] Understandably, after obtaining the proxy address information and proxy browser information, an availability access test is performed on the target landing page's webpage address using these information. If the availability access test fails, new proxy address information and proxy browser information need to be obtained again. If the availability access test succeeds, the proxy address information and proxy browser information are used to perform subsequent access screenshot operations on the target landing page's webpage address, resulting in a screenshot image of the target landing page. The screenshot image of the target landing page refers to the image obtained by taking a screenshot of the actual target landing page after access. For ease of subsequent processing, the corresponding proxy address information and proxy browser information can also be displayed on the screenshot image, such as "Beijing, WeChat client browser".

[0034] In a timed landing page detection method, when there is only one target landing page, one screenshot is generated for the same proxy address and proxy browser information. When there are multiple target landing pages, multiple screenshots are generated for the same proxy address and proxy browser information. To improve detection efficiency, screenshot tasks can be executed in parallel. For example, if the landing page detection task is triggered every 10 minutes, with each screenshot taking 10 seconds, 6 screenshots are generated per minute. Assuming a 4-minute validity period for the proxy IP address and proxy browser, 24 screenshots can be taken within that time. If there are 180 target landing pages, at least 8 sharded threads are needed to process the tasks simultaneously, and all screenshot tasks share the same proxy address and proxy browser information.

[0035] S40. If it is determined that there is no image difference between the filing image of the target landing page and the screenshot image, then the detection result of the target landing page is determined to be normal.

[0036] Understandably, after obtaining a screenshot of the target landing page, it's also necessary to retrieve the backup image of the target landing page from the backup database. The backup image and the screenshot are then compared to determine if there are any differences. The backup image refers to the image of the target landing page when it passed the review. When there are no differences between the backup image and the screenshot, it indicates that the actually accessed advertising landing page matches the approved advertising landing page, thus confirming that the target landing page's detection result is normal.

[0037] This embodiment periodically acquires the webpage address of the target landing page to determine whether redirection has occurred, accurately detecting URL tampering and reducing the risk of malicious landing page redirection. Simultaneously, when the target landing page is not redirected, a preset proxy allocation tool acquires proxy address and proxy browser information. Based on this information, a screenshot of the target landing page is taken, enabling multi-region and multi-browser monitoring of the landing page, avoiding the inability to effectively detect landing pages due to regional blocking. Furthermore, the registered image and screenshot of the target landing page are compared. If no differences exist between the two images, the detection result of the target landing page is considered normal. This embodiment achieves comprehensive detection from webpage address analysis to landing page image comparison, improving the comprehensiveness and effectiveness of landing page detection.

[0038] In one embodiment, step S10, i.e. after periodically obtaining the webpage address of the target landing page, includes:

[0039] S101. Send a code loading request to the webpage address of the target landing page, and obtain the loading address and the loading count information corresponding to the loading address after the target landing page is successfully loaded.

[0040] S102. Determine whether the webpage address and the loading address are consistent;

[0041] S103. When the webpage address and the loading address are the same, determine whether the loading count information is greater than 1;

[0042] S104. If the load count information is not greater than 1, then it is determined that the target landing page has not been redirected.

[0043] Understandably, after periodically obtaining the target landing page's URL, when determining whether the target landing page has redirected, this can be done using a status code or by using the URL before and after the redirection. When using the URL before and after method, a code loading request is sent to the target landing page's URL. After the target landing page loads successfully, the loading address and the corresponding load count information are obtained. The determination of whether a redirection has occurred is based on the loading address and load count information. The code loading request refers to the request information for loading the code of the target landing page. The loading address refers to the actual page address corresponding to the target landing page after it has finished loading. The load count information refers to the number of page loads during the loading process of the target landing page. If the target landing page has not redirected, the URL and loading address are the same, and only one load is needed to get from the URL to the loading address.

[0044] In one specific embodiment, when sending a code loading request to the target landing page's webpage address, the webpage address is recorded, denoted as `before_url = Url`. After the target landing page loads successfully, the actual page address is obtained, denoted as `after_url = CurrentUrl`, and a load count is recorded. The `Url` and `CurrentUrl` are compared for equality. If they are equal, the load count is checked to see if it is greater than 1. If the load count is not greater than 1, it is determined that the target landing page has not been redirected.

[0045] This embodiment determines whether the target landing page has been redirected by comparing the addresses before and after loading. This can accurately rule out the phenomenon of landing page tampering based on web page address masking, which helps to ensure the effectiveness of subsequent screenshot judgment.

[0046] In one embodiment, step S102, after determining whether the webpage address and the loading address are consistent, further includes:

[0047] S1021. If the webpage address and the loading address are inconsistent, it is determined that the target landing page has been redirected, and the detection result of the target landing page is determined to be abnormal.

[0048] In step S103, after determining whether the load count information is greater than 1 when the webpage address and the loading address are the same, the method further includes:

[0049] S1031. If the load count information is greater than 1, it is determined that the target landing page has been redirected, and the detection result of the target landing page is determined to be abnormal.

[0050] Understandably, when the webpage address and the loading address are inconsistent, it indicates that the target landing page has been redirected. Similarly, when the webpage address and the loading address are the same and the load count is greater than 1, it also indicates that the target landing page has been redirected. That is, for the ad landing page, the actual ad landing page accessed has been modified from the approved ad landing page. In this case, the detection result of the target landing page can be directly determined to be abnormal, without needing to obtain proxy address information and proxy browser information through a preset proxy allocation tool for subsequent landing page detection processes.

[0051] Furthermore, for ad landing pages with abnormal detection results, the ad landing pages can be directly removed from the platform, and an alert message can be sent to the advertiser of the ad landing page, reminding them to restore and rectify the ad landing page. Then, the time of occurrence and type of abnormality are recorded, an abnormality log for the target landing page is generated, and stored in the database.

[0052] This embodiment determines that the target landing page has been redirected by using the loading address and loading count information, which can effectively detect abnormal scenarios of intermediate page jumps.

[0053] In one embodiment, the preset proxy allocation tool includes an address proxy interface and a browser proxy interface; step S20, namely obtaining proxy address information and proxy browser information through the preset proxy allocation tool, includes:

[0054] S201. Determine at least one available proxy address obtained through the address proxy interface as the proxy address information for accessing the target landing page;

[0055] S202. The at least one available proxy browser identifier obtained through the browser proxy interface is determined as the proxy browser information used to access the target landing page.

[0056] Understandably, the default proxy allocation tool includes an address proxy interface and a browser proxy interface. The address proxy interface (e.g., an API interface) is used for data interaction from the proxy server's address list, while the browser proxy interface (e.g., an API interface) is used for data interaction from the proxy server's browser identifier list. Available proxy addresses refer to IP addresses on the proxy server that carry a specified geographic location and can access web pages normally. Available proxy browser identifiers refer to browser identifiers on the proxy server that carry a specified browser type and can access web pages normally.

[0057] In one specific embodiment, at least one available proxy IP address is obtained from the proxy IP address list via an address proxy interface, and this obtained available proxy IP address is used as the proxy address information for accessing the target landing page. At least one available proxy UA is obtained from the browser identifier (User-Agent, UA) list via a browser proxy interface, and this obtained available UA is used as the proxy browser information. The UA is a field (request header identifier) ​​in an HTTP request initiated by the browser. This field is used by the browser to send its version and engine information to the requested server when accessing a page, enabling the server to identify the user's browser name and version, browser rendering engine, browser language, and browser plugins, such as distinguishing whether the user is accessing the page using a desktop browser or a mobile browser. The combination of available proxy IP addresses and available UAs allows ordinary users to access the landing page using browsers from different regions and of different types.

[0058] For proxy address information and proxy browser information, you can obtain one or multiple separate pieces of information. When there is only one piece of proxy address information and one piece of proxy browser information, a single screenshot image will be obtained for the same target landing page in a single timed landing page detection method. When there are multiple pieces of proxy address information and / or proxy browser information, multiple screenshot images will be obtained for the same target landing page in a single timed landing page detection method.

[0059] This embodiment obtains available proxy addresses through the address proxy interface and available proxy browser identifiers through the browser proxy interface, providing a diverse basis for subsequent screenshot judgment. It can achieve multi-region detection based on available proxy addresses and multi-terminal detection based on available proxy browser identifiers, thus meeting diverse detection needs.

[0060] In one embodiment, step S30, namely, taking a screenshot of the target landing page's webpage address based on the proxy address information and the proxy browser information to obtain a screenshot image of the target landing page, includes:

[0061] S301. Obtain a first available proxy address and a second available proxy address through the address proxy interface, and obtain an available proxy browser identifier through the browser proxy interface;

[0062] S302. Based on the first available proxy address and the available proxy browser identifier, perform an access screenshot operation on the webpage address of the target landing page to obtain the first screenshot image of the target landing page;

[0063] S303. Based on the second available proxy address and the available proxy browser identifier, perform an access screenshot operation on the webpage address of the target landing page to obtain a second screenshot image of the target landing page;

[0064] S304. Compare the first screenshot image and the second screenshot image to determine whether there are image differences between the first screenshot image and the second screenshot image;

[0065] S305. If there is no image difference between the first screenshot image and the second screenshot image, then either the first screenshot image or the second screenshot image is determined as the screenshot image of the target landing page.

[0066] Understandably, some advertisers use technical means to circumvent detection by having IP addresses from different regions and different types of browsers access different landing pages. This results in the landing page showing inappropriate information but still appearing normal in the detection results, a phenomenon known as region-based or browser-based blocking. When taking screenshots of the target landing page based on proxy address and proxy browser information, one can use a combination of one available proxy address and one available proxy browser identifier to access the target landing page and take a screenshot, or one can use two or more available proxy addresses and one available proxy browser identifier to access the target landing page and take a screenshot, ultimately obtaining a screenshot of the target landing page.

[0067] In one specific embodiment, a screenshot of the target landing page is obtained by accessing the target landing page using a combination of two available proxy addresses corresponding to a single available proxy browser identifier. First, two different available proxy addresses, designated as a first available proxy address and a second available proxy address, are obtained through an address proxy interface, and a unique available proxy browser identifier is obtained through a browser proxy interface. Then, the webpage address of the target landing page is accessed and screenshotted using the combination of the first and second available proxy addresses and their corresponding available proxy browser identifiers, respectively, resulting in a first screenshot image and a second screenshot image of the target landing page. The first screenshot image corresponds to the first available proxy address, and the second screenshot image corresponds to the second available proxy address. Next, the first and second screenshot images are compared to determine if there are any image differences between them. Finally, if there are no image differences between the first and second screenshot images, it indicates that the page content accessed by users from different regions is consistent, therefore either the first or second screenshot image is selected as the screenshot image of the target landing page.

[0068] In this embodiment, the combination of the first available proxy address and the available proxy browser identifier corresponding to the second available proxy address is used to take screenshots of the web page address of the target landing page, resulting in a first screenshot image and a second screenshot image of the target landing page. By comparing the first screenshot image and the second screenshot image, the phenomenon of regional blocking can be effectively eliminated, and the effectiveness of landing page detection can be improved.

[0069] In one embodiment, step S304, after determining whether there is an image difference between the first screenshot image and the second screenshot image, further includes:

[0070] S3041. If there is an image difference between the first screenshot image and the second screenshot image, then it is determined that the detection result of the target landing page is abnormal.

[0071] Understandably, in the process of determining whether there are image differences between the first screenshot and the second screenshot, if there are image differences between the first screenshot and the second screenshot, it indicates that the page content when users from different regions access the target landing page is inconsistent, and there may be a regional blocking phenomenon. Therefore, it is directly determined that the detection result of the target landing page is abnormal.

[0072] In this embodiment, when there are image differences between the first screenshot image and the second screenshot image, the detection result of the target landing page is directly determined to be abnormal, without the need for subsequent image comparison process, which is conducive to rapid anomaly detection and improves detection efficiency.

[0073] In one embodiment, step S30, after obtaining a screenshot of the target landing page, includes:

[0074] S306. Obtain the filing image of the target landing page, and obtain the filing size information of the filing image and the screenshot size information of the screenshot image, and compare whether the filing size information and the screenshot size information are consistent;

[0075] S307. If the filing size information and the screenshot size information are consistent, then the filing image and the screenshot image are compared using a preset pixel analysis model to obtain the pixel difference value.

[0076] S308. When the pixel difference value reaches a preset difference threshold, it is determined that there is an image difference between the filing image and the screenshot image;

[0077] S309. When the pixel difference value has not reached the preset difference threshold, it is determined that there is no image difference between the filing image and the screenshot image.

[0078] Understandably, after obtaining a screenshot of the target landing page, the corresponding image (or "registration image") is acquired, and then the registration image and screenshot are compared to see if they match. First, a size comparison is performed, checking if the registration image size information and screenshot size information are consistent. Registration image size information refers to the data used to characterize the size of the registration image. Screenshot image size information refers to the data used to characterize the size of the screenshot image. Then, when the size dimensions are consistent, a pixel-level comparison is performed. That is, when the registration image size information and screenshot image size information are consistent, a preset pixel analysis model is used to perform pixel comparison processing on the registration image and screenshot image to obtain pixel difference values. The preset pixel analysis model is a pre-trained neural network model used to compare pixels between different images. The input to the preset pixel analysis model is two images, and the output is the pixel difference value, which is the ratio of the number of differing pixels between the two images to the total number of pixels. Conversely, when the size dimensions are inconsistent, there is no need to perform a pixel-level comparison; the detection result of the target landing page is directly determined to be abnormal. Finally, it is determined whether the pixel difference value reaches a preset difference threshold. The preset difference threshold is the maximum critical value used to determine whether the pixel difference value makes two images significantly different. For example, the default value for the preset difference threshold can be set to 5%. If the pixel difference value reaches the preset difference threshold, it is determined that there is an image difference between the registered image and the screenshot image, thus determining that the detection result of the target landing page is abnormal. If the pixel difference value has not yet reached the preset difference threshold, it is determined that there is no image difference between the registered image and the screenshot image, thus determining that the detection result of the target landing page is normal.

[0079] This embodiment compares the registered image and the screenshot image from both size and pixel dimensions, which can accurately determine whether there are image differences between the registered image and the screenshot image, thus improving the comprehensiveness and accuracy of landing page detection.

[0080] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0081] In one embodiment, a landing page detection device is provided, which corresponds one-to-one with the landing page detection method in the above embodiments. For example... Figure 2 As shown, the landing page detection device includes a webpage address acquisition module 10, a proxy information acquisition module 20, a screenshot image acquisition module 30, and a screenshot image comparison module 40. Detailed descriptions of each functional module are as follows:

[0082] The webpage address acquisition module 10 is used to periodically acquire the webpage address of the target landing page;

[0083] The proxy information acquisition module 20 is used to acquire proxy address information and proxy browser information through a preset proxy allocation tool if it is determined from the web page address that the target landing page has not been redirected.

[0084] The screenshot image acquisition module 30 is used to perform an access screenshot operation on the webpage address of the target landing page according to the proxy address information and the proxy browser information, and obtain a screenshot image of the target landing page;

[0085] The screenshot image comparison module 40 is used to determine that the detection result of the target landing page is normal if it is determined that there is no image difference between the filing image of the target landing page and the screenshot image.

[0086] In one embodiment, the webpage address acquisition module 10 includes:

[0087] The loading information acquisition unit is used to send a code loading request to the webpage address of the target landing page, and to acquire the loading address and the loading count information corresponding to the loading address after the target landing page is successfully loaded.

[0088] The address consistency judgment unit is used to determine whether the webpage address and the loading address are consistent.

[0089] A load count determination unit is used to determine whether the load count information is greater than 1 when the webpage address and the load address are the same;

[0090] A no-redirection determination unit is used to determine that the target landing page has not been redirected if the load count information is not greater than 1.

[0091] In one embodiment, the webpage address acquisition module 10 further includes:

[0092] The first detection result abnormality unit is used to determine that the target landing page has been redirected if the web page address and the loading address are inconsistent, and to determine that the detection result of the target landing page is abnormal.

[0093] The second detection result abnormality unit is used to determine that the target landing page has been redirected and to determine that the detection result of the target landing page is abnormal if the load count information is greater than 1.

[0094] In one embodiment, the agent information acquisition module 20 includes:

[0095] The proxy address information determination unit is used to determine at least one available proxy address obtained through the address proxy interface as proxy address information for accessing the target landing page;

[0096] The proxy browser information determination unit is used to determine at least one available proxy browser identifier obtained through the browser proxy interface as proxy browser information for accessing the target landing page.

[0097] In one embodiment, the screenshot image acquisition module 30 includes:

[0098] The proxy information acquisition unit is used to obtain a first available proxy address and a second available proxy address through the address proxy interface, and to obtain an available proxy browser identifier through the browser proxy interface.

[0099] The first screenshot image acquisition unit is used to perform an access screenshot operation on the webpage address of the target landing page according to the first available proxy address and the available proxy browser identifier, so as to obtain the first screenshot image of the target landing page;

[0100] The second screenshot image acquisition unit is used to perform an access screenshot operation on the webpage address of the target landing page according to the second available proxy address and the available proxy browser identifier, so as to obtain a second screenshot image of the target landing page;

[0101] The comparison processing unit is used to compare the first screenshot image and the second screenshot image to determine whether there is an image difference between the first screenshot image and the second screenshot image;

[0102] The screenshot image determination unit is used to determine either the first screenshot image or the second screenshot image as the screenshot image of the target landing page if there is no image difference between the first screenshot image and the second screenshot image.

[0103] In one embodiment, the screenshot image acquisition module 30 further includes:

[0104] The third detection result anomaly unit is used to determine that the detection result of the target landing page is abnormal if there is an image difference between the first screenshot image and the second screenshot image.

[0105] In one embodiment, the screenshot image acquisition module 30 further includes:

[0106] The size information comparison unit is used to obtain the filing image of the target landing page, and obtain the filing size information of the filing image and the screenshot size information of the screenshot image, and compare whether the filing size information and the screenshot size information are consistent;

[0107] A pixel comparison processing unit is used to perform pixel comparison processing on the filing image and the screenshot image through a preset pixel analysis model if the filing size information and the screenshot size information are consistent, so as to obtain the pixel difference value.

[0108] The image difference determination unit is used to determine that there is an image difference between the filing image and the screenshot image when the pixel difference value reaches a preset difference threshold;

[0109] The image difference determination unit is used to determine that there is no image difference between the filing image and the screenshot image when the pixel difference value has not reached a preset difference threshold.

[0110] Specific limitations regarding the landing page detection device can be found in the limitations of the landing page detection method described above, and will not be repeated here. Each module in the aforementioned landing page detection device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0111] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes a readable storage medium and internal memory. The readable storage medium stores an operating system, computer-readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the readable storage medium. The database stores data related to the landing page detection method. The network interface communicates with external terminals via a network connection. When the computer-readable instructions are executed by the processor, a landing page detection method is implemented. The readable storage medium provided in this embodiment includes both non-volatile and volatile readable storage media.

[0112] In one embodiment, a computer device is provided, including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor performs the following steps when executing the computer-readable instructions:

[0113] Retrieve the web address of the target landing page periodically;

[0114] If it is determined from the webpage address that the target landing page has not been redirected, then the proxy address information and proxy browser information are obtained through a preset proxy allocation tool;

[0115] Based on the proxy address information and the proxy browser information, a screenshot of the target landing page is taken by accessing the webpage address of the target landing page to obtain a screenshot image of the target landing page;

[0116] If it is determined that there are no image differences between the filing image of the target landing page and the screenshot image, then the detection result of the target landing page is determined to be normal.

[0117] In one embodiment, one or more computer-readable storage media storing computer-readable instructions are provided. The readable storage media provided in this embodiment include non-volatile readable storage media and volatile readable storage media. The readable storage media stores computer-readable instructions, which, when executed by one or more processors, perform the following steps:

[0118] Retrieve the web address of the target landing page periodically;

[0119] If it is determined from the webpage address that the target landing page has not been redirected, then the proxy address information and proxy browser information are obtained through a preset proxy allocation tool;

[0120] Based on the proxy address information and the proxy browser information, a screenshot of the target landing page is taken by accessing the webpage address of the target landing page to obtain a screenshot image of the target landing page;

[0121] If it is determined that there are no image differences between the filing image of the target landing page and the screenshot image, then the detection result of the target landing page is determined to be normal.

[0122] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware through computer-readable instructions. These computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When executed, these computer-readable instructions can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0123] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0124] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A landing page detection method, characterized in that, include: Retrieve the web address of the target landing page periodically; If it is determined from the webpage address that the target landing page has not been redirected, then the proxy address information and proxy browser information are obtained through a preset proxy allocation tool; Based on the proxy address information and the proxy browser information, a screenshot of the target landing page is taken by accessing the webpage address of the target landing page to obtain a screenshot image of the target landing page; If it is determined that there is no image difference between the filing image of the target landing page and the screenshot image, then the detection result of the target landing page is determined to be normal; The preset proxy allocation tool includes an address proxy interface and a browser proxy interface; The step of obtaining proxy address information and proxy browser information through a preset proxy allocation tool includes: At least one available proxy address obtained through the address proxy interface is determined as the proxy address information for accessing the target landing page. The available proxy address refers to the IP address in the proxy server that carries a specified regional attribute and can access the webpage normally. At least one available proxy browser identifier obtained through the browser proxy interface is determined as the proxy browser information used to access the target landing page. The available proxy browser identifier refers to the browser identifier in the proxy server that carries a specified browser type attribute and can access the webpage normally.

2. The landing page detection method as described in claim 1, characterized in that, After periodically obtaining the web address of the target landing page, the process includes: Send a code loading request to the webpage address of the target landing page, and obtain the loading address and the loading count information corresponding to the loading address after the target landing page is successfully loaded; Determine whether the webpage address and the loading address are consistent; When the webpage address and the loading address are the same, determine whether the loading count information is greater than 1; If the load count is not greater than 1, it is determined that the target landing page has not been redirected.

3. The landing page detection method as described in claim 2, characterized in that, After determining whether the webpage address and the loading address are consistent, the method further includes: If the webpage address and the loading address are inconsistent, it is determined that the target landing page has been redirected, and the detection result of the target landing page is determined to be abnormal. After determining whether the load count information is greater than 1 when the webpage address and the loading address are the same, the method further includes: If the load count information is greater than 1, it is determined that the target landing page has been redirected, and the detection result of the target landing page is determined to be abnormal.

4. The landing page detection method as described in claim 1, characterized in that, The step of taking a screenshot of the target landing page based on the proxy address information and the proxy browser information to obtain a screenshot image of the target landing page includes: The first available proxy address and the second available proxy address are obtained through the address proxy interface, and an available proxy browser identifier is obtained through the browser proxy interface. Based on the first available proxy address and the available proxy browser identifier, a screenshot operation is performed on the webpage address of the target landing page to obtain the first screenshot image of the target landing page; Based on the second available proxy address and the available proxy browser identifier, a screenshot operation is performed on the webpage address of the target landing page to obtain a second screenshot image of the target landing page; The first screenshot image and the second screenshot image are compared to determine whether there are any image differences between them. If there is no difference between the first screenshot image and the second screenshot image, then either the first screenshot image or the second screenshot image is determined as the screenshot image of the target landing page.

5. The landing page detection method as described in claim 4, characterized in that, After determining whether there are image differences between the first screenshot image and the second screenshot image, the method further includes: If there are image differences between the first screenshot image and the second screenshot image, then the detection result of the target landing page is determined to be abnormal.

6. The landing page detection method as described in claim 1, characterized in that, After obtaining a screenshot of the target landing page, the process includes: Obtain the filing image of the target landing page, and obtain the filing size information of the filing image and the screenshot size information of the screenshot image, and compare whether the filing size information and the screenshot size information are consistent; If the filing size information and the screenshot size information are consistent, then the filing image and the screenshot image are compared using a preset pixel analysis model to obtain the pixel difference value; When the pixel difference value reaches a preset difference threshold, it is determined that there is an image difference between the filing image and the screenshot image; If the pixel difference value has not reached the preset difference threshold, it is determined that there is no image difference between the filing image and the screenshot image.

7. A landing page detection device, characterized in that, include: The webpage address acquisition module is used to periodically obtain the webpage address of the target landing page; The proxy information acquisition module is used to acquire proxy address information and proxy browser information through a preset proxy allocation tool if it is determined from the webpage address that the target landing page has not been redirected. The screenshot image acquisition module is used to perform an access screenshot operation on the webpage address of the target landing page based on the proxy address information and the proxy browser information, and obtain a screenshot image of the target landing page; The screenshot image comparison module is used to determine that the detection result of the target landing page is normal if it is determined that there is no image difference between the filing image of the target landing page and the screenshot image. The preset proxy allocation tool includes an address proxy interface and a browser proxy interface, and the proxy information acquisition module includes: The proxy address information determination unit is used to determine at least one available proxy address obtained through the address proxy interface as proxy address information for accessing the target landing page. The available proxy address refers to the IP address in the proxy server that carries a specified regional attribute and can access the webpage normally. The proxy browser information determination unit is used to determine at least one available proxy browser identifier obtained through the browser proxy interface as proxy browser information for accessing the target landing page. The available proxy browser identifier refers to a browser identifier in the proxy server that carries a specified browser type attribute and can access the webpage normally.

8. A computer device comprising a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, characterized in that, When the processor executes the computer-readable instructions, it implements the landing page detection method as described in any one of claims 1 to 6.

9. A computer-readable storage medium storing computer-readable instructions, characterized in that, When the computer-readable instructions are executed by one or more processors, the one or more processors cause the landing page detection method as described in any one of claims 1 to 6 to be performed.

Images