HTTP Headers Analyzer
6 / 10
https://www.wikipedia.org
Website → Browser8 missing headers, 0 warnings, 2 notices
Header
Value
Explanation
date
sat, 29 mar 2025 08:46:23 gmt
The date and time at which the request was made. A browser uses it for age calculations rather than using its own internal date and time; e.g. when comparing against
Max-Age
or Expires
.cache-control
s-maxage=86400, must-revalidate, max-age=3600
max-age
specifies the maximum amount of seconds a page is considered valid. The higher max-age
, the longer a page can be cached.s-maxage
overrides max-age
header, but only for shared caches (e.g. CDN, Varnish) and not for browser caches.must-revalidate
indicates that once a page becomes stale, both shared caches and browser caches must not use their stale copy without validating it with the origin server first.server
ats/9.2.9
etag
w/"162d4-631157ccabe80"
A unique identifier that changes every time a page at a given URL changes. It acts as a fingerprint. A cache can compare
Etag
values to see if the page has changed and became stale. For example, a browsers will send the ETag
value of a cached page in an If-None-Match
header. The web server compares the ETag
value sent by the browser with the ETag
value of the current version of the page. If both values are the same, the web server sends back a 304 Not Modified
status and no body. This particular Etag
value starts with w/
which means that it is a weak identifier; while unlikely, multiple pages might have the same identifier. Weak identifiers are used because strong identifiers can be difficult and costly to generate.last-modified
mon, 24 mar 2025 12:10:18 gmt
The date and time at which the origin server believes the page was last modified.
Notice Because there is an
Notice Because there is an
Etag
header, Last-Modified
is likely to be ignored. The ETag
hash is more accurate than the date/time in Last-Modified
. Consider removing Last-Modified
to save bandwidth and processing power.vary
accept-encoding
The
Vary
header specifies a list of headers that must be considered when caching responses. For a cached response to be used, these headers must match between the cached response and the new request. This ensures that the appropriate version of a resource is served based on factors like language, encoding, or device type.age
8230
The time in seconds that the page has been in the shared proxy cache. The maximum age is set by
max-age
or s-maxage
in the Cache-Control
header.x-cache
cp1110 miss, cp1110 hit/156446
The page was served from a cache.
x-cache-status
hit-front
Indicates how the caching system processed this request. The response was served from cache.
server-timing
cache;desc="hit-front", host;desc="cp1110"
Communicates one or more metrics for a given request-response cycle. Can includes metrics for CPU time, database read/writes, file system access, etc.
strict-transport-security
max-age=106384710; includesubdomains; preload
The
Strict-Transport-Security
header (HSTS) instructs browsers to only use HTTPS for future connections to this domain, enhancing security by preventing downgrade attacks and cookie hijacking.max-age
specifies the time, in seconds, that the browser should remember to use HTTPS only for this domain.includesubdomains
instructs the browser that all subdomains are HTTPS-only as well.preload
recommends the domain for inclusion in browsers' preload lists. If accepted, the domain would get hardcoded into browsers as HTTPS-only.report-to
{ "group": "wm_nel", "max_age": 604800, "endpoints": [{ "url": "https://intake-logging.wikimedia.org/v1/events?stream=w3c.reportingapi.network_error&schema_uri=/w3c/reportingapi/network_error/1.0.0" }] }
This header is part of the Reporting API specification. They are used to configure the reporting of network errors and other issues to a specified endpoint.
The
The
Report-To
header specifies where reports should be sent.group
defines the reporting group. Groups allow reports to be grouped logically; e.g. there could be a group for network errors and a second group for browser feature deprecation reports.max_age
defines the number of seconds the browser should remember these settings. Prevents the browser from having to parse the JSON on each request.endpoints
defines one or more URLs where the reports need to be send to. Multiple URLs can be specified for failover and load-balancing. Endpoints can be assigned a weight
to distribute load, with each endpoint receiving a specified fraction of the reporting traffic. Endpoints can also be assigned a priority
to set up fallback collectors.nel
{ "report_to": "wm_nel", "max_age": 604800, "failure_fraction": 0.05, "success_fraction": 0.0}
This header is part of the Reporting API specification. They are used to configure the reporting of network errors and other issues to a specified endpoint.
The
The
NEL
(Network Error Logging) header configures the reporting of network errors.report_to
defines the reporting group that reports for this NEL policy will be sent to. The reporting group details are specified in the Report-To
header.max_age
defines the number of seconds the browser should remember these settings. Prevents the browser from having to parse the JSON on each request.success_fraction
defines the sampling rate that should be applied to reports about successful network requests. Its value must be a number between 0.0 and 1.0: 0 means no successful requests should be reported, and 1 means that every successful request should be reported.failure_fraction
defines the sampling rate that should be applied to reports about failed network requests. Its value must be a number between 0.0 and 1.0: 0 means no failed requests should be reported, and 1 means that every failed request should be reported.set-cookie
wmf-last-access=29-mar-2025;path=/;httponly;secure;expires=wed, 30 apr 2025 00:00:00 gmt
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.path=
indicates the path that must exist in the requested URL for the browser to send the cookie.secure
instructs the browser to only send the cookie back when HTTPS requests are used, making it more resistant to man-in-the-middle attacks.httponly
forbids JavaScript from accessing the cookie. Helps mitigate the risk of client side scripts accessing a protected cookie.set-cookie
wmf-last-access-global=29-mar-2025;path=/;domain=.wikipedia.org;httponly;secure;expires=wed, 30 apr 2025 00:00:00 gmt
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.domain=
sets the domain to which the cookie will be sent.path=
indicates the path that must exist in the requested URL for the browser to send the cookie.secure
instructs the browser to only send the cookie back when HTTPS requests are used, making it more resistant to man-in-the-middle attacks.httponly
forbids JavaScript from accessing the cookie. Helps mitigate the risk of client side scripts accessing a protected cookie.set-cookie
geoip=us:va:ashburn:39.05:-77.49:v4; path=/; secure; domain=.wikipedia.org
A cookie that was sent from the server to the browser.
domain=
sets the domain to which the cookie will be sent.path=
indicates the path that must exist in the requested URL for the browser to send the cookie.secure
instructs the browser to only send the cookie back when HTTPS requests are used, making it more resistant to man-in-the-middle attacks.set-cookie
networkprobelimit=0.001;path=/;secure;samesite=lax;max-age=3600
A cookie that was sent from the server to the browser.
Notice
max-age=
sets the maximum lifetime of the cookie in seconds.path=
indicates the path that must exist in the requested URL for the browser to send the cookie.Notice
samesite=lax
instructs the browser not to share the cookie with third-party sites (e.g. when loading images, videos or frames from other sites), with one exception. The cookie will be sent when a user is navigating to the origin site from an external site (for example, when following a link). To improve protection against cross-site request forgery attacks, set to samesite=strict
.secure
instructs the browser to only send the cookie back when HTTPS requests are used, making it more resistant to man-in-the-middle attacks.x-client-ip
50.19.157.248
accept-ranges
bytes
Used by the server to advertise its support of partial HTTP requests. The browser can ask for a range or subset of the response body. It's a feature that allows a browser to resume an interrupted download.
bytes
is the only range unit currently supported. none
means that the server does not support range requests.content-length
90836
The size of the message body, in bytes.
content-security-policy
missing Add a
Content-Security-Policy
header. The Content-Security-Policy
header helps browsers prevent cross site scripting (XSS) and data injection attacks.referrer-policy
missing Add a
Referrer-Policy
header. When a visitor navigates from one page to another, browsers often pass along referrer information. The Referrer-Policy
header controls how much referrer information a browser can share. This is important to configure when private information is embedded in the path or query string and passed onto an external destination.permissions-policy
missing Add a
Permissions-Policy
header. Restrict access to device features like the camera, microphone, location, accelerometer and much more.cross-origin-embedder-policy
missing Add a
Cross-Origin-Embedder-Policy
to specify how this page can be loaded by cross-origin resources.cross-origin-opener-policy
missing Add a
Cross-Origin-Opener-Policy
header to opt-in into better browser isolation.cross-origin-resource-policy
missing Add a
Cross-Origin-Resource-Policy
header to specify who can load this page.x-frame-options
missing Add a
X-Frame-Options
header. The X-Frame-Options
header prevents this URL from being embedded in an iframe
. This protects against clickjacking attacks. Alternatively, set a Content-Security-Policy
header with a frame-ancestor
directive.x-permitted-cross-domain-policies
missing Add a
X-Permitted-Cross-Domain-Policies
header to prevent Flash, Adobe Reader and other clients from sharing data across domains.Questions or feedback? Email dries@buytaert.net.