X-Nf-Request-Id

The HTTP X-Nf-Request-Id response header is an unofficial header containing a unique request identifier assigned by Netlify's edge network.

Note

The "X-" naming convention for HTTP headers, "X" referring to "experimental", has been deprecated and needs to be transitioned to the formal naming convention for HTTP headers.

Usage

Netlify adds the X-Nf-Request-Id header to every response passing through its edge infrastructure. The value uniquely identifies each request and enables log correlation when debugging issues in Netlify's dashboard or when working with Netlify support.

The header serves a similar purpose to X-Request-Id in general infrastructure and X-Vercel-Id on Vercel deployments. For Cloudflare-proxied sites, Cf-Ray fills the same role. Each platform assigns its own request identifier format, but the goal is the same: tracing a single request through the serving infrastructure.

Values

Format

Netlify describes the value as a 26-character string. The format is consistent with ULID (Universally Unique Lexicographically Sortable Identifier): 26 characters of Crockford's Base32, with a timestamp-prefixed structure making identifiers sortable by creation time. Netlify has not officially confirmed the identifier is a ULID.

Example

A request to a Netlify-hosted site returns a 26-char identifier. The leading characters appear to encode a timestamp, so identifiers from the same time period share a common prefix.

X-Nf-Request-Id: 01KJD9FATBP38BK9EPSN617QKP

A different request to another Netlify site produces a distinct identifier. The prefix differs because the request occurred at a different time.

X-Nf-Request-Id: 01KD3QBFYW8JQM28DMGPGX58YC

When contacting Netlify support or searching through deploy logs, providing the X-Nf-Request-Id value pinpoints the exact request in the platform's logging infrastructure.

X-Nf-Request-Id: 01KGEM0MSVX1MD8D2F6KAJSSAV

Takeaway

The X-Nf-Request-Id response header provides a unique 26-character identifier for every request handled by Netlify's edge network, enabling log correlation and support debugging.

See also

Last updated: March 6, 2026