What is Imperva and how to bypass it when web scraping?

Imperva is a popular anti-bot protection service, extensively used across various websites to prevent unauthorized automated access.

While automated access controls primarily target security threats, Web Application Firewalls (WAF) systems like Imperva, block and hinder web scraping bots as well.

This guide overviews Imperva's anti-bot technology with focus on legitimate bypass methods for efficient web scraping.

What is Imperva WAF?

Imperva offers a Web Application Firewall (WAF) service that acts as a formidable barrier between a website and its users, enhancing security.

This critical middleware layer scrutinizes incoming traffic, differentiating between automated bot activities and genuine human interactions.

example Imperva Incapsula block page encountered in web scraping
example Imperva block page as seen on gamestop.com

Even though most web scraping bots are benign, their automated nature means they often get ensnared by Imperva’s intricate anti-bot mechanisms.

How to bypass Imperva?

The Imperva bypass when web scraping involves many different techniques and resources that are already implemented by most web scraping APIs.

Here are the best web scraping APIs for Imperva anti-bot protected targets:

Service Success % Speed Cost $/1000 πŸ”—
1
96%
+2
20.1s
+0.8
$2.11
-0.61
2
96%
-3
38.0s
+6.5
$12.0
=
3
12%
-25
4.4s
+0.3
$2.76
=
4
1%
-1
0.9s
-0.2
$2.2
=
5
0%
-
-
6
0%
-
-
7
0%
-
-
Data range Dec 13 - Dec 20

Job listing pages on Indeed.com

more on indeed.com

However, to bypass Imperva WAF manually the web scraper needs to be fortified with several key features that resist Imperva identification methods. To implement that we need to take a deep look at how Imperva works.

Join the Scrapeway newsletter!

Early benchmark reports and industry insights every week!

How does the Imperva anti-bot works?

Imperva inspects each incoming connection and generates a trust score which is used as a filter to determine the likelihood of the connection coming from a real human being.

To generate this score Imperva is using various fingerprinting and data point metrics. Let's take a quick look at some.

IP Address

The first metric is the IP address of the connecting client and each client has one.

There's a limited amount of IPs on the internet and they each have distinct features that let Imperva to assign probabilities to them.

πŸ—ΊοΈπŸ—ΊοΈπŸ—ΊοΈ

For example, a user connecting from a home internet connection is significantly less likely to be a robot than a user connecting from a data center.

With this IP's are separated into several categories:

  • Datacenter - assigned to all data centers like AWS, Google Cloud hosts and so on.
  • Residential - assigned to all home connections.
  • Mobile - assigned to mobile cell towers, satellites and so on.

To combat IP Address analysis, scrapers should high-quality use residential or mobile proxies that haven't been identified by Imperva yet.

Javascript fingerprinting and challenges

The second metric is the client's ability to execute Javascript. As most bots don't execute javascript an easy way to identify them is to serve a javascript challenge.

These challenges are often simple mathematical puzzles that use tokens distributed at other parts of the website. Reverse engineering this behavior can be tricky without using a real web browser.

To solve javascript challenges scrapers need to use real web browsers through headless browser automation. Most commonly through libraries like Puppeteer, Playwright or Selenium.

πŸ‘£πŸ‘£πŸ‘£

Headless browsers can be identified through javascript fingerprinting techniques as they are just slightly different from user browsers in many different ways. Tiny details add up to a full evaluation profile which can be used to identify robots very successfully.

To combat fingerprinting, headless browsers need to be patched with fingerprint resistance and randomization.

HTTP fingerprinting and analysis

Real-user web browsers browse and connect in a few different ways that can be used to identify robot connections.

Most robots still use HTTP1.1 connections which are not sure by real browsers at all in 2024. Meaning, scrapers should use newer versions of the HTTP2 or HTTP3 protocol.

πŸ”ŽπŸ”ŽπŸ”Ž

While advanced HTTP clients like libcurl support HTTP2 pretty well they are susceptible to HTTP2 fingerprinting. This type of fingerprinting measures slight differences between the HTTP2 implementation of the client and the real browser.

Another fingerprinting technique related to HTTP is TLS fingerprinting. In this type of fingerprint, the TLS handshake is analyzed for slight differences between the client and the real browser.

To combat HTTP and TLS fingerprinting, scrapers need to use advanced HTTP2 capable clients that are TLS and HTTP fingerprint resistant.

Behavior and technical analysis

While scrapers usually just collect data without interacting with the website, they can still be identified through their behavior.

Most commonly this is done through scraper implementation mistakes that just don't happen with real users. Some examples:

  • Forgetting custom request headers.
  • Sending requests in different formats or encodings.
  • Missing expected cookies or browser-specific headers like User-Agent.
  • Visiting pages that aren't visited by real users which are known as honey pots.

These slight irregularities are tracked by Imperva in its trust score calculation so, scrapers need to be diligent and replicate requests as close to real user behavior as possible.

πŸͺ€πŸͺ€πŸͺ€

Imperva logs every connection and use behavior and pattern analysis to identify robots. This means that scrapers that behave in an unusual pattern, connect in bursts or have any connection irregularities can be identified through AI-based analysis.

To combat behavior analysis, scrapers need to implement a human-like behavior pattern that is indistinguishable from a real user.

What are some websites that use Imperva?

Imperva is a widely adopted anti-bot and there are many popular websites encountered in web scraping that use it. Here's a quick list:

  • Realtor.com
  • Realestate.com.au
  • Target.com
  • Footlocker.com
  • Hotels.com

And many others, though, as most big targets often rotate and use multiple anti-bot technologies based on needs and performances.

Many other targets implement Imperva anti-bot protection temporarily when experiencing high traffic or bot attacks which affects web scraping as well.

Summary

Imperva employs cutting-edge fingerprinting and analysis methods to detect bots and scrapers, assigning a dynamic trust score based on web scraper capabilities and overall behavior.

As Imperva continually advances its anti-bot measures, it is crucial for web scrapers to rapidly evolve and adapt to these sophisticated defenses.

Given these ongoing developments, we highly recommend adopting a state-of-the-art, continuously maintained web scraping API service. Consult the benchmarks for the latest performance comparisons!

Newsletter

Join us for the best in web scraping and data hacking news and insights once per week! Early benchmark results, industry insights and highlights from Scrapeway :)