The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.

The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.

Date of Patent:
Jun. 13, 2023

Filed:

Feb. 08, 2022
Applicant:

Cloudflare, Inc., San Francisco, CA (US);

Inventors:

Lee Hahn Holloway, Santa Cruz, CA (US);

Matthew Browning Prince, San Francisco, CA (US);

Ian Gerald Pye, Santa Cruz, CA (US);

Matthieu Philippe François Tourne, San Francisco, CA (US);

Michelle Marie Zatlyn, San Francisco, CA (US);

Assignee:

CLOUDFLARE, INC., San Francisco, CA (US);

Attorney:
Primary Examiner:
Int. Cl.
CPC ...
G06F 21/00 (2013.01); G06F 16/958 (2019.01); G06F 16/95 (2019.01); G06F 21/55 (2013.01); H04L 9/40 (2022.01); G06Q 30/0251 (2023.01); G06Q 30/0241 (2023.01); G06Q 10/107 (2023.01); H04L 67/02 (2022.01); H04L 69/40 (2022.01); G06F 40/143 (2020.01); G06F 40/14 (2020.01); H04L 51/42 (2022.01); H04L 61/4511 (2022.01); H04L 61/5007 (2022.01); H04L 67/56 (2022.01); H04L 67/561 (2022.01); H04L 67/568 (2022.01); G06F 15/16 (2006.01); H04L 67/146 (2022.01); H04L 47/74 (2022.01); H04L 61/59 (2022.01);
U.S. Cl.
CPC ...
G06F 16/958 (2019.01); G06F 15/16 (2013.01); G06F 16/95 (2019.01); G06F 21/00 (2013.01); G06F 21/552 (2013.01); G06F 40/14 (2020.01); G06F 40/143 (2020.01); G06Q 10/107 (2013.01); G06Q 30/0241 (2013.01); G06Q 30/0251 (2013.01); G06Q 30/0277 (2013.01); H04L 47/745 (2013.01); H04L 51/42 (2022.05); H04L 61/4511 (2022.05); H04L 61/5007 (2022.05); H04L 63/0236 (2013.01); H04L 63/0245 (2013.01); H04L 63/0254 (2013.01); H04L 63/0281 (2013.01); H04L 63/083 (2013.01); H04L 63/0861 (2013.01); H04L 63/102 (2013.01); H04L 63/126 (2013.01); H04L 63/1416 (2013.01); H04L 63/1433 (2013.01); H04L 63/1441 (2013.01); H04L 63/1458 (2013.01); H04L 63/1466 (2013.01); H04L 67/02 (2013.01); H04L 67/146 (2013.01); H04L 67/56 (2022.05); H04L 67/561 (2022.05); H04L 67/568 (2022.05); H04L 69/40 (2013.01); H04L 61/59 (2022.05);
Abstract

A proxy server receives from a client network application a request for an action to be performed on an identified network resource of a domain of an origin server. The request is received at the proxy server as a result of a DNS request for the domain returning an IP address of the proxy server. The proxy server determines that the first request is indicative of being from a bot. Responsive to this determination, the proxy server transmits a block page to the client network application that includes a mechanism to allow a human user of the client network application to provide input that indicates that they are human and not a bot. If the proxy server does not receive input from the client network application through the mechanism in the block page that indicates that the first request is not from a bot, the proxy server blocks the request.


Find Patent Forward Citations

Loading…