Bunny CDN & bunny.net Developer Platform

Bunny CDN and the wider bunny.net platform: Storage, Stream, Optimizer, Shield, DNS, Edge Scripting, Database and Magic Containers.

Updated 8 September 2026

What a Bunny CDN pull zone does

A pull zone connects a content source to Bunny’s delivery network. Visitors request a URL on the delivery hostname, and eligible content can be reused from cache. A site can apply this arrangement to an asset subdomain instead of moving its main application.

For example, a tutorial site might serve its HTML from a CMS while placing screenshots and downloadable files on a separate CDN hostname. The page and its images then have different delivery paths, which is why inspecting only the homepage does not describe the whole site.

Cache variants and file updates

Bunny documents cache variation controls for cases where a request can have more than one valid response. The cache must distinguish the variants that matter to the application. Otherwise, reusing an object can produce the wrong representation even when the network is functioning.

For a file release, use a deliberate naming and update strategy. Publishing manual-v2.pdf as a new asset is a different operation from replacing the contents of manual.pdf. The latter requires accounting for copies already held in caches.

The broader bunny.net platform

Bunny CDN is one product within bunny.net. Storage supplies an origin for files, Stream handles video delivery, and Optimizer processes images. DNS manages domain records and Shield supplies security controls. These services can be combined, but a CDN pull zone does not imply that every asset is stored in Bunny Storage.

Developer tools: Edge Scripting, Database and containers

Edge Scripting runs application logic at the edge. Bunny Database provides SQLite-compatible databases, while Magic Containers deploys containerized workloads. This makes bunny.net a developer platform as well as an asset delivery provider. For example, a media application could combine a custom backend with Stream, using the CDN to distribute the resulting content.

Checking an asset delivery setup

Test the actual asset URLs and their response headers. Bunny exposes point-of-presence information that helps identify the responding edge location. A fast HTML response says little about a large image fetched from a different hostname.

Verify fonts, cross-origin requests and download links after changing asset URLs. An origin file can exist and still fail in a browser because its public URL or response policy no longer matches what the page expects.

How DNSTrace.dev detects Bunny CDN

Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.

cdn-pullzone — The numeric identifier of the pull zone serving the request.
cdn-requestid — Per-request identifier.
cdn-cache — Cache outcome at the Bunny edge.
server: BunnyCDN — The Bunny edge software.
CNAME targets under b-cdn.net — The standard Bunny mapping.

What a detection proves

The asset was delivered through a Bunny pull zone.

What it does not prove

The origin the pull zone fetches from, which is configured privately and not exposed in the response.

Common questions about Bunny CDN

Can Bunny CDN serve only a website’s images?

Yes. A site can reference assets on a Bunny pull-zone hostname while its HTML and application routes are served elsewhere. Delivery should be checked for the individual hostname or resource in question.

Why does only part of a site show Bunny headers?

Pull zones are commonly attached to an asset subdomain, so the main document can be served by a different platform entirely.

Cloud, AI and edge platform