# Vendor facets — bunny.net. CDN, Bunny Shield bot detection with verified-bot categories for
# AI scrapers and AI tools, and Deno-based Edge Scripting. Delivery and filtering only: no maps.
vendor: bunny-net
name: bunny.net
website: https://bunny.net
areas:
- cdn
registry_keys: []
rubric_schema_version: 0.22.0
generated: '2026-09-25'
features_refreshed: '2026-09-25'
basis: capability
summary: >-
  bunny.net moves no Kin Score check. Bunny Shield recognises and verifies AI scrapers and user-triggered
  AI tools by reverse DNS and published IP ranges, not Web Bot Auth, and lets a zone allow or block them.
  That is enforcement, not a published consent signal. Edge Scripting can host APIs and middleware, but
  whatever it serves is the provider's own work. No detector in the vendors registry keys on bunny.net,
  so a customer cohort cannot be measured.
features:
- id: shield-verified-bots
  name: Bunny Shield verified bots
  description: >-
    Verifies crawlers and AI agents by rDNS and published IP ranges into categories (AI Scraper, AI Tool,
    SEO and more) and allows or blocks them per Shield zone.
  source: https://bunny.net/docs/shield/verified-bots
  tier: paid
- id: edge-scripting
  name: Bunny Edge Scripting
  description: JavaScript/TypeScript (Deno) serverless code at 119 edge locations for APIs and CDN middleware.
  source: https://bunny.net/edge-scripting/
  tier: paid
maps: []
earns_nothing:
- feature: shield-verified-bots
  check: consent_identity
  layer: agent_readiness
  why: Allowing or blocking AI bots publishes no AIPREF/ContentSignal/WebBotAuth artifact.
- feature: edge-scripting
  check: well_known_published
  layer: composite
  why: >-
    A script can serve a well-known file, but the credit goes to the file the provider writes. Any host
    could serve it.
out_of_reach:
  checks:
  - consent_identity
  - agentic_commerce
  - well_known_published
  - llms_txt_published
  - mcp_server
  - contract_present
  note: No managed agent-facing artifact is shipped on the fetched pages.
surface:
  agent_readiness:
    reachable: 0
    total: 139
hard_rule: >-
  A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes
  the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership
  can.
method: searched
source:
- https://bunny.net/docs/shield/verified-bots
- https://bunny.net/edge-scripting/
measured:
  cohort:
    method: vendors-catalog.json detections (CNAME / header / URL shape / markup), never a name match
    detected: 0
    in_baseline: 0
  control:
    basis: providers earning contract_present + documentation_present + api_reference_present, minus the
      cohort
    n: 5216
  metric: >-
    cohort_pct / control_pct = mean share of the check's points earned (derived and platform credit weighted),
    x100
  measured_on: '2026-09-25'
  status: 'not measurable: 0 detected customers clear the baseline (need 20)'
simulation:
  simulated_on: '2026-09-25'
  rubric: 0.23.0
  population: providers publishing a contract (contract_present earned), replayable exactly
  providers: 8977
  providers_unreplayable: 987
  providers_moved: 0
  conditional_rows: excluded (they depend on what the API already does)
  composite_lift:
    median: 0.0
    p75: 0.0
    p90: 0.0
    max: 0.0
    mean_among_movers: 0.0
  agent_readiness_lift:
    median: 0.0
    p75: 0.0
    p90: 0.0
    max: 0.0
    mean_among_movers: 0.0
  facet_lift_median_among_movers: {}
  composite_band_moves: {}
  agent_readiness_band_moves: {}
  method: >-
    each provider's own kin/checks file, the vendor's maps at their stated credit, the scorer's composite
    formula; from -> to, nothing written