What records might a content-delivery network hold?¶

A content-delivery network sits between visitors and the website’s origin, so it may record both the public requests it handles and the customer configuration used to forward them.

Records from two relationships¶

On the customer side, the CDN may hold account, billing, administrator access, domains added, certificate and security settings. Origin configuration can identify the hostname or address to which the CDN forwarded requests.

On the visitor side, request and security logs may record timestamps, source addresses, requested hostnames and paths, responses, firewall decisions or abuse events. The precise fields and retention depend on the product and customer settings.

Think of a regional distribution depot: it can know who hired the service, where goods arrived from and which deliveries passed through, without owning the factory or products.

A CDN address may serve many unrelated sites. It identifies the intermediary, not the website operator or origin. Current origin settings may also differ from those used during the relevant event.

Specify the exact hostname, URL, timestamp and time zone, and distinguish whether the enquiry concerns the customer account, origin configuration, traffic or a security event. Volatile logs may require early preservation.