Content delivery network meaning, in plain words

A content delivery network serves copies of your pages from sites around the world. How a CDN works, what RFC 6707 and CISA say about it, and what it does not fix.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

A CDN serves your site quickly and helps protect it by delivering from locations around the world. It stands for content delivery network. Copies of images and pages are placed near the visitor and delivered from there. RFC 6707 from the IETF defines a CDN as an infrastructure in which network devices cooperate to deliver content more effectively.

How does a CDN work?

Think of a nationwide chain that keeps stock in warehouses in each region and ships from the one nearest the customer. Orders do not pile up at the head office (the origin server), and parcels arrive sooner.

RFC 6707 explains that a CDN can place copies of content at the edge of the network, on the side close to users. The devices holding the copies are called surrogates, which can also be described as caches. The same document says this design helps in situations such as sudden bursts of access and denial-of-service attacks. CISA lists subscribing to a DoS protection service as one countermeasure. Such a service detects abnormal traffic and diverts it away from your own network.

A CDN does not close every path. If a route that connects straight to the origin server stays open, that route needs separate protection. For pages whose content changes per member, decide in advance that they are left out of the copies. Preparation for access floods is gathered under DDoS measures.

Why do CDNs matter?

When a campaign or a TV mention sends traffic up suddenly, a single server can slow down or stop. A CDN shares that load among its sites around the world and reduces the number of requests that reach the origin server.

RFC 6707 names lower delivery cost, a better experience for users, and more resilient delivery as benefits of a CDN. A CDN is still not a shield for everything, and holes in the site must be fixed on their own. The free URL check can show the site as an outside visitor sees it, with or without a CDN in front.

Related terms

  • DDoS attack: an attack that makes a site unusable with a flood of traffic
  • WAF: a mechanism that stops malicious traffic at the entrance
  • SRI: a mechanism that detects tampering with files loaded from outside
  • Cache poisoning: an attack that slips false content into a stored copy

Frequently asked questions

If I add a CDN, are the site's vulnerabilities fixed too?

No. A CDN supports delivery. Weaknesses in the site's own program or settings still have to be fixed separately. If a path that connects straight to the origin server is open, that path needs its own protection.

Is it safe to let a CDN store pages shown after login?

Avoid storing pages whose content differs by member as a copy for everyone. Decide page by page which ones the CDN may copy, and check the display after you switch it on.

Next step

The order in which to prepare for traffic surges and attacks is in DDoS measures. If you are weighing whether to introduce a CDN, contact us.

Frequently asked questions

If I add a CDN, are the site's vulnerabilities fixed too?

No. A CDN supports delivery. Weaknesses in the site's own program or settings still have to be fixed separately. If a path that connects straight to the origin server is open, that path needs its own protection.

Is it safe to let a CDN store pages shown after login?

Avoid storing pages whose content differs by member as a copy for everyone. Decide page by page which ones the CDN may copy, and check the display after you switch it on.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.