Scantide Observe
What Security Headers Actually Do
Security headers tell browsers how to handle HTTPS, scripts, framing, referrers and browser features. Missing headers are evidence to review, not automatic proof that a site is unsafe.
Scantide Observe Guides
Browser-visible website security and privacy evidence
Practical, evergreen explanations built around the questions administrators, security teams and technically curious users actually ask. Read the concept first, then use Scantide to inspect the evidence.
12 guidesEvidence-orientedNo exploitation
Practical-depth library: Scantide guides are maintained as technical references with field examples, failure modes, investigation detail and checklists rather than short search summaries.
Scantide Observe
Content Security Policy Explained Without the Jargon
A Content-Security-Policy header can limit where scripts and other content are allowed to load from, reducing the impact of some injection attacks and making unexpected dependencies easier to spot.
Scantide Observe
HSTS Explained: Why HTTPS Alone Is Not the Whole Story
HTTP Strict Transport Security tells a browser to prefer HTTPS for a site after receiving the policy, reducing opportunities for accidental HTTP use and some downgrade scenarios.
Scantide Observe
Secure, HttpOnly and SameSite Cookies: What the Flags Mean
Cookie attributes influence when cookies are sent, whether browser scripts can read them, and how they behave across sites. They are small settings with important security and privacy consequences.
Scantide Observe
Why Third-Party Scripts Matter to Website Security
A page inherits part of the security and privacy posture of the scripts it loads. External analytics, widgets, consent platforms and libraries expand the trust chain beyond the site owner.
Scantide Observe
Website Trackers: What They Are and Why They Matter
Trackers can support analytics, advertising, consent, fingerprinting, measurement and session replay. Their presence is not automatically malicious, but it changes who may receive data when a page is used.
Scantide Observe
Network Beacons and Contacted Hosts: What a Browser Reveals
A page may contact far more hosts than the address bar suggests. Network requests can expose analytics, APIs, CDNs, advertising, identity providers and other dependencies.
Scantide Observe
Forms, Iframes and Embedded Content: Hidden Parts of the Trust Chain
Forms and iframes can send users or data into systems operated by other domains. Reviewing their destinations helps explain where authentication, payment and embedded content actually live.
Scantide Observe
Why a Website Security Score Is Not a Verdict
A risk score is useful as a shortcut, but the evidence behind it matters more. Different pages have different purposes, dependencies and acceptable exposure.
Scantide Observe
What Browser-Visible Security Evidence Can — and Cannot — Tell You
A browser can reveal headers, cookies, scripts, forms, frames and network behavior. It cannot see every server-side control, database setting or internal security decision.
Scantide Observe
Website Jurisdiction and Third-Party Services: What Can Be Inferred
Infrastructure country, provider and ASN context can help governance reviews, but location evidence should be treated as context rather than a complete legal conclusion.
Scantide Observe
How to Review a Login Page Before Entering Credentials
Before entering a password, check the domain, HTTPS state, browser-visible dependencies, form destination and unexpected third-party content. The goal is context, not paranoia.
Use the product
The guides explain the problem. Scantide Observe provides the corresponding viewpoint and evidence.
Explore Scantide ObserveAll Scantide guides