X-Sucuri-Id

The HTTP X-Sucuri-Id response header is an unofficial HTTP header identifying the Sucuri CDN point of presence (PoP) or edge node handling the request.

Note

The X- prefix for non-standard headers is deprecated per RFC 6648.

Table of Contents

Usage

Sucuri is a website security platform providing DDoS protection, web application firewall (WAF) filtering, and content delivery network (CDN) services. When a request passes through Sucuri's proxy network, the X-Sucuri-Id header is added to the response identifying which CDN edge node or PoP served the request.

The value encodes the Sucuri data center location. Requests routed to the same PoP return the same identifier regardless of the specific request. Site administrators and Sucuri's support team use the value to determine which edge location handled a request when investigating routing, performance, or WAF filtering issues. Sites protected by Sucuri typically also return an X-CDN or Server header identifying the Sucuri proxy layer.

Values

numeric-id

The numeric-id is an opaque numeric string, typically five digits. The first two digits identify the Sucuri PoP location (e.g., 14 for Washington DC). The remaining digits encode node or configuration details within the PoP. Requests handled by the same edge location return the same value prefix.

Example

A response from a site protected by Sucuri's WAF includes the identifier as a short numeric string. The value 11004 identifies the Sucuri PoP serving the request. All requests routed to the same PoP return the same leading digits.

X-Sucuri-Id: 11004

A different value indicates a different PoP location. The 14 prefix here identifies the Washington DC data center.

X-Sucuri-Id: 14020

Values in the 20000 range indicate yet another PoP or configuration group within Sucuri's network.

X-Sucuri-Id: 20004

Takeaway

The X-Sucuri-Id header identifies the Sucuri CDN edge node or PoP handling the request. The numeric value encodes the data center location, giving site administrators and Sucuri support a way to determine which edge location served a particular request.

See also

Last updated: March 6, 2026