← All guides

Check Set-Cookie header with curl

Requirement:

curl or a comparable HTTP tool and the public URLs to be checked.

Check response headers of the homepage and relevant subpages. Include redirect chains. A Set-Cookie header is initially a finding; Then evaluate the purpose, lifespan, SameSite/Secure and necessity of the cookie.

The specific read-only commands are collected under Check the website yourself.

Rate result

A single hit is a technical finding. Then check the purpose, actual storage, transfer and retention period of the affected level separately.

Classify in the overall check

This individual test only covers one level. Then systematically check the remaining levels using the checklist for unnecessary visitor data .

Related guides

• Cookieless is not automatically tracking-free
• CAPTCHA and spam protection: first local, then external
• PHP sessions: only use when state is really needed
• PostHog: Correctly classify cookieless mode

Sources and verification

This guide is based on multiple current sources. Vendor documentation is not treated as proof that every concrete installation automatically follows the same privacy characteristics.

• Self-test
• Inspection checklist

Important: IP processing is not IP storage

An IP address has to be processed to establish and deliver a network connection. Hosting providers, firewalls or DDoS protection may also process or retain it for a limited time for security purposes. No Logging distinguishes this security layer from unnecessary persistent visitor logging by the website, application and ordinary access logs.