Exit node benchmark feature

1. A computer implemented method of examining and collecting qualitative information about an exit node comprising:

receiving, by the exit node, a benchmark request, wherein the exit node is connected to a network, wherein the benchmark request is produced by a service provider infrastructure based on benchmark test definitions;

connecting, by the exit node, to a target via the network, wherein the exit node upon connecting to the target, forwards the benchmark request to the target;

receiving, by the exit node, a response to the benchmark request from the target, wherein the exit node, upon receiving the response, forwards the response to a service provider infrastructure, and wherein the service provider infrastructure categorizes the exit node based on the response to the benchmark request.

2. The method of claim 1 further comprising:

receiving, by the exit node, a data scraping request from the service provider infrastructure, wherein the service provider infrastructure formulates the data scraping request based on a client's request received from a client device;

implementing, by the exit node, the data scraping request, wherein the exit node upon implementing the data request obtains data from the target via the network;

forwarding, by the exit node, the data obtained from the target to the service provider infrastructure via the network, wherein the service provider infrastructure collects the qualitative information of the exit node.

3. The method of claim 2 , wherein qualitative information about the exit node indicates the service quality of the exit node in servicing the data scraping request.

4. The method of claim 2 , wherein the exit node is admitted for suitable use by the service provider infrastructure, when the data forwarded by the exit node is speedy enough when compared to thresholds configured by the service provider infrastructure and comprises appropriate HTTP response codes.

5. The method of claim 2 , wherein the exit node is acknowledged for benchmark testing by the service provider infrastructure when the data forwarded by the exit node is not speedy enough when compared to thresholds configured by the service provider infrastructure and does not comprise appropriate HTTP response codes.

6. The method of claim 1 , wherein the exit node receives the benchmark request during an initial registration with the service provider infrastructure or when exhibiting performance inadequacy corresponding to thresholds configured by the service provider infrastructure.

7. The method of claim 1 , wherein the benchmark test definitions are configuration files described locally at the service provider infrastructure.

8. The method of claim 1 , wherein the benchmark test definitions comprise at least one or a combination of: geo-location of the target, network placement, country affiliation, communication protocol type and characteristics deemed to be relevant by the service provider infrastructure.

9. The method of claim 1 , wherein the response to the benchmark is evaluated by the service provider infrastructure.

10. The method of claim 1 , wherein the service provider infrastructure evaluates at least one or a combination of:

reception of the response to the benchmark request;

availability of the exit node;

ability of the exit node to reach the target.

11. The method of claim 10 , wherein the service provider infrastructure evaluates if the reception of the response to the benchmark request is speedy enough when compared to thresholds configured by the service provider infrastructure to use the exit node.

12. The method of claim 1 , wherein information on the exit node is sent to a database by the service provider infrastructure.

13. The method of claim 1 , where the exit node is grouped according to at least one of these categories within the database: a) availability of the exit node; b) ability of the exit node to reach the target.

14. A non-transitory computer readable medium for examining and collecting qualitative information about an exit node comprising instructions which, when executed by a computing device within a service provider infrastructure, cause the computer readable medium to:

receive a benchmark request produced by a service provider infrastructure based on benchmark test definitions;

connect to a target and forward the benchmark request to the target;

receive a response to the benchmark request from the target;

forward the response to the service provider infrastructure and wherein the service provider infrastructure categorizes the exit node based on the response to the benchmark request;

receive a data scraping request formulated by the service provider infrastructure based on a client's request received from a client device;

implement the data request and obtain data from the target;

forward the data obtained from the target to the service provider infrastructure, wherein the service provider infrastructure collects qualitative information about the exit node.

15. The non-transitory computer readable medium of claim 14 , wherein the benchmark request is received by the exit node.

16. The non-transitory computer readable medium of claim 14 , wherein the exit node connects to the target and forwards the benchmark request to the target.

17. The non-transitory computer readable medium of claim 14 , wherein the exit node receives the response to the benchmark request from the target.

18. The non-transitory computer readable medium of claim 14 , wherein the qualitative information about the exit node indicates the service quality of the exit node in servicing the data scraping request.

19. The non-transitory computer readable medium of claim 14 , wherein the benchmark test definitions comprise at least one or a combination of: geo-location of the target, network placement, country affiliation, communication protocol type and characteristics deemed to be relevant by the service provider infrastructure.