AlphaSierraGaming - OPSEC: Passive Recon Demonstration

OPSEC Principle: You don't have to do anything wrong to be radiating useful intelligence. The moment your browser contacts a server, a passive sweep is already complete. No login. No interaction. No warning. Everything below was collected before you clicked anything.

Your Visitor ID 31963740 will follow you through this demonstration.

► LAYER 1 — Server-Side Collection

Passive — collected before you clicked anything.

IP Address	216.73.217.87
Encrypted	Yes (HTTPS)
Port	443
Host Requested	alphasierragaming.com
Referrer	(none - direct navigation or referrer suppressed)
User Agent	Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Languages
Encodings	gzip, br, zstd, deflate
Query String	(none)

► LAYER 2 — Client-Side Collection

JavaScript — your browser reports in.

Screen Resolution	collecting...
Viewport Size	collecting...
Color Depth	collecting...
Pixel Ratio	collecting...
Platform	collecting...
Browser Language	collecting...
Timezone	collecting...
UTC Offset	collecting...
Cookies Enabled	collecting...
Local Storage	collecting...
Touch Capable	collecting...
Online Status	collecting...
Do Not Track	collecting...
CPU Cores	collecting...
Page Load Time	collecting...

► LAYER 2a — Media Device Intelligence

Passive — no prompt fired. Your browser reports what hardware exists and what permissions you have previously granted.

Camera Hardware	collecting...
Camera Permission	collecting...
Microphone Hardware	collecting...
Microphone Permission	collecting...

OPSEC Note: If device labels are visible above, your browser previously granted camera or microphone access to some site — and never revoked it. That permission follows you. No interaction required to collect this information.

► RAW HTTP HEADERS — Everything Your Browser Transmitted

Connection: close Accept: */* Accept-Encoding: gzip, br, zstd, deflate Host: alphasierragaming.com User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)

► LAYER 3 — What This Site Has Stored In Your Browser

Scope: This only shows what alphasierragaming.com has stored in your browser. Every other site you visit maintains its own equivalent store — tokens, credentials, preferences, tracking identifiers — invisible unless you look. Keys flagged like this contain patterns associated with auth tokens or session data.

● Cookies ()

● sessionStorage (0 items)

(none)

● localStorage (0 items)

(none)

► LAYER 4 — Device Battery Status

—

Battery Level

checking...

Charging	—
Time to Full	—
Time to Empty	—

OPSEC implication: Battery level can be used as a cross-site tracking vector. A low battery device visiting multiple sites can be correlated even across VPNs and private browsing sessions because the battery state is consistent regardless of identity measures. Firefox and Safari have restricted this API specifically because of this.

► WHAT THIS MEANS — OPSEC TAKEAWAY

Every item above was collected without your consent, without a login, and without you clicking anything. This is standard browser behavior — not an exploit.

IP Address — Geolocatable to city/region. VPNs mask this; many mobile carriers do not.
Referrer — Reveals where you came from, including search terms in some cases.
User Agent — Identifies OS, browser, and version. Partial fingerprint on its own.
Accept-Language — Reveals locale even when IP is masked by a foreign VPN exit node.

Screen + Timezone + Platform — Together these form a browser fingerprint capable of tracking you across sessions with no cookies required.
Do Not Track — A request, not a requirement. Most sites ignore it entirely.
CPU Cores / Pixel Ratio — Hardware fingerprinting. Narrows device identification significantly.
Browser Storage — Sites leave tokens, identifiers, and cached data in your browser. Most users never see it.
Battery Status — A persistent hardware fingerprint that survives VPNs and private browsing.

The parallel: This is EMCON discipline applied to your browser. Every HTTP request your machine makes is a transmission. Adversaries — commercial, criminal, and state-level — collect this passively, at scale, continuously. You are always broadcasting. The question is who is listening.

That was passive collection.

Want to see what an active intelligence sweep finds on your IP?
Or see exactly what our server logged about your visit today?

▲ Generate Intelligence Dossier on My IP ► What My Server See's - Log Entries ★ Generate Full Intelligence Dossier

▲ PASSIVE RECON DEMONSTRATION

That was passive collection.