Skip to content

Anti-Blocking & Proxy Guard

Protected targets often check IP reputation, TLS fingerprints, browser fingerprints, request pacing, geolocation, resource loading patterns, and interaction timing. ScrapeNest exposes those controls through worker tiers, Proxy Guard, and Stealth jobs.

Proxy Routing

Proxy Guard routes jobs through managed residential and datacenter pools.

  • Rotation: distribute requests across proxy exits instead of reusing one IP for every job.
  • Geotargeting: originate requests from target markets such as US, FR, DE, or JP.
  • Session stickiness: keep all requests in one browser job on the same exit IP.
  • Custom egress: pass a proxy object when you want to route through your own infrastructure.

Fingerprint Management

ScrapeNest employs different levels of fingerprinting based on your selected Worker Tier.

TLS & HTTP Impersonation (Light Tier)

light jobs use TLS and HTTP settings that look like modern browser traffic instead of a default server-side HTTP client.

Browser Fingerprinting (Standard Tier)

standard jobs run in a browser context and can control viewport, locale, timezone, headers, resource loading, and interactions.

Hardened Stealth Engine (Stealth Tier)

stealth jobs add deeper anti-detection controls for targets that block standard automation:

  • OS profile selection with os_name: windows, macos, or linux.
  • Hardened browser fingerprint surfaces including Canvas, WebGL, AudioContext, and WebRTC.
  • Managed proxy pool integration with session stickiness.
  • Optional helper extensions such as ublock and isdcac.
  • Resource-blocking options to reduce noisy third-party scripts.

Tuning for Higher Success Rates

  1. Start with the cheapest tier that works: light for direct responses, standard for rendering, stealth for protected targets.
  2. Match the visitor profile: align os_name, locale, timezone_id, viewport, and geolocation.
  3. Use waits and actions: set wait_until, add explicit wait actions, scroll lazy-loaded pages, and click overlays when needed.
  4. Reduce noise: block images, media, fonts, or stylesheets when they are not required for the output.
  5. Pace per target: use rate limits, job concurrency, and idempotency tokens for large crawls.
  6. Inspect diagnostics: enable metadata, HAR, console logs, and screenshots when tuning a difficult target.

See also