HTTP Headers Analyzer
6 / 10
https://freeshemale.club
Website → CloudFlare → Browser9 missing headers, 1 warnings, 0 notices
The site is using a CDN, but the HTML page is not cached.
Header
Value
Explanation
date
thu, 26 dec 2024 10:59:09 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
.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.set-cookie
user_var=deleted; expires=thu, 01-jan-1970 00:00:01 gmt; max-age=0; path=/
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.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.set-cookie
from=spiders; expires=fri, 27-dec-2024 10:59:09 gmt; max-age=86400; path=/
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.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.set-cookie
lfrom=spiders; expires=fri, 27-dec-2024 10:59:09 gmt; max-age=86400; path=/
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.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.set-cookie
idcheck=1735210749; expires=fri, 27-dec-2024 10:59:09 gmt; max-age=86400; path=/
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.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.set-cookie
lp=%2f; expires=fri, 27-dec-2024 10:59:09 gmt; max-age=86400; path=/
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.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.set-cookie
index_page=1; expires=fri, 27-dec-2024 10:59:09 gmt; max-age=86400; path=/
A cookie that was sent from the server to the browser.
expires=
sets the maximum lifetime of the cookie using a specific date.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.cf-cache-status
dynamic
Warning The
dynamic
status indicates that Cloudflare did not cache the requested HTML page, similar to a "cache miss". By default, Cloudflare caches static assets such as images, CSS, and JavaScript but excludes HTML due to its dynamic nature. To cache HTML content, change the 'Cache Level' setting from dynamic
to cache everything
in Cloudflare. This adjustment allows HTML pages to be cached, leveraging Cloudflare's global network for faster and more efficient content delivery.report-to
{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=bpm5lmdf8roaqxoumd0t4nm%2f2vgths8aa1svyftbpwowsg5d0f0adogxj0rdxzg%2f79tc3so0rlhehvgqspkyj2neqnthrtmn0z%2fndxjqwwhhquxcpkymbaiuqq9hmcjkvgkb"}],"group":"cf-nel","max_age":604800}
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
{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
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.server
cloudflare
cf-ray
8f808f513c4e060e-iad
The
cf-ray
header provides a unique identifier for each request through Cloudflare. It's useful for troubleshooting and tracking requests in Cloudflare logs.alt-svc
h3=":443"; ma=86400
The
alt-svc
header advertises alternative services for accessing the same resource, enabling protocol negotiation and potential performance improvements.h3
indicates that HTTP/3 is supported. Variants like h3-29
refer to specific drafts of the HTTP/3 protocol.ma=86400
specifies that the alternative service information is fresh for 86400 seconds.server-timing
cfl4;desc="?proto=tcp&rtt=1056&min_rtt=1044&rtt_var=317&sent=6&recv=10&lost=0&retrans=0&sent_bytes=3400&recv_bytes=816&delivery_rate=2732075&cwnd=77&unsent_bytes=0&cid=14f0268aa855e777&ts=151&x=0"
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
missing Add a
Strict-Transport-Security
header. The Strict-Transport-Security
header or HSTS header is used to instruct browsers to only use HTTPS, instead of using HTTP. It helps enforce secure communication.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.