Free cookie security checker
Check the cookies your home page sets, and whether each has the Secure, HttpOnly and SameSite attributes it needs.
Example report
example.com- 1 Medium
- 1 Information
- 1 passed
Cookie set without the Secure flagexample.comMedium
https://example.com/ sets the cookie session without the Secure attribute.
Next step
Add the
Secureattribute to every cookie the site sets over HTTPS.Cookie set without SameSiteexample.comInformation
https://example.com/ sets the cookie prefs without a SameSite attribute.
Next step
Add
SameSite=Lax(orStrictwhere possible) to cookies.
- Cookie security
Cookies set by the home page
example.com
| Cookie | Secure | HttpOnly | SameSite | Scope |
|---|---|---|---|---|
session | No | Yes | Lax | Path=/ |
prefs | Yes | No | Not set | Path=/ |
www.example.com
No cookies were set on the home page.
Cookie values are never kept or shown: the scanner removes them before anything leaves it.
What the cookie check looks at
Secure
Every cookie kept to HTTPS, never sent over plain HTTP.
HttpOnly
Session-like cookies hidden from scripts on the page.
SameSite
Whether a cookie travels with requests that start on other sites.
What is listed
Each cookie name and its attributes. Values are removed by the scanner.
Only cookies the public home page sets are seen. Cookies set after signing in, by scripts or on other paths are not.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
Cookie set without the Secure flagMedium
A cookie was set over HTTPS without the Secure attribute.
Set-Cookie: session=; Path=/; HttpOnly; SameSite=LaxWithout Secure, the browser will also send the cookie over plain HTTP, where it can be intercepted. This matters most for session and authentication cookies.
Add the Secure attribute to every cookie the site sets over HTTPS.
Common cookie issues you can put right
Cookie set without the Secure flagMedium
A cookie without Secure can be sent over plain HTTP, where anyone on the network path can read it. Add Secure to every cookie the site sets over HTTPS.
Session cookie readable by scriptsLow
A session cookie that scripts can read is exposed to any script injected into the page. Add HttpOnly to cookies only the server needs.
Cookie set without SameSiteInformation
Without SameSite, each browser applies its own default. Set it on every cookie, usually Lax, so its cross-site behaviour is your choice.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- Every
Set-Cookieheader on the HTTPS responses for the home page, redirects included, for the domain and itswww.name, or the subdomain entered. Up to 10 cookie names per host are judged. Secureon every cookie. Without it, the finding is medium severity when the name looks like a session or sign-in cookie, and low otherwise.HttpOnlyon cookies whose names suggest a session or sign-in token, such as names containingsess,sid,auth,tokenorjwt. Other cookies may legitimately be read by scripts and are not judged on it.SameSiteon every cookie, with its value shown.- Each cookie's name and attributes are listed. Values are removed by the scanner before anything is kept or shown.
Reading a result
A cookie's attributes decide where the browser sends it and who can read it. Secure keeps it to HTTPS connections. HttpOnly hides it from JavaScript, so a script injected into the page cannot read it. SameSite controls whether it travels with requests that start on another site: Strict never, Lax only when the visitor follows a link to the site, None always, and then it must also be Secure.
Session and sign-in cookies matter most, because whoever holds one is, to the site, the signed-in user. The check recognises them by name, so a session cookie with an unusual name is judged like any other cookie, and a harmless one with token in its name may be flagged.
A pass means the home page set no cookies, or every cookie had Secure and SameSite and every session-like cookie had HttpOnly. Many sites set no cookies on the home page at all; that is a genuine pass, not a sign the check did not look.
What it does not do
- It sees only cookies the public home page sets. Session cookies are usually set after signing in, on other paths or by an application on another host, and none of those are visited.
- Cookies set by JavaScript in the browser, including by third-party scripts, are not seen. The check does not run scripts.
- Recognising a session cookie by its name is a guess. Review any finding against what the cookie actually does.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- What is the difference between Secure and HttpOnly?
- Secure stops the browser sending the cookie over plain HTTP. HttpOnly stops JavaScript on the page reading it. A session cookie should have both.
- Which SameSite value should I use?
- Lax suits most cookies, including sessions on sites people reach by following links. Strict is tighter but leaves the cookie out when a visitor arrives from another site. None is only for cookies that must work inside other sites, and requires Secure.
- Why does the checker show no cookies for my site?
- The home page did not set any. Many sites set cookies only after sign-in, or on the application's own host, which this check does not visit.

