Whether you're just starting to build a web scraper from scratch and wondering what you're doing wrong because your solution isn't working, or you've already been working with crawlers for a while and are stuck on a page that gives you an error saying you're a bot, you can't go any further, keep reading.
Anti-bot solutions have evolved in recent years. More and more websites are introducing security measures: from simple ones, such as filtering IP addresses according to their geolocation, to advanced ones based on in-depth analysis of browser parameters and behavioral analysis. All this makes web scraping content more difficult and costly than a few years ago. Nevertheless, it is still possible. Here I highlight a few tips that you may find helpful.
Below you can find list of curated services that I used to get around different anti-bot protections. Depending on your use-case you may need one of the following:
| Scenario/use-case | Solution | Example |
|---|---|---|
| Short-lived sessions without auth | Pool of rotating IP addresses | That comes handy when you scrape websites like Amazon, Walmart or public LinkedIn pages. That is any website where no sign-in is required. You plan to make a high number of short-lived sessions and can afford being blocked every now and then. |
| Geographically restricted websites | Region-specific pool of IP addresses | This is useful when the website uses a firewall similar to the one from Cloudflare to block entire geography from accessing it. |
| Long-lived sessions after sign-in | Repeatable pool of IP addresses and stable set of browser fingerprints | The most common scenario here is social media automation e.g. you build a tool to automate social media accounts to manage ads more efficiently. |
| Javascript-based detection | Use of popular evasion libraries, similar to puppeteer-extra-plugin-stealth | There is a number of websites utilizing FingerprintJS that can be easily bypassed when you employ open-source plugins such as the aforementioned puppeteer stealth plugin to work with your existing software. |
| Detection with browser fingerprinting techniques | Natural looking browser fingerprints. That is, having covered the whole surface that is being validated by the installed Javascript solution on the target website. | These are one of the most advanced cases. Mainstream examples are credit card processors such as Adyen or Stripe. A very sophisticated browser fingerprint is being created to detect credit fraud, or prompt additional authorization from the user. |
| Unique set of detection techniques | Specialized bot software that targets the unique detection surface of the target website. | Good examples are sneakers marketplace websites and e-commerce shops, reportedly being under heavy attack from custom made bot software. |
| Simple custom-made detection techniques | Before diving into any of the above, if you are targeting a smaller website, it is very likely that all you need is a Scrapy script with tweaks, a cheap data-center proxy, and you are good to go. | - |
Once you have decided on what type of evasion is going to be needed in your project, you can use the list below to pick the best provider for your project:
| Type | Service | Note |
|---|---|---|
| Proxy |
BrightData (formerly Luminati Networks)
|
One of the most reliable, stable and recommended proxy provider. Best to begin there and if it turns out to be too pricey, move to cheaper alternatives. |
Global Peer to Business Proxy Network - infatica.io
|
An alternative to BrightData that is three times cheaper, but however do mind their terms of use. | |
Oxylabs
|
Competitor to BrightData with very similar pricing model. Rumor has it that they have a better TCP fingerprinting masking mechanism in place. | |
| Scraping as a service |
ScrapingBee
|
One of the most advanced stealthy scraping as a service. At times it may be cheaper than building a dedicated scraping solution - they do not charge for the amount of traffic used. |
Apify.com
|
Handy when your project is about one-off scraping. Their data understanding algorithm makes extracting data a breeze. | |
| De-captcha as a service |
Anti Captcha: Captcha Solving Service. Bypass reCAPTCHA, FunCaptcha (...)
|
Self-explanatory. Bitcoin accepted ❤️. |
This is a non-exhaustive list of companies that provide the most advanced anti-bot solutions for businesses ranging from smaller e-commerce sites to Fortune 500 companies:
- Akamai Bot Manager by Akamai
- Advanced Bot Protection by Imperva (former Distil Networks)
- DataDome Bot Protection
- PerimeterX
- Shape Security
- Cloudflare Bot Management
- Barracuda Advanced Bot Protection
- HUMAN
- Kaskada
- Alibaba Cloud Anti-Bot Service
- Travatar
Join extra.community. There runs an automated tester Botty McBotface that uses several complicated techniques to determine what exact protection a tested website uses (credits to berstend and others from #insiders).
Important You use this software at your own risk. Some of them contain malwares just fyi. I do not recommend using them.
| Stealth Browser | Puppeteer | Selenium | Evasions | SDK/Tooling | Origin |
|---|---|---|---|---|---|
| GoLogin | ✔️ | ✔️ | 🤮 | 👍 | 🇺🇸 + 🇷🇺 |
| Incogniton | ✔️ | ✔️ | 🤮 | ✔️ | ❓ |
| ClonBrowser | ✔️ | ✔️ | 🤮 | ✔️ | ❓ |
| MultiLogin | ✔️ | ✔️ | 🤮 | ✔️ | 🇪🇪 + 🇷🇺 |
| Indigo Browser | ✔️ | ✔️ | 🤮 | ✔️ | ❓ |
| GhostBrowser | ❌ | ❌ | ❌ | 👍 | ❓ |
| Kameleo | ✔️ | ✔️ | 🤮 | ✔️ | ❓ |
| AntBrowser | ❌ | ❌ | ❌ | ❌ | 🇷🇺 |
| CheBrowser | ❌ | ❌ | 🤮/✔️ | 👍 | 🇷🇺 |
Legend: 🤮 - Evasion based on noise. ❌ - No. ✔️ - Acceptable (with support libraries or not). 👍 - Very nice.
A ⭐ on this repo will be appreciated!
Here I study various aspects of evasion techniques used to get around bot detection systems used by major online websites. I cover both technical and non-technical matters, including recommendations, references to scientific papers and more.
The technical findings that I am sharing below are based on observations of running web scraping scripts for a few months against websites protected by the major anti-bot solution vendors.
I constantly add stuff to this section. Over time I will try to make it look&feel more structured.
- Cap FPS for Chromium with software rendering --use-gl=swiftshader - Limit CPU usage from SwiftShader by redraw freq. of Chromium in AVD
- Unlike some public comments on that matter chrome devtools protocol actually works on AVD-s with puppeteer
- Abusing GPU cache to create persistent tracking identifiers
✔️ Win / ❌ Fail / 🤷 Tie :
- ✔️ Client Hints - Shipped recently. In line with Chromium cpp implementation.
- ✔️ General
navigatorandwindowproperties - ✔️ Chrome plugins and native extensions - This includes both Widevine DRM extension, as well as Google Hangouts, safe-browsing etc.
- 🤷 p0f - detect host OS from TCP struct - Not possible to fix via Puppeteer APIs. Used in Akamai Bot Manager to match against JS and browser headers (Client Hints and
User-Agent). There is a detailed explaination of the issue. The most reliable evasion seems to be not spoofing host OS at all, or using OSfooler-ng. - 🤷 Browser dimensions - Although stealth plugin provides
window.outerdimensionsevasion, it won't work without correct config on non-default OS in headless mode; almost always fails whenviewport size >= screen resolution(low screen resolution display on the host). - ❌ core-estimator - This can detect mismatch between navigator.hardwareConcurrency and SW/WW execution profile. Not possible to limit/bump the
ServiceWorker/WebWorkerthread limit via existng Puppeteer APIs. - ❌ WebGL extensions profiling - desc. tbd
- ❌ RTCPeerConnection when behind a proxy - Applies to both SOCKS and HTTP(S) proxies.
- ❌ Performance.now - desc. tbd (red pill)
- ❌ WebGL profiling - desc. tbd
- ❌ Behavior Detection - desc. tbd (events, params, ML+AI buzz)
- ❌ Font fingerprinting - desc. tbd (list+version+renderer via HTML&canvas)
- ❌ Network Latency - desc. tbd (integrity check: proxy det., JS networkinfo, dns resolv profiling&timing)
- ❌ Battery API - desc. tbd
- ❌ Gyroscope and other (mostly mobile) device sensors - desc. tbd
Multilogin, Kameleo and others 💰🤠
- ❌ General
navigatorandwindowproperties - As per Multilogin documentation custom browser builds typically lag behind the latest additions added by browser vendors. In this case modified Chromium M7X is used (almost 10 versions behind when writing this). - 🤷 Font masking - Font fingerprinting still leaks host OS due to use of different font rendering backends on Win/Lin/Mac. However, the basic "font whitelisting" technique can help to slightly rotate browser fingerprint.
- ❌ Inconsistencies - Profile misconfiguration leads to early property/behavior inconsitency detection.
- ❌ Native extensions - Unlike
puppeteer-extra-plugin-stealthcustom Chromium builds such as ML and Kameleo provide at most an override for native plugins and extensions shipped with Google Chrome. - ❌ AudioContext APIs and WebGL property override - Manipulation of original canvas and audio waveform can be detected with custom JS.
- ✔️ Audio and GL noise
tbd (if you have an active subscription in any of these services and don't mind sharing an account drop me an email ❤️)
These websites may be useful to test fingerprinting techniques against a web scraping software
| Test page | Notes |
|---|---|
| https://pixelscan.net/ | Not 100% realiable as it often displays "inconsistent" to Chrome after a new update, but worth checking as the author adds new interesting detection features every now and then |
| https://browserleaks.com/ | Doesn't need introduction 😉 |
| https://f.vision/ | Good quality test page from some 🇷🇺 guys |
| https://www.ipqualityscore.com/ip-reputation-check | Commercial service with free reputation check against popular blacklists |
| https://antcpt.com/eng/information/demo-form/recaptcha-3-test-score.html | ReCaptcha score as well as some interesting notes on how to optimize captcha solving costs |
| https://ja3er.com/ | SSL/TLS fingerprint |
| https://fingerprintjs.com/demo/ | Good for basic tests - from people who believe and claim can create unique fingerprints "99.5%" of the time |
| https://coveryourtracks.eff.org/ | - |
| https://www.deviceinfo.me/ | - |
| https://amiunique.org/ | - |
| http://uniquemachine.org/ | - |
| http://dnscookie.com/ | - |
| https://whatleaks.com/ | - |
| https://kitchensink.ssl.fun/vendor/shape/fp | - |
I need to make a general remark to people who are evaluating (and/or) planning to introduce anti-bot software on their websites. Anti-bot software is nonsense. Its snake oil sold to people without technical knowledge for heavy bucks.
Blocking bot traffic is based on the premise that you (or your technology provider) can distinguish bots from real users. To make this happen various privacy-invasive techniques are applied. To date none of them has been proved to be successful against specialized web scraping tools. Anti-bot software is all about reducing cheap bot traffic. It makes the process of scraping more expensive and complicated, but does not make it entirely impossible.
Anti-bot software vendors use detection techniques that fall into one of these two categories:
No specialized web scraping software is used. Vendor can detect the bad traffic based on information openly disclosed by the scraper e.g. User-Agent header, connection parameters etc.
As a result only bots that are not targeted to scrape specific website are blocked. This will make most of the managers happy, because the overall number of bad traffic goes down and it may almost look like there is no more bot traffic on the website. Wrong.
More advanced web scrapers make use of residential proxies and implement complex evasion techniques to fool anti-bot software to think that the web scraper is a real user. No detection mechanism exists to get around this due to technical limitation of web browsers.
In this case, most of the time the vendor will be only able to cluster the bad traffic by finding patterns in bot traffic and behavior. This is where browser fingerprinting comes into play. The problem with banning the traffic here is that it may turn out to be a risky operation when bots are successfully mimicking real users. There is a chance that by blocking bots the website will become unavailable to real visitors.
If you think this is a way to go google "captcha resolve api".
If you have problems with scraping specific website, write me a short email at [email protected]. Let's have a quick tête-à-tête consultation via Skype 😊.
Have I mentioned a ⭐ would be appreciated? :-)
➡️ Ethereum address 0x380a4b41fB5e0e1EB8c616eBD56f62f8F934Bab6