Global CDN Network

FAST
DELIVERY

Static assets, media files and API responses — cached at the edge, served in milliseconds.

12
Edge nodes
99.9%
Uptime SLA
<18ms
Avg latency
TLS 1.3
Encryption
// 01
Edge Caching
Content is stored at nodes closest to the user. TTL is configurable per path pattern.
// 02
HTTP/3 + QUIC
All endpoints support HTTP/3 with QUIC transport for reduced handshake latency.
// 03
Cache Purge API
Invalidate single assets or entire path prefixes via REST API with immediate propagation.
// 04
Origin Shield
A single shield node absorbs all cache misses before traffic reaches your origin server.
// 05
Access Control
Token-based URL signing with expiry and IP allowlisting at the edge level.
// 06
Analytics
Per-asset bandwidth, hit ratio, and geographic distribution — updated every 60 seconds.
All systems operational
Services
Edge nodes
12 / 12 online
Cache layer
4 ms
Origin shield
11 ms
Purge API
operational
TLS termination
operational
Analytics pipeline
~60 s delay
Edge nodes — latency
Frankfurt (DE)
— ms
Amsterdam (NL)
— ms
Warsaw (PL)
— ms
Paris (FR)
— ms
New York (US)
— ms
Singapore (SG)
— ms
90-day uptime
Documentation

Quickstart

Point your static assets to cdn.dfctnet.org. No registration required for public files — just prefix your asset path with the CDN base URL.

# Base URL
https://cdn.dfctnet.org/{bucket}/{path}

# Example
https://cdn.dfctnet.org/assets/images/logo.svg

Files are cached on first request and distributed to edge nodes automatically. Default TTL is 86400 seconds (24 hours).

# HTML usage
<img src="https://cdn.dfctnet.org/assets/logo.svg">

# CSS
background-image: url('https://cdn.dfctnet.org/assets/bg.webp');

Asset URLs

URL structure follows a bucket / path pattern. Buckets map to origin directories configured in your account settings.

https://cdn.dfctnet.org/{bucket}/{version}/{filename}

# Versioned asset (cache-busting via path)
https://cdn.dfctnet.org/app/v2.4.1/bundle.js

# With query string (ignored by cache key by default)
https://cdn.dfctnet.org/assets/font.woff2?v=3

Query strings are stripped from cache keys by default. To include them, set x-cache-qs: true in your origin response headers.

Cache Purge API

Invalidate cached assets immediately. Purge propagates to all edge nodes within ~5 seconds.

POST /api/purge

# Purge single file
curl -X POST https://cdn.dfctnet.org/api/purge \
  -H "Authorization: Bearer <token>" \
  -d '{"path": "/assets/logo.svg"}'
# Purge by prefix (wildcard)
curl -X POST https://cdn.dfctnet.org/api/purge \
  -H "Authorization: Bearer <token>" \
  -d '{"prefix": "/assets/images/"}'

Response Headers

Every CDN response includes diagnostic headers to help debug caching behaviour.

x-cache: HIT | MISS | STALE
x-cache-node: fra-01
x-cache-age: 3721 # seconds since cached
x-cache-ttl: 82679 # seconds remaining
x-origin-time: 43 # ms, only on MISS
vary: Accept-Encoding

To override TTL per response, set Cache-Control: max-age=N on your origin. The CDN respects s-maxage over max-age when both are present.