SOC//PRAMOD │ SHIFT: NIGHT UTC: --:--:--

SECURE CHANNEL

Building a SOC, need detection engineering and SOAR automation, or hiring blue team analysts — get in touch. I reply to everything.

SECURE CHANNEL

TLS 1.3 · OPEN

Building a SOC, need detection engineering and SOAR automation, or hiring blue team analysts — open a channel. I reply to everything.

OSINT RECON — SUBJECT PROFILE

SELF-DISCLOSED
SUBJECT
Pramod Rodge
ALIAS
pramod-rodge-
EMPLOYER
Amazure Technology Pvt Ltd
ROLE
Cybersecurity Engineer & SOC Analyst
GEO
Mumbai / Pune, Maharashtra, IN
EDUCATION
B.Tech CSE (Cyber Security), Parul University — 2024
LANGUAGES
English · Hindi · Marathi
FOOTPRINT
linkedin.com/in/pramod-rodge-
CODE
github.com/Pramod1336
CONTACT
pramod.srodge@gmail.com
ANALYST ASSESSMENT Subject's exposure surface is deliberate and minimal: professional identifiers published, nothing else. Everything on this page was put here on purpose — which is the point. Knowing what your own footprint looks like from the outside is the first exercise in OSINT.

PASSIVE RECON — TARGET: YOU

NOTHING HERE IS TRANSMITTED · ZERO STORAGE
READ THIS FIRST Nothing below leaves your browser. No request is made, no cookie is set, nothing is stored, there is no analytics on this site and no visit is ever recorded — this page declares connect-src 'none' in its Content-Security-Policy, so it is structurally incapable of transmitting any of it. I ran no scan and asked you nothing. Every website you open can read everything below the moment it loads, before you click a single thing. Most people have never been shown what that looks like, so here is yours.
THE POINT The point isn't the data — it's that passive collection is this cheap and this invisible. Verify the claim above in your own developer tools: check the CSP in the response headers, then watch the network tab stay completely empty while this panel fills.
WHERE THIS GETS INTERESTING Some of the above may be wrong, and that is the good news. Brave and Firefox deliberately farble or withhold these values — randomising screen dimensions, clamping CPU counts, refusing deviceMemory entirely. Brave goes further and ships a User-Agent byte-identical to Chrome so the string itself cannot give it away; the only honest way to ask is navigator.brave.isBrave(), which is what this panel calls. Anything reading "withheld" is your browser refusing to answer, and that refusal is worth more to you than the value would have been.