Checks

SameSite=None without Secure

A cookie uses SameSite=None and does not set Secure.

Why it matters

Browsers reject SameSite=None unless the cookie is Secure, so the cookie is dropped or sent in a way you did not intend.

What to do

Add Secure, or use SameSite=Lax or Strict if the cookie does not need to be sent cross-site.

Reference

Cookie attributes such as Secure, HttpOnly, and SameSite protect session tokens in browsers.

OWASP Session Management Cheat Sheet