Internet-based proxy security services

1. A method in a proxy server, 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, wherein the request is received at the proxy server as a result of a DNS (Domain Name System) request for the domain returning an IP address of the proxy server instead of an IP address of the origin server,

determining, through analyzing the request, that a visitor belonging to the request poses a threat, and responsive to this determination performing the following:

blocking the request,

customizing a block page based on one or more of: a set of one or more characteristics associated with the identified resource and a set of one or more characteristics associated with the request, and

transmitting the block page to the client device that indicates that the request has been blocked.

2. The method of claim 1 , wherein analyzing the request to determine whether the visitor poses a threat includes determining whether an IP address of the request is included on one or more of: a global restricted IP address list that identifies IP addresses that are not allowed to access content of any of a plurality of origin servers, and a local IP restricted address list that identifies IP addresses that are not allowed to access content of the origin server.

3. The method of claim 1 , wherein the visitor is determined to pose a threat as a result of determining, based on a set of one or more characteristics associated with the request, that the client device potentially has a software vulnerability, and wherein the block page indicates that the client device potentially has the software vulnerability.

4. The method of claim 3 , further comprising:

including, as part of the block page, instructions to remedy the software vulnerability including one or more of: run an anti-virus software program on the client device, download and run an anti-virus software program on the client device, download and install one or more patches on the client device, and upgrade software on the client device.

5. The method of claim 3 , further comprising:

including, as part of the block page, one or more advertisements for one or more solution providers that offer one or more products to remedy the software vulnerability.

6. The method of claim 1 , wherein the visitor is determined to pose a threat as a result of determining, based on a set of one or more characteristics associated with the request, that the visitor is potentially an automated bot that is part of a botnet.

7. The method of claim 6 , further comprising:

including, as part of the block page, a mechanism to dismiss the block page, wherein the mechanism is selected from the group consisting of: a link to close the block page, a CAPTCHA, and a dismiss code field.

8. The method of claim 7 , further comprising:

determining that the visitor has successfully dismissed the block page;

reconstructing the request; and

transmitting the request to the origin server.

9. The method of claim 1 , 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.

10. The method of claim 1 , wherein customizing the block page further comprises:

determining a threat level associated with the visitor belonging to the request; and

modifying the block page to include a mechanism to dismiss the block page when the threat level is below a threshold value.

11. A proxy server, comprising:

a memory to store instructions;

a processor coupled with the memory to process the stored instructions to:

receive, from a client device, a request to perform an action on an identified resource that is hosted at an origin server for a domain, wherein the request is received at the proxy server as a result of a DNS (Domain Name System) request for the domain returning an IP address of the proxy server instead of an IP address of the origin server,

determine, through analyzing the request, that a visitor belonging to the request poses a threat, and responsive to this determination perform the following:

block the request, and

customize a block page based on one or more of: a set of one or more characteristics associated with the identified resource and a set of one or more characteristics associated with the request, and

transmit the block page to the client device that indicates that the request has been blocked.

12. The proxy server of claim 11 , wherein analyzing the request to determine whether the visitor poses a threat includes a determination of whether an IP address of the request is included on one or more of: a global restricted IP address list that identifies IP addresses that are not allowed to access content of any of a plurality of origin servers, and a local IP restricted address list that identifies IP addresses that are not allowed to access content of the origin server.

13. The proxy server of claim 11 , wherein the visitor is determined to pose a threat as a result of determining, based on a set of one or more characteristics associated with the request, that the client device potentially has a software vulnerability, and wherein the block page indicates that the client device potentially has the software vulnerability.

14. The proxy server of claim 13 , wherein the processor is further to process the stored instructions to:

include, as part of the block page, instructions to remedy the software vulnerability including one or more of: run an anti-virus software program on the client device, download and run an anti-virus software program on the client device, download and install one or more patches on the client device, and upgrade software on the client device.

15. The proxy server of claim 13 , wherein the processor is further to process the stored instructions to:

include, as part of the block page, one or more advertisements for one or more solution providers that offer one or more products to remedy the software vulnerability.

16. The proxy server of claim 11 , wherein the visitor is determined to pose a threat as a result of a determination, based on a set of one or more characteristics associated with the request, that the visitor is potentially an automated bot that is part of a botnet.

17. The proxy server of claim 16 , wherein the processor is further to process the stored instructions to:

include, as part of the block page, a mechanism to dismiss the block page, wherein the mechanism is selected from the group consisting of: a link to close the block page, a CAPTCHA, and a dismiss code field.

18. The proxy server of claim 17 , wherein the processor is further to process the stored instructions to:

determine that the visitor has successfully dismissed the block page;

reconstruct the request; and

transmit the request to the origin server.

19. The proxy server of claim 11 , 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.

20. The proxy server of claim 11 , wherein customizing the block page further comprises:

determining a threat level associated with the visitor belonging to the request; and

modifying the block page to include a mechanism to dismiss the block page when the threat level is below a threshold value.

21. A non-transitory machine-readable storage medium that provides instructions that, when executed by a processor, 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, wherein the request is received at a proxy server as a result of a DNS (Domain Name System) request for the domain returning an IP address of the proxy server instead of an IP address of the origin server,

determining, through analyzing the request, that a visitor belonging to the request poses a threat, and responsive to this determination performing the following:

blocking the request, and

customizing a block page based on one or more of: a set of one or more characteristics associated with the identified resource and a set of one or more characteristics associated with the request, and

transmitting the block page to the client device that indicates that the request has been blocked.

22. The non-transitory machine-readable storage medium of claim 21 , wherein analyzing the request to determine whether the visitor poses a threat includes determining whether an IP address of the request is included on one or more of: a global restricted IP address list that identifies IP addresses that are not allowed to access content of any of a plurality of origin servers, and a local IP restricted address list that identifies IP addresses that are not allowed to access content of the origin server.

23. The non-transitory machine-readable storage medium of claim 21 , wherein the visitor is determined to pose a threat as a result of determining, based on a set of one or more characteristics associated with the request, that the client device potentially has a software vulnerability, and wherein the block page indicates that the client device potentially has the software vulnerability.

24. The non-transitory machine-readable storage medium of claim 23 , further comprising:

including, as part of the block page, instructions to remedy the software vulnerability including one or more of: run an anti-virus software program on the client device, download and run an anti-virus software program on the client device, download and install one or more patches on the client device, and upgrade software on the client device.

25. The non-transitory machine-readable storage medium of claim 23 , further comprising:

including, as part of the block page, one or more advertisements for one or more solution providers that offer one or more products to remedy the software vulnerability.

26. The non-transitory machine-readable storage medium of claim 21 , wherein the visitor is determined to pose a threat as a result of determining, based on a set of one or more characteristics associated with the request, that the visitor is potentially an automated bot that is part of a botnet.

27. The non-transitory machine-readable storage medium of claim 26 , further comprising:

including, as part of the block page, a mechanism to dismiss the block page, wherein the mechanism is selected from the group consisting of: a link to close the block page, a CAPTCHA, and a dismiss code field.

28. The non-transitory machine-readable storage medium of claim 27 , further comprising:

determining that the visitor has successfully dismissed the block page;

reconstructing the request; and

transmitting the request to the origin server.

29. The non-transitory machine-readable storage medium of claim 21 , 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.

30. The non-transitory machine-readable storage medium of claim 21 , wherein customizing the block page further causes said processor to perform operations comprising:

determining a threat level associated with the visitor belonging to the request; and

modifying the block page to include a mechanism to dismiss the block page when the threat level is below a threshold value.