Validating visitor internet-based security threats
A validating server receives from a client device a first request that does not include a cookie for a validating domain that resolves to the validating sever. The first request is received at the validating server as a result of a proxy server redirecting the client device to the validating domain upon a determination that a visitor belonging to the client device is a potential threat based on an IP (Internet Protocol) address assigned to the client device used for a second request to perform an action on an identified resource hosted on an origin server for an origin domain. The validating server sets a cookie for the client device, determines a set of characteristics associated with the first client device, and transmits the cookie and a block page to the client device that has been customized based on the set of characteristics, the block page indicating that the second request has been blocked.
1. A method in a proxy server for validating visitor Internet-based security threats, comprising
receiving, from a client device, a request to perform an action on an identified resource that is hosted at an origin server for a domain as a result of a DNS (Domain Name System) request for the domain resolving to the proxy server, wherein the origin server is one of a plurality of origin servers that belong to different domains that resolve to the proxy server and are owned by different entities, and wherein the proxy server and the plurality of origin servers are owned by different entities;
determining, based on an IP (Internet Protocol) address assigned to the client device and associated with the request, that a visitor belonging to the client device is a potential threat; and
causing a validating domain server to determine whether the visitor is a threat based on a cookie associated with the visitor for a validating domain, the causing including transmitting a response to the client device that includes a redirection to the validating domain that resolves to the validating domain server.
2. The method of claim 1 , wherein determining that the visitor is a potential threat includes determining that the IP address assigned to the client device is included in an IP restricted list.
3. The method of claim 1 , wherein the response includes a script that when executed by a client network application of the client device causes a request for a resource to be generated and issued to the validating domain.
4. A non-transitory machine-readable storage medium that provides instructions that, when executed by a processor of a proxy server, cause said processor to perform operations comprising:
receiving, from a client device, a request to perform an action on an identified resource that is hosted at an origin server for a domain as a result of a DNS (Domain Name System) request for the domain resolving to the proxy server, wherein the origin server is one of a plurality of origin servers that belong to different domains that resolve to the proxy server and are owned by different entities, and wherein the proxy server and the plurality of origin servers are owned by different entities;
determining, based on an IP (Internet Protocol) address assigned to the client device and associated with the request, that a visitor belonging to the client device is a potential threat; and
causing a validating domain server to determine whether the visitor is a threat based on a cookie associated with the visitor for a validating domain, the causing including transmitting a response to the client device that includes a redirection to the validating domain that resolves to the validating domain server.
5. The non-transitory machine-readable storage medium of claim 4 , wherein determining that the visitor is a potential threat includes determining that the IP address assigned to the client device is included in an IP restricted list.
6. The non-transitory machine-readable storage medium of claim 4 , wherein the response includes a script that when executed by a client network application of the client device causes a request for a resource to be generated and issued to the validating domain.