Web Scraping CoreElite tier

F5 Shape: The Fingerprint Is in the Request

Sibling vendors stamp cookies and ray IDs on the way out. F5 Shape Security (Bot Defense) expects your client to send telemetry — HTTP headers or POST body fields minted after JS runs — and it attaches policy to endpoints and methods, not “the whole hostname.” Retail symptom: homepage 200s; one XHR or login POST returns transformed junk. Do not “detect Shape” via TS*, BIGipServer*, or reese84.

JSWritten by Jordan Smith·Reviewed by Sarah Chen·Last verified September 4, 2026
12 min read
Editorial board showing F5 Shape scoring a request fingerprint rather than IP reputation alone.

Key takeaways

  • Artifact location: request telemetry (headers/POST body), not a stable branded response cookie documented by F5.
  • Operators configure a Telemetry Header Prefix; mobile identifier header names are also per-app — not one global constant.
  • Mitigations include continue (monitor/flag), block, redirect, transform, and on some connectors drop — content scraping interstitial tooling is an Advanced-tier capability.
  • GET(Document) can serve a transparent interstitial once per user session; GET(XHR/Fetch) protection applies to XHR from instrumented pages, not raw address-bar GETs.
  • Asymmetry is the practical tell: document routes healthy, specific methods/paths degraded.
  • Lookalikes: TS* (BIG-IP ASM), BIGipServer* (LTM persistence), MRH* / F5_* (APM), reese84 (Imperva Distil-lineage), x-acf-sensor-data (Akamai mobile) — none prove Shape.

On this page

Which defense layers are scoring your request

1

Connector / edge

Bot Defense rides XC, BIG-IP, CloudFront, Cloudflare, Commerce Cloud, Adobe Commerce, or custom connectors — tech detectors often stop at the CDN.

2

JS instrumentation

Script injection points (after head/title/before script) enable telemetry collection on configured routes.

3

Telemetry attach

Single-use header sets or POST body telemetry on protected requests; replays are invalid by design on mobile guidance.

4

Endpoint policy

Methods include GET(Document), GET(XHR/Fetch), POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE — scoped per path.

5

Mitigation

Continue/flag vs block/redirect/transform/(drop). Transform yields “successful” HTTP with useless payloads.

6

IP reputation

Residential helps ASN/velocity only; missing telemetry is not fixed by rotation.

Retail pipeline from browse to payment with harder scoring on cart and checkout paths.
The same pool can browse and still fail on cart if Shape scores the path.

How to implement this with residential proxies

  1. 1

    Map asymmetry before naming the vendor

    Hit the document URL and the failing XHR/POST with the same client. Shape-class deployments often protect methods differently — a 200 homepage never falsifies Bot Defense on /api/availability.

  2. 2

    Eliminate lookalike cookies

    TS + hex → BIG-IP ASM (length varied by version). BIGipServer* → LTM persistence. MRHSession/F5_ST family → APM. reese84 → Imperva Distil-lineage cookie name, not Shape. x-acf-sensor-data → Akamai mobile sensor. None of these equal Bot Defense.

  3. 3

    Three-way curl on the failing method

    Plain, Chrome-UA, residential — against the protected endpoint, not only /. Expect missing telemetry to look similar across exits when Transform/Block ignores IP.

    bash
    EP='https://TARGET/api/availability'
    UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36'
    PX='http://aethyn-XXXXX-country-us-isp-comcast:PASSWORD@proxy.aethyn.io:5499'
    for label in plain ua res; do
      echo "=== $label ==="
      case $label in
        plain) curl -sS -D - -o /tmp/sh.body "$EP" ;;
        ua) curl -sS -D - -o /tmp/sh.body "$EP" -A "$UA" ;;
        res) curl -sS -D - -o /tmp/sh.body "$EP" -A "$UA" -x "$PX" ;;
      esac | grep -iE 'HTTP/|set-cookie:|content-type|x-volterra-location'
      python - <<'PY'
    from pathlib import Path
    b=Path('/tmp/sh.body').read_bytes()
    print('bytes', len(b), 'head', b[:120])
    PY
    done
  4. 4

    Read F5-documented behaviours, not unverified blog claims

    Prefer primary facts: telemetry in headers or POST body; Telemetry Header Prefix as a console field; interstitial on GET(Document) transparent to users and typically once per session; ISTL as an F5 scraping-endpoint configuration name without a confirmed expansion. Avoid publishing single-capture body strings as universal fingerprints.

  5. 5

    Remediate honestly

    If residential changes the failing endpoint, keep ISP targeting. If not, you need an instrumented browser path that can attach telemetry under your compliance rules — still not a CAPTCHA-solving guide.

What goes wrong when this scraper fails

Retail collectors scrape the PDP fine, then availability or add-to-cart calls return opaque JS or empty data with 200. Wappalyzer shows Cloudflare or BigIP and the team chases the wrong product. Shape-class failures are silent in response space and loud in endpoint asymmetry.

Why this failure mode happens

F5 documents that Bot Defense collects browser telemetry and attaches it on protected requests, often after an interstitial on GET(Document). Continue/flag mode can let traffic pass while logging — collectors look healthy until mitigation flips. Because telemetry is client-generated, curl without the JS path never participates correctly, and rotating IPs cannot mint tokens.

Form cards separating ASN-shaped blocks from request-fingerprint blocks.
Use residential when the tell is ASN. Keep a browser stack when the tell is the request.

How Aethyn residential proxies help here

Use ISP-targeted Elite sticky sessions when retail bots are scored per carrier, and keep three-way proof that IP is actually implicated before scaling concurrency.

  • Elite HTTP 5499 + ISP suffixes for carrier-sensitive retail
  • Sticky lifetimes for session-carrying browser flows
  • Premium 2099 for asymmetry surveys
  • SOCKS5 3499 for Playwright
  • Explicit non-claim: proxy ≠ Shape telemetry

Common questions about this scraper problem

How do I detect F5 Shape from a response?
Often you cannot via a stable branded cookie. Infer from endpoint/method asymmetry, connector context, and absence of other vendors’ markers after lookalike elimination. Optional x-volterra-location only proves an F5 XC regional edge, not Bot Defense.
Where does the Shape fingerprint live?
In client-generated telemetry attached to protected requests (headers or POST body), after JS instrumentation — not in a classic Set-Cookie brand.
Are BIGipServer or TS cookies Shape?
No. They belong to other F5 BIG-IP products (LTM persistence / ASM). Separate them cleanly.
Does rotating residential proxies bypass Shape?
No for telemetry/interstitial layers. Yes possibly for IP-weighted scoring when three-way tests show a flip.
Aethyn ports for retail asymmetry tests?
Elite HTTP 5499 with country/ISP suffixes; Premium 2099 for cheap probes; SOCKS5 1099/3499 as needed.
CAPTCHA or step-up solving?
Out of scope. F5 marketing mentions step-up controls on some deployments — this page stays diagnostic.

Best practices that keep scrapers reliable

  • Test the failing method, not the marketing homepage
  • Disqualify BIG-IP/Imperva/Akamai lookalikes
  • Prefer F5 primary docs over detector regex blogs
  • Assume Continue/flag can precede hard mitigation
  • Public-data collection only

Common mistakes that burn proxy budget

  • TS* ⇒ Shape
  • reese84 ⇒ Shape
  • Homepage-only probes
  • Infinite IP rotation on transform 200s
  • Inventing global telemetry header names
Share this article

Solve this with Aethyn residential proxies

Route your first request through rotating residential IPs in minutes, with transparent per-byte pricing.

All solutions