You can check some website security settings from the outside. Response headers, cookie attributes, CORS behavior, and redirects reveal how the site handles browser requests. They are a useful place to start before testing the application’s private functions.

Here is how to inspect those four areas and understand what the results can tell you.

Security headers: your browser's first line of defense

HTTP security headers tell the browser how to behave when it renders your site, and a missing or misconfigured header is one of the most common gaps in web application security.

Content-Security-Policy (CSP) restricts the scripts, styles, and frames a page can load. A well-configured policy can block injected scripts, reducing the impact of cross-site scripting. Check what the policy actually permits; its presence alone is not enough.

Strict-Transport-Security (HSTS) forces the browser to use HTTPS for every future visit, closing the window where a downgrade attack could force a connection back to unencrypted HTTP.

X-Frame-Options and its modern replacement, the frame-ancestors directive in CSP, control whether your site can be embedded in an iframe on another domain. Without it, your site is vulnerable to clickjacking, where an attacker overlays invisible UI elements on top of a legitimate-looking page to trick users into clicking something they didn't intend to.

X-Content-Type-Options stops the browser from guessing a file's MIME type based on content rather than the declared header, which shuts down a class of attacks that rely on MIME sniffing.

Referrer-Policy limits URL information sent in the Referer header. Permissions-Policy controls access to browser features such as the camera, microphone, and geolocation. Review both against what the site needs.

Inspect the attributes on session cookies, especially Secure, HttpOnly, and SameSite. These settings affect how browsers send the cookie and whether page scripts can read it.

The Secure flag ensures a cookie is only ever transmitted over HTTPS, never sent in plaintext over an unencrypted connection. HttpOnly prevents client-side JavaScript from reading the cookie at all, which is the primary defense against session token theft via XSS. If an attacker manages to inject a script but the session cookie is HttpOnly, they still can't exfiltrate it.

SameSite controls when browsers include a cookie in cross-site requests. Review its value alongside the application’s CSRF protection and any legitimate cross-site integrations.

Treat a missing attribute as a finding to investigate in context. Identify what the cookie holds and how the application uses it before assigning severity.

CORS configuration: where cross-origin access goes wrong

CORS tells browsers which other origins may read API responses. Review the permitted origins and credential settings together, then test the response from an origin that should be denied.

Check for origin reflection combined with Access-Control-Allow-Credentials: true. An API that trusts an arbitrary Origin may let another site read sensitive responses using the visitor’s credentials. Verify that behavior with test accounts. Also review wildcard settings; browsers reject a wildcard allowed origin for credentialed response access.

Transport and redirects: the path your traffic takes

Inspect the initial HTTP response and every redirect to HTTPS. An HTTP request can be observed or changed on an untrusted network before the upgrade. Check HTTPS pages for resources loaded over plain HTTP as well.

Evidence over guesswork

Running through all four layers manually means inspecting response headers with browser dev tools, checking cookie attributes in the application panel, and testing CORS behavior with crafted requests, which is doable but slow, and easy to get wrong if you're not doing it daily.

Ceron Check makes a small number of read-only requests to a public URL and reports on headers, cookies, CORS, and redirects. Each finding includes the observed evidence, an explanation, and a suggested next step, ordered by severity. The check is free and requires no login or installation.

What this layer can't tell you

A successful check describes the responses examined. It does not assess account permissions, injection, business rules, or private cloud configuration. Those need tests with the relevant inputs and access.

Use this check to find browser-facing configuration problems, then scope deeper testing around the application’s accounts, APIs, and cloud services. Those areas need tests that exercise what users can read and change.

Back to the blogExplore Ceron