Secure CDN. Faster delivery, less load on your origin.
Content comes from the nearest node, fast for users anywhere and with less load on your origin.
- Faster load times
- Less origin load
- Globally distributed network
Secure CDN. What it is and what it does.
Secure CDN serves your content from the nearest edge node; if your origin stops responding, cached content can optionally be kept available there. TLS and access restrictions apply at the node.
ISO 27001
SOC 2 Type II
BSI C5- 24/7 SupportSecurity threats don’t wait for business hours, and neither do we. Our specialists are available around the clock to help you when needed.
- GDPR-compliantLink11’s European location ensures your content remains compliant with strict GDPR regulations and EU data protection laws.
- Fully managed serviceOur fully managed solution, maintained by security experts around the clock, ensures your protection is always up to date, 24/7, 365 days a year.
Your users are everywhere. Your origin is in one place.
Three situations where the application runs and still nobody arrives.
Static content sits at the edge and comes from the nearest node.
Optionally, cached content stays available on the node, even without a response from the origin.
HTTP is redirected to HTTPS at the node; IP-based access restrictions apply there.
When everyone clicks at once. The nearest node delivers.
On holiday, readers open the news from home, and travelers order from your shop abroad. Your origin is far away from both.
Content comes from the nearest edge node, so pages load quickly wherever they are.
Polls close, the whole country reloads the results, and the page is a target too.
When enabled, the CDN keeps serving cached results, even if the origin stops responding.
Your offer is meant for certain countries, but requests arrive from everywhere.
Geo blocking prevents access to your content in the CDN per country, or for whole regions.
See what comes from the edge. And what from the origin.
Cache rules per path, TLS and access rules at the node and the origins behind it.
Shorter path, faster answer. Four steps to delivery at the edge.
Before you connect. The technical details.
- Onboarding: DNS to the CDN nodes, origin stays
- Caching: Static at the edge, rules per path
- Protection: Link11 nodes behind Network DDoS, TLS, ACL
- Geofencing: Storage limited by country, per instance
- Edge caching
- Cacheable resources sit at the nodes; DNS-based load balancing leads to the nearest one.
- Control
- Three cache modes — header-based, static by file type or hybrid — plus cache key and rules by path or file extension.
- Origins
- Several origins via load balancing; separate setup for static and dynamic content.
- API
- Secure CDN can be configured almost entirely through the API.
- Nodes
- Cached content is delivered from the node nearest to your users.
- Geofencing
- You can prevent nodes in certain countries from storing your content.
- TLS and access
- HTTP-to-HTTPS redirection, auto-renewing certificates (with Secure DNS), IP-based access restrictions.
- WAAP
- CDN functions and WAAP protection run in sync on the same platform.
- Dynamic content
- What can be cached is cached. Personalized or dynamic responses continue to the origin — faster only through the shorter path, not through the cache.
- Geo blocking
- Blocking works per country or region based on IP databases. It is a control, not access control with 100% accuracy.
- No application protection
- Secure CDN does not inspect requests and does not protect on Layer 7; that is the job of the WAAP platform. Nodes in the Link11 network sit behind Link11 Network DDoS Protection so that the CDN itself stays available.
Questions before you decide. Answered directly.
Do I need CDN and WAAP together?
Not necessarily. The CDN brings delivery and origin offload, the WAAP platform inspects requests. The two can be combined.
Does dynamic content get faster too?
The CDN caches what you allow it to: by default it follows your origin’s caching headers, and the cache mode per path can change that. Responses that may not be cached go to the origin and gain only from the shorter path; static and dynamic origins can be connected separately.
Do I need Secure DNS for this?
Not for delivery. The automatically renewed TLS certificates via Let’s Encrypt do require Secure DNS — without it you bring your own certificates.
What happens if our origin goes down?
If you switch on stale content in the location caching settings, cached content keeps being delivered on server errors or timeouts. Whatever is not in the cache goes down with the origin — which is why the question of what gets cached belongs in onboarding, not in the incident.
Is CDN uptime guaranteed?
Yes. We guarantee 100% CDN uptime and optimized performance, so you can deliver exactly what your users need, every day, at any time.
What does Secure CDN cost?
You receive an individual quote depending on traffic volume, regions and origins. Access logs are an add-on. A conversation clarifies scope and price.
Let’s talk
Your business stays online. We’ll show you how.