hubCDN node

Put your domain behind hubCDN

No signup, no dashboard. Everything is configured with two DNS records.

  1. Point your domain at this node

    Add a CNAME (or ALIAS at the apex) to:

    www.your-domain.com    CNAME    cdn.hubcdn.space

    Or point A/AAAA records directly at:

    your-domain.com    A/AAAA    41.186.167.39 
    
  2. Open your domain in a browser

    Once DNS propagates, hubCDN issues a TLS certificate for your domain automatically and shows a setup page with your next step.

  3. Declare your origin in a TXT record

    Tell hubCDN where your actual server lives:

    hubcdn.v1.origin.your-domain.com    TXT    "https://origin.your-server.com"

    That's it. Traffic now flows through this node with caching and automatic certificate renewal.

Optional: tune caching with one more TXT record

hubcdn.v1.config.your-domain.com    TXT    "cache=aggressive; ttl=6h; websocket=on"
KeyValuesDefault
cacheoff · standard · aggressivestandard
ttlduration (90s, 6h) or seconds1h
swrserve-stale window · 0 = off10m
websocketon · offon
preserve_hoston · offon
max_objectsize (16mb)node limit

Changes are picked up automatically on the next refresh cycle.

Results: dummy-web.uhost.pro is faster

Metricdummy-web.uhost.proorigin-dummy-web.uhost.pro
Avg. first byte (TTFB)0.595s1.153s
Avg. total time0.702s1.153s
Response size12,881 bytes12,881 bytes

dummy-web.uhost.pro is ~48% faster in time to first byte than the origin - served from hubCDN's edge cache instead of round-tripping across continents on every request.

direct caching - no DNS needed

Optimize any image through hubCDN

Wrap any public image URL and get back a compressed, resized, edge-cached copy. No DNS changes, no signup - just a URL.

URL format

/img/<options>/<image-url>
/img/w=800,q=75,f=jpeg/https://your-site.com/photo.jpg

Options are comma-separated key=value pairs. A single _ applies the defaults: re-encode at quality 80 with metadata stripped.

Try it

Your optimized URL appears here.
optimized preview

All options

KeyValuesEffect
w, h1–4096Resize; one dimension keeps aspect ratio
fitscaledown · contain · cover · fillHow the image maps into w×h (cover center-crops)
dpr0.5–3Device pixel ratio multiplier for w/h
q1–100JPEG quality (default 80)
fauto · jpeg · png · gifOutput format; auto keeps transparency in PNG
grayonGrayscale
blur1–50Blur radius
fliph · v · hvMirror horizontally / vertically
_-No options: just compress & strip metadata
Retention: optimized images stay cached for up to 7 days. When the node fills up, the least-recently-used images are purged automatically and simply re-optimized on their next request - so hotlinking these URLs is always safe. Animated GIFs are passed through untouched.

Real example: 110x smaller, automatically

Photo optimized live through hubCDN's image endpoint
MetricOriginalThrough hubCDN
File size3.7 MB34 KB
Dimensions6000×4000600×400
FormatJPEG, untouchedJPEG, quality 80, no metadata

That preview above is this exact photo, live, resized with w=600 - 99% smaller (110x). Even with zero options at all (/img/_/<url>), just the default 2048px cap and re-encode alone takes it from 3.7 MB down to 247 KB - a 93% reduction - with no configuration whatsoever.

The first request pays a one-time cost to fetch and optimize the source (a few seconds, since this source is large); every request after that is served instantly from cache.

Test it yourself - open either link directly:

Original:  http://origin-dummy-web.uhost.pro/arnaud-padalle-9a8GgZPWnqU-unsplash.jpg
Optimized: https://cdn.hubcdn.space/img/w=600/http://origin-dummy-web.uhost.pro/arnaud-padalle-9a8GgZPWnqU-unsplash.jpg
Live Metrics
connecting...
-
Total Requests
-
Cache Hits
-
Stale Served
-
Cache Misses
-
Bypass
-
Not Modified
-
WebSocket
-
Image Requests
-
Image Hits
-
Image Misses
-
Cached Objects
-
Cache Usage
-
Uptime
-
Active Domains