Moz installed incapsula. Its a firewall that is basically blocking legitimate requests from lots of users and lots of tools.
You can mail moz about being blocked and ask them to whitelist you. If you so happen to get the right person on support they will whitelist you, but if you get the wrong person they will give you a copy and paste response saying that they don't whitelist people and blaming whatever tool you tell them you use as being the issue.
If you tell them you use scrapebox they will say its because of scrapebox not coinciding with their TOU. If you tell them your using netpeak, which is completely inside their TOU they will give you some other reason.
I can't blame them, they are trying to make a buck and no doubt after PR was shut down they have gotten a huge influx of free use. They already lowered their max requests from 1 million per month to 25K.
Generally their support seems to prefer to "pass the buck" rather then "fix the problem". In their defense the people answering the support tickets probably don't have the ability to actually fix the long term problem, its below their pay grade.
But its a game of cat and mouse, you might get whitelisted you might not. Random requests dont get thru the firewall while a byte for byte duplicate of the same request can randomly get thru. They have done multiple rounds of this, this is the 3rd round and I think has lasted the longest or nearly. Perhaps they have manually filtered out enough good traffic they feel they can just offer a free service and arbitrarily ban most of the traffic they get from it. Hard to say for sure where they still stop or what the end game is.
Right now though they are blocking all sorts of tools and web tool and even if you make a request from something like firefox, using their API, they typically just block it.
They also often say they created a php script and tested your api and all is fine, but no doubt they are testing it from a ip that is already whitelisted which makes it a mute point.
You can mail moz about being blocked and ask them to whitelist you. If you so happen to get the right person on support they will whitelist you, but if you get the wrong person they will give you a copy and paste response saying that they don't whitelist people and blaming whatever tool you tell them you use as being the issue.
If you tell them you use scrapebox they will say its because of scrapebox not coinciding with their TOU. If you tell them your using netpeak, which is completely inside their TOU they will give you some other reason.
I can't blame them, they are trying to make a buck and no doubt after PR was shut down they have gotten a huge influx of free use. They already lowered their max requests from 1 million per month to 25K.
Generally their support seems to prefer to "pass the buck" rather then "fix the problem". In their defense the people answering the support tickets probably don't have the ability to actually fix the long term problem, its below their pay grade.
But its a game of cat and mouse, you might get whitelisted you might not. Random requests dont get thru the firewall while a byte for byte duplicate of the same request can randomly get thru. They have done multiple rounds of this, this is the 3rd round and I think has lasted the longest or nearly. Perhaps they have manually filtered out enough good traffic they feel they can just offer a free service and arbitrarily ban most of the traffic they get from it. Hard to say for sure where they still stop or what the end game is.
Right now though they are blocking all sorts of tools and web tool and even if you make a request from something like firefox, using their API, they typically just block it.
They also often say they created a php script and tested your api and all is fine, but no doubt they are testing it from a ip that is already whitelisted which makes it a mute point.