<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by D4rk_Intel on Medium]]></title>
        <description><![CDATA[Stories by D4rk_Intel on Medium]]></description>
        <link>https://medium.com/@preciousvincentct?source=rss-9b988def4bd3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ICnZ4maXLkAWEV74l5Dxjw@2x.jpeg</url>
            <title>Stories by D4rk_Intel on Medium</title>
            <link>https://medium.com/@preciousvincentct?source=rss-9b988def4bd3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:04:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@preciousvincentct/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Professional Workflow for Investigating Online Scammers]]></title>
            <link>https://preciousvincentct.medium.com/a-professional-workflow-for-investigating-online-scammers-09aac8a432c4?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/09aac8a432c4</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 22:03:07 GMT</pubDate>
            <atom:updated>2026-10-16T20:08:50.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*IVvYftQiFPgrkBSeDcHWQA.png" /></figure><p><strong>Before we begin, one crucial clarification</strong>. In OSINT, we do not investigate “<strong><em>scammers</em></strong>” as abstract entities. We investigate <strong>actors</strong>, <strong>infrastructure</strong>, <strong>artifacts</strong>, and <strong>networks</strong>. A scammer is a person or group behind a fraudulent operation. The scam itself is the operation. Your job as an analyst is to collect, preserve, correlate, and validate publicly available information to identify the people, tools, and patterns behind the fraud.</p><p>This is not a passive activity. It requires operational security, documentation discipline, and analytical rigor. Every step you take is logged. Every piece of evidence is preserved with provenance. Every conclusion is calibrated with confidence language.</p><h3>Who Is a Scammer? Who Is a Scam?</h3><p>A scam is a deliberate deception designed to produce financial or informational gain. A scammer is the actor or group executing that deception. They are not always lone wolves. Many are part of organized networks operating across borders, using infrastructure that spans multiple platforms and jurisdictions .</p><p>Modern scammers are professionals. They use AI-generated content, synthetic identities, and layered infrastructure to scale operations and evade detection . The traditional image of a lone fraudster is outdated. What I investigate is often an ecosystem: operators, money mules, infrastructure providers, and sometimes trafficked labor in scam compounds.</p><h3>Types of Scams and How to Protect Yourself</h3><p>Before you investigate a scam, you need to understand what you are looking at. Scams are not random. They follow patterns, and those patterns are predictable. The more you understand the taxonomy of fraud, the faster you can identify what a scammer is doing, why they are doing it, and where their infrastructure is likely hosted.</p><p>This section is not just for victims. It is for investigators. When you know the anatomy of a scam, you know where to look for evidence.</p><h3>The Major Scam Categories</h3><h3>1. Phishing and Spoofing</h3><p>Phishing is the most reported fraud category, accounting for roughly one in three complaints filed with fraud watchdogs . The mechanics are simple: a <strong>scammer impersonates a trusted entity</strong> — your bank, a government agency, a delivery service — and tricks you into revealing credentials, personal data, or payment details.</p><p><strong>Spoofing </strong>is the technical layer that makes it work. Scammers manipulate caller ID, email headers, or website URLs to make the communication appear legitimate. A text message can appear in the same thread as a genuine conversation with your bank. An email can display the correct sender name while routing through a scammer’s server.</p><p><strong>Why this matters for investigators</strong>: Phishing infrastructure leaves traces. Domain registration data, email headers, and SSL certificates are the breadcrumbs you follow in Steps 2 and 4.</p><p><strong>How to protect yourself</strong>: Never click links in unexpected messages. Contact the organization using a phone number or website you look up yourself, not the one provided in the message . Check for slight variations in sender IDs — dots, special characters, or numbers that do not belong.</p><h3>2. Investment and Cryptocurrency Scams</h3><p>Investment scams are the most financially destructive category, with a median reported loss of $30,000 . FTC data shows reports of more than $7.9 billion in investment scam losses in 2025 alone, with cryptocurrency fraud being particularly damaging because transactions are irreversible.</p><p>The playbook is consistent. Scammers reach out through social media with “<strong>special opportunities”</strong> to invest in crypto. They guarantee big returns with little or no risk. They direct victims to a spoofed platform that looks legitimate. After extracting as much as possible, they shut down the site and disappear.</p><p><strong>Why this matters for investigators</strong>: Fake investment platforms leave domain registration trails, wallet addresses, and social media accounts that can be pivoted through Steps 1 through 5.</p><p><strong>How to protect yourself</strong>: No legitimate investment guarantees returns with no risk. All investments carry risk . Use<strong> </strong><a href="https://investor.gov/"><strong>Investor.gov</strong></a> to check whether anyone recommending investments is licensed and registered . Never let someone you met on social media direct your investment decisions.</p><h3>3. Romance and Friendship Scams</h3><p>Nearly 60 percent of people who reported losing money to a romance scam in 2025 said it started on social media . The scammer uses what is visible on your profile — your interests, your relationship status, your emotional vulnerabilities — to build a connection. Once trust is established, they invent a crisis that requires money .</p><p>Friendship and sweetheart scams carry a median loss of $15,000, making them the second most financially damaging category after investment fraud.</p><p><strong>Why this matters for investigators</strong>: Romance scams are the primary use case for everything in Step 1. Reverse image search, User ID extraction, and geolocation analysis are the tools that unmask the stolen photos and fabricated personas behind these operations.</p><p><strong>How to protect yourself</strong>: Limit who can see your posts and contacts on social media. Be suspicious of anyone who builds intense emotional connection quickly and then asks for money. The FTC warns that scammers may even use real photos of your friends or family members, sometimes enhanced with AI.</p><h3>4. Online Shopping and Non-Delivery Scams</h3><p>Shopping scams were the most reported scam on social media, with scammers posting ads offering high-priced items for cheap . Victims either never receive the item, or they receive a knockoff or something completely different from what was ordered .</p><p>Non-delivery scams — where you pay for goods or services you find online but never receive them — accounted for over $785 million in losses according to FBI data .</p><p><strong>Why this matters for investigators</strong>: Fake shopping sites are a goldmine for Steps 2 and 3. WHOIS data, domain age, SSL certificates, and the site’s structural patterns often reveal connections to broader scam networks.</p><p><strong>How to protect yourself</strong>: Before buying, search the company name plus “scam” or “complaint” . Research the seller through trusted review sites . Pay with a credit card, not bank transfer, and check out as a guest if possible.</p><h3>5. Imposter Scams (Government, Business, and Tech Support)</h3><p>Imposter scams are the number one scam category reported to the FTC . Scammers pretend to be from the government, your bank, a tech company, or someone you know. They create a sense of urgency — a fake transaction, a fake toll violation, a fake virus — and pressure you to act immediately.</p><p>Tech support impersonation alone caused over $1.46 billion in losses in 2024 . Business Email Compromise, where scammers impersonate executives or vendors to redirect payments, caused over $2.77 billion .</p><p><strong>Why this matters for investigators</strong>: Email header analysis in Step 5 is specifically designed to unmask spoofed senders in imposter scams. The “From” field lies, but the routing data does not.</p><p><strong>How to protect yourself</strong>: Never call back a number from an unexpected message or voicemail. Contact the organization through their official website or app . Government agencies will never demand immediate payment or ask for gift cards.</p><h3>6. Prize, Lottery, and Charity Scams</h3><p>Prize scams tell you that you have won something — a lottery, a sweepstakes, a grant — and then ask you to pay fees or taxes upfront to claim it . Charity scams exploit generosity, especially after disasters, by creating fake charities or impersonating real ones .</p><p><strong>Why this matters for investigators</strong>: These scams often use email addresses and phone numbers that are recycled across multiple campaigns. The Forgot Password technique and breach lookups in Step 5 can connect a single prize scam to a network of related operations.</p><p><strong>How to protect yourself</strong>: If you have to pay to receive a prize, it is not a prize. Government agencies do not call to demand money to collect winnings . For charities, verify the organization independently before donating.</p><h3>The Warning Signs</h3><p>Regardless of the scam type, certain patterns repeat. The FTC, CFPB, and international law enforcement agencies all point to the same red flags:</p><p><strong>Unexpected contact</strong>. Scammers reach out first. A call, text, or message you did not initiate is the first warning sign.</p><p><strong>Urgency and pressure</strong>. They tell you to act now, that the deal will not last, that your account will be frozen, that someone will be arrested. Urgency is a tactic to prevent you from thinking critically.</p><p><strong>Specific payment methods</strong>. Gift cards, wire transfers, cryptocurrency, and payment apps are preferred because they are hard to trace and hard to reverse. If someone says the only way to pay is one of these methods, it is a scam.</p><p><strong>Requests for personal information</strong>. Passwords, PINs, account numbers, Social Security numbers. Legitimate organizations do not ask for these in unsolicited messages.</p><p><strong>Emotional manipulation</strong>. Romance, fear, greed, sympathy. Scammers play on emotions because emotion overrides reason.</p><h3>Core Protection Principles</h3><p>The advice from every authoritative source converges on the same fundamental principles. I have distilled them into what I consider the six layers of scam prevention:</p><p><strong>Layer 1</strong>: Do not engage with unknown contacts. Never respond to calls, texts, or emails from people you do not know. Do not open attachments. Do not click links. Do not call numbers left in voicemails.</p><p><strong>Layer 2</strong>: Verify through official channels. If you think a message might be legitimate, contact the organization using a phone number or website you look up yourself. Never use the contact information provided in the suspicious message.</p><p><strong>Layer 3</strong>: Slow down. Scammers rely on speed. They want you to act before you think. Pause. Ask questions. Get information in writing. Talk to someone you trust.</p><p><strong>Layer 4</strong>: Limit what you share. Scammers use information from data brokers, social media, and breached databases to make their approaches convincing. The less you share publicly, the less they have to work with.</p><p><strong>Layer 5</strong>: Secure your accounts. Use strong, unique passphrases. Enable multi-factor authentication on every account that offers it. Keep software updated. These basic measures block the vast majority of automated attacks.</p><p><strong>Layer 6</strong>: Report and monitor. Report scams to the FTC at <a href="https://reportfraud.ftc.gov/">ReportFraud.ftc.gov</a> or your national equivalent. Regularly check your financial accounts and credit reports for discrepancies. Freeze your credit if you suspect identity theft.</p><h3>AI Face-Swapping Scam Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qkBU7CcWr_ESOYtipYLGzQ.png" /></figure><p>This is the evolution of impersonation. The scammer does not just steal a name and a profile picture. They steal a face and a voice. In a live video call, they appear as someone the victim trusts.</p><p>The technology is called deepfake, and it uses generative adversarial networks (GANs) to map a target’s face onto the scammer’s real-time video feed. The same technology clones voices. With a few seconds of audio from a social media video, the scammer can make the impersonated person say anything.</p><h4>How it works:</h4><p>The scammer gathers source material. Public videos, voice messages, video calls, even photos from social media. From this, they build a deepfake model of the target — a CEO, a family member, a police officer.</p><p>Then they initiate contact. It might be a video call claiming an emergency. “<strong>Dad, I’m in trouble</strong>. <strong>I need money urgently.</strong>” The face is the son’s face. The voice is the son’s voice. The urgency is manufactured.</p><p>Or it might be a business context. A “<strong>CEO</strong>” joins a video conference and instructs an employee to transfer funds for a confidential acquisition. The employee sees the CEO’s face and hears the CEO’s voice. They comply.</p><p>The scam works because humans trust what they see. A face is proof. A voice is proof. But in 2026, both can be fabricated.</p><h4>Practical example (from real cases):</h4><p>An 82-year-old man received a video call from someone who looked exactly like a famous tech billionaire. The “<strong>billionaire</strong>” pitched an investment opportunity. The man transferred over $690,000 of his retirement savings. The face was AI-generated. The investment platform was fake. The money was gone.</p><p>In another case, scammers impersonated university professors and used voice cloning to call students. “This is Professor X. I need you to help me with an urgent payment.” The students transferred money because the voice sounded real.</p><h4>How to detect a deepfake in a live call:</h4><p>Deepfakes still have tells. The technology is good, but it is not perfect.</p><h4>Visual tells:</h4><ul><li><strong>Lip-sync issues</strong>. Even top-tier deepfakes have a slight delay between speech and lip movement. A hundred milliseconds is noticeable. Look for irregular lip shapes when pronouncing M, F, or T sounds</li><li><strong>Blinking patterns</strong>. Real people blink 10–20 times per minute. Deepfakes often blink too rarely, too often, or asynchronously — one eye not matching the other.</li><li><strong>Hairline blurring</strong>. The edge where the cloned face meets the original head often shows blurring, flickering, or unnatural color transitions.</li><li>Lighting inconsistencies. The direction of shadows on the face may not match the background. Glare on the skin may look unnatural or absent.</li><li><strong>Static or blurred background</strong>. The background may not respond to movement naturally. It might be frozen or blurred in a way that does not match a real environment.</li><li><strong>Odd facial expressions</strong>. Deepfakes struggle with emotion. Smiles look frozen. Fine wrinkles that appear when expressing emotion are absent. The face looks “botoxed”</li></ul><h4>Audio tells:</h4><ul><li><strong>Wooden or electronic tone</strong>. The voice may lack natural intonation variations. It might sound flat or slightly mechanical.</li><li><strong>Choppy speech or odd pauses</strong>. Background noise that does not match the visual environment. Audio dropouts that seem suspicious.</li></ul><h4>Behavioral tells:</h4><ul><li><strong>Refusal to do spontaneous gestures</strong>. Ask them to touch their left ear, wave their hand in front of their face, or turn their head quickly. Deepfakes often glitch when processing rapid movements or facial occlusion.</li><li><strong>Pre-arranged calls only</strong>. If the person always schedules calls in advance and never accepts spontaneous video requests, they may need time to prepare the deepfake overlay.</li><li><strong>Refusal to answer personal questions</strong>. Ask something only the real person would know. A childhood nickname. A shared secret. A specific memory. The AI cannot answer this</li></ul><h4>Defense mechanisms:</h4><ul><li><strong>Request gesture verification</strong>. “Touch your left ear right now.” “Wave your hand in front of your face.” AI struggles with occlusion and rapid movement.</li><li><strong>Ask a personal verification question</strong>. Something that is not on social media. Something only the real person would know.</li><li><strong>Hang up and call back</strong>. Use the contact information you already have for that person. Do not call the number they provided. Call the number in your contacts.</li><li><strong>Use a second communication channel</strong>. If they called on WhatsApp, call their regular phone number. If they video-called, send a text to their verified number.</li><li><strong>Limit your public video and voice footprint</strong>. The less source material you provide, the harder it is to clone you. Adjust your social media privacy settings. Be careful what you post.</li></ul><h3>Why This Matters for Scammer Investigations</h3><p>Understanding scam types is not just about prevention. It is about pattern recognition.</p><p>Before you investigate a scammer, identify their category first. <strong>Is this an investment scam? A romance scam? A phishing operation?</strong> That tells you what infrastructure to look for. Investment scams leave wallet addresses and fake platform domains. Romance scams leave stolen photos and dating app profiles. Phishing scams leave email headers and spoofed URLs.</p><p>The scam type is the starting point. The methodology in the following steps is how you trace it back to the actor behind it.</p><blockquote><strong>A note on sources</strong>: The data in this section draws from the FTC, CFPB, FBI, European Banking Authority, and international fraud prevention organizations. The statistics are current as of the most recent reports available. Scam tactics evolve constantly, but the underlying patterns remain remarkably consistent.</blockquote><h3>The investigation methodology</h3><h4>Before investigating a scammer, your first questions should be:</h4><ul><li>What was the pretext? (<strong>romance, investment, job offer, sextortion</strong>)</li><li>What was the contact vector? (<strong>email, SMS, social media, dating app</strong>)</li><li>What was the financial mechanism? (<strong>crypto wallet, bank transfer, gift card</strong>)</li><li>What digital artifacts did they leave behind? (<strong>domains, phone numbers, images, wallet addresses</strong>)</li></ul><p>Without answering these first, the investigation has no direction.</p><h3>Step 1: Reverse Image Search</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVvYftQiFPgrkBSeDcHWQA.png" /></figure><p>Most scam operations reuse stolen photos. The “<strong><em>beautiful woman</em></strong>” on the dating app, the “<strong><em>successful crypto trader</em></strong>” on LinkedIn, the “c<strong><em>ompany executive</em></strong>” in the email signature — these images are often lifted from other people or AI-generated.</p><h4>What you do:</h4><p>Start with Google Images, Yandex, and TinEye. Upload the profile photo or the image from the scam website. Look for exact matches, visually similar matches, and the earliest appearance of that image.</p><p><strong>Why Yandex matters</strong>: Yandex is significantly better than Google at facial recognition and Eastern European sources. If the scammer lifted a photo from a Russian or Ukrainian social media account, Yandex will find it.</p><h4>What you look for:</h4><ul><li>The same image appearing on multiple profiles with different names</li><li>The original source: a legitimate Instagram model, a stock photo site, a random person’s Facebook page</li><li>The earliest date the image appeared online</li></ul><p><strong>Tools</strong>: Google Images, Yandex Images, TinEye, Bing Visual Search.</p><p><strong>Documentation 1</strong>: Take screenshot of every match with the URL visible</p><p>Archive the source page using <a href="https://archive.today/"><strong>archive.today</strong></a> or the <strong>Wayback Machine</strong>. Log the timestamp.</p><p><strong>Documentation 2: </strong>Extracting and Preserving the User ID</p><p>Reverse image search tells you the photo is stolen. But the profile itself — the account the scammer is operating — can disappear the moment they change their username or delete the account. The User ID is the anchor. Unlike the username, which is just a display label, the User ID is a numeric identifier assigned at account creation. It never changes. Even if the scammer renames their profile ten times, the User ID remains constant.</p><p>So after you have confirmed the image is stolen, immediately extract the User ID from every social profile the scammer uses. This is your insurance policy against account renaming.</p><h4>Extracting the User ID: Using Facebook as an Illustration</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bUt9DLCY2vGUV7FTDQHxbQ.png" /></figure><p>Facebook has two types of profile URLs: vanity URLs (e.g., <strong>facebook.com/john.smith.123</strong>) and numeric IDs (e.g., <strong>facebook.com/profile.php?id=100094902271869</strong>). The numeric ID is the permanent identifier.</p><h4>Method 1: Manual Source Code Analysis</h4><p>Open the scammer’s Facebook profile in a browser. Right-click and select View Page Source (Ctrl+U on Windows, Cmd+Option+U on Mac). Then you search the source code for the string <strong>&quot;userID&quot;</strong>. Facebook embeds the numeric ID in the page source, typically in a format like <strong>&quot;userID&quot;:&quot;100094902271869&quot;</strong></p><p>Copy that number. Save it in your case file alongside the profile URL, the username, the date and time of extraction, and a screenshot of both the profile and the source code.</p><p><strong>Method 2: URL Parsing</strong></p><p>If the profile URL already contains <strong>profile.php?id=</strong>, extract the number directly from the URL. That is the User ID.</p><h4>Method 3: Third-Party Tools (for efficiency and corroboration)</h4><p>For a quick one-off, <a href="https://lookup-id.com/"><strong>Lookup-ID.com</strong></a> is a straightforward web tool that accepts a Facebook URL and returns the numeric ID.</p><h4>Why the User ID matters for your investigations:</h4><p>Once you have the User ID, you can use it to search for the scammer’s internal data even if their username changes. Tools like <strong>Who Posted What</strong> use the User ID to search for posts from a specific account within a date range, which is invaluable for building a timeline of the scammer’s activity .</p><h4>Validating the User ID</h4><p>Extracting the ID is step one. Validation is step two. Never trust a single extraction method.</p><h4>Validation method 1: Cross-reference with a second tool</h4><p>If you extracted the ID from the page source, run the same profile through Apify or a browser extension. If both return the same numeric ID, you have high confidence.</p><h4>Validation method 2: Facebook customized UserID to username Resolver</h4><p>Aside using the automated tool, you can use the the numeric ID directly in the URL like this:</p><pre>https://facebook.com/profile.php?id=&lt;UID&gt;</pre><p><strong>Or even just</strong>:</p><pre>https://facebook.com/&lt;UID&gt;</pre><p><strong>For example, using John’s ID</strong>:</p><pre>https://facebook.com/61593163516523</pre><p>This automatically redirects to the scammer’s profile on Facebook. The numeric ID is the permanent, underlying identifier, and the vanity username is just a display layer on top of it.</p><h3>Documenting the User ID in the Case File</h3><p>For each profile, you log:</p><ul><li><strong>Platform</strong>: Facebook or Instagram</li><li><strong>Profile URL at time of extraction</strong>: (e.g., instagram.com/scammer.handle)</li><li><strong>Current username</strong>: (e.g., @scammer.handle)</li><li><strong>Numeric User ID</strong>: (e.g., 1234567890)</li><li><strong>Extraction method</strong>: (manual source code, tool name, script)</li><li><strong>Extraction timestamp</strong>: (date and time, with timezone)</li><li><strong>Validation method</strong>: (second tool used, reverse lookup result)</li><li><strong>Former usernames</strong> (if available): with dates</li><li><strong>Screenshot of profile</strong>: archived</li><li><strong>Screenshot of source code or tool output</strong>: archived</li><li><strong>Archived URL</strong>: <a href="https://archive.today/">archive.today</a> or Wayback Machine snapshot</li></ul><p>This documentation ensures that even if the scammer deletes the account or changes the username tomorrow, you have a permanent record of the profile as it existed during your investigation. The User ID is the thread you can pull to reconnect the investigation if the scammer resurfaces under a new name.</p><h3>Why This Matters for Scammer Investigations</h3><p>Scammers are acutely aware that their usernames are searchable. A simple Google search of their handle can reveal forum posts, victim reports, and OSINT investigations. Their countermeasure is to change the username regularly. The User ID defeats this evasion tactic.</p><p><strong>Critical note</strong>: A reverse image match does not prove the scammer’s identity. It proves the image is stolen. This is a lead, not a conclusion .</p><blockquote><em>To go deeper into the methodology behind social media attribution and platform enumeration, I have shared my full workflow in a free course,</em><strong> The Professional OSINT Practitioner</strong> — <em>you can read it here:</em> <a href="https://d4rkintel.substack.com/p/the-professional-osint-practitioner"><strong><em>https://d4rkintel.substack.com/p/the-professional-osint-practitioner</em></strong></a></blockquote><h3>Step 2: Scamming Website Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BeYaaMbLhZlaN7gYIUuCoQ.png" /></figure><p>If the scam involved a website — fake investment platform, fraudulent e-commerce store, phishing page — that domain is a goldmine of infrastructure data.</p><h4>What you do:</h4><p>Start with WHOIS lookup. Look for:</p><ul><li><strong>Registration date</strong> (scam sites are often registered recently)</li><li><strong>Registrar</strong> (some registrars are favored by fraudsters for anonymity)</li><li><strong>Registrant details</strong> (often redacted, but sometimes not)</li><li><strong>Name servers</strong></li></ul><p>Then check DNS history. Domains that have changed hands or been repurposed leave traces. SecurityTrails and Complete DNS show historical records .</p><p>Use the Wayback Machine. If the site has been taken down, archived versions may still show the original content, contact details, and wallet addresses.</p><p>Look at the site’s structure. Does it use a free website builder (Wix, Squarespace)? Does it reuse templates from known scam kits? Does the “<strong>About Us</strong>” page have stock photos that reverse image search reveals?</p><p><strong>Tools</strong>: WHOIS lookup tools, SecurityTrails, crt.sh, Censys, Wayback Machine, <a href="https://urlscan.io/">urlscan.io</a>, Virustotal.</p><p><strong>Documentation</strong>: Archive every page. Take screenshot of WHOIS results. Export DNS records. Calculate hashes where applicable.</p><h3>Step 3: Geolocation and Real Name Identity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mSFWpDXagbPceCVtzX0PZA.png" /></figure><p>Scammers hide their location and real identity, but they leave this in exif signals. Sometimes intentionally, sometimes not.</p><h4>What you do:</h4><p><strong>EXIF metadata</strong>: If the scammer uploaded an image directly from a phone, the EXIF data may contain GPS coordinates and their real identity (name). ExifTool is your standard here. Most social media platforms strip EXIF, but email attachments, forums, and direct website uploads often do not .</p><p><strong>Photo analysis</strong>: If EXIF is stripped, analyze the image content. <em>Shadows, architecture, vegetation, street signs</em>, and <em>license plates </em>can narrow a location. SunCalc helps verify shadow direction and time of day.</p><p><strong>Social media check-ins</strong>: If the scammer has a social media presence, check for tagged locations, check-ins, and geotagged posts that may reveal their connected real account. Even deleted posts may be archived.</p><p><strong>Phone number geolocation</strong>: Truecaller (for those living in Nigeria) and similar tools can reveal the country and carrier associated with a number. This is not precise location, but it narrows the region.</p><p><strong>Timezone analysis:</strong> When does the scammer post? When do they respond? Activity patterns often correlate with work hours in a specific timezone. Log message timestamps and look for patterns.</p><p><strong>Tools</strong>: ExifTool, Truecaller, SunCalc, Google Earth, PhoneInfoga, social media geolocation archives.</p><p><strong>Caution</strong>: Geolocation from a single artifact is weak. You need corroboration from multiple independent sources before asserting a location</p><h3>Step 4: Phishing Link Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zh3nN7NL6rRph4JW9kps3w.png" /></figure><p>If the scam involved a link — phishing page, fake login portal, malicious download — that link is a vector to the infrastructure.</p><h4>What You do:</h4><p>Never click links directly. Use<strong> </strong><a href="https://urlscan.io/"><strong>urlscan.io</strong></a> or <strong>VirusTotal</strong> to scan the URL. These tools render the page in a sandbox and capture screenshots, redirects, and network requests.</p><p>Expand shortened URLs. Bitly, TinyURL, and other shorteners hide the destination. Use URL expander tools or simply append a “+” to the Bitly link to see statistics and destination.</p><h4>Example:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fK8MpzazCdCsNa7E-BDTvA.png" /></figure><p>Original shortened link:</p><pre>https://bit.ly/3xYz***</pre><p>Modified to reveal destination and stats:</p><pre>https://bit.ly/3xYzA***+</pre><p>When you append the “<strong>+</strong>”, Bitly redirects you to its own analytics page for that link. This page shows you:</p><ul><li>The destination URL (where the link actually points)</li><li>Creation date (when the link was generated)</li><li>Referrers (where the clicks came from)</li></ul><p>For an investigator, this is intelligence gold. A link created three days ago with 12,000 clicks tells you this is an active, spreading campaign. The destination URL gives you the domain to investigate next. The referrer data shows you which platforms the scammer is targeting.</p><p><strong>Important caveat</strong>: The Bitly “+” trick only works on Bitly links (<strong>bit.ly, </strong><strong>j.mp, </strong><strong>bitly.com</strong>). It does not work on TinyURL, Rebrandly, or other shorteners. For those, you need a general URL expander tool.</p><h4>General URL expanders:</h4><p>For any shortened link — TinyURL, <a href="https://ow.ly/">Ow.ly</a>, <a href="https://short.io/">short.io</a>, Rebrandly, custom shorteners — Use dedicated expansion tools:</p><ul><li><strong>CheckShortURL</strong> — supports hundreds of shorteners</li><li><strong>URLExpander </strong>— fast and simple</li><li><strong>WhereGoes </strong>— shows the full redirect chain, not just the final destination</li></ul><p><strong>WhereGoes</strong> is particularly useful because it shows you every step in the redirect chain. Scammers often route through multiple shorteners and redirects to obscure their final destination. Each hop may reveal additional domains and infrastructure.</p><p>Analyze the redirect chain. Phishing pages often redirect multiple times before landing on the final page. Each redirect may reveal additional domains and infrastructure.</p><p>Check the domain against phishing databases. <strong>PhishTank</strong>, <strong>OpenPhish</strong>, and <strong>Google Safe Browsing</strong> maintain lists of known phishing domains.</p><p>Extract the page source. If the phishing page mimics a legitimate brand, the source code may contain comments, API keys, or form submission endpoints that reveal the attacker’s infrastructure.</p><p><strong>Tools</strong>: <a href="https://urlscan.io/">urlscan.io</a>, VirusTotal, Bitly “+” trick, CheckShortURL, WhereGoes, URL expanders, PhishTank, OpenPhish.</p><p><strong>Documentation</strong>: Capture the full redirect chain, screenshots of each page, and the final destination URL. I archive everything.</p><h3>Step 5: Email and Phone Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zsq41P0xwpDle-OZo3TmmA.png" /></figure><p>Email addresses and phone numbers are often the only direct contact points with the scammer.</p><h3>Email Analysis:</h3><p>Extract full email headers. The “<strong>From</strong>” field is trivially spoofed, but the headers contain the actual sending infrastructure: originating IP, mail server, and authentication results (SPF, DKIM, DMARC). Use tools like <strong>MXToolbox</strong> or manual header analysis.</p><p>Check the email against breach databases and email reverse intelligence tools like<strong> Intelbase, Fingerprint, OSINT Industries.</strong>, etc. <strong>Have I Been Pwned</strong> and <strong>DeHashed </strong>reveal whether the email was exposed in previous data breaches. This can link the scammer to other accounts and platforms that form a true intelligence collection on their real identity.</p><p>Use tools like <strong>Holehe, BehindTheEamil, OSINT Industries, etc </strong>to check which platforms the email is registered on. This reveals the scammer’s digital footprint across services.</p><h4>The Forgot Password Technique: Turning Account Recovery Into Intelligence</h4><p>Breach databases and email headers are your first pass. They give you the skeleton. But there is a second technique that fills in the flesh, and it is one of the most underrated tools in scammer investigations: the <strong>Forgot Password technique</strong>.</p><p>I call it a technique, but it is really just a disciplined reading of what platforms voluntarily show you before you authenticate. Every major platform — Facebook, Instagram, LinkedIn, X, Snapchat, TikTok — has a password reset flow. When you enter an email address, the platform tells you whether that email is registered. It does this to help the legitimate user recover their account. You are simply observing what the platform displays.</p><p><strong>Why this matters in scammer investigations</strong>: Scammers lie about who they are. They use fake names, stolen photos, and disposable emails. But the platforms behind those accounts do not lie. When Facebook says, “We can send a code to <strong>j*****e@yahoo.com”</strong> or shows a profile picture and display name, that is Facebook confirming the account exists and revealing a partial recovery vector. That is not a guess. That is platform-verified intelligence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04Xt1YtTuW4XMphqKx1B_A.png" /></figure><p><strong>The key operational principle</strong>: You never click the verification link. You never reset the password. You never access the account. You only observe the response. This keeps you within legal and ethical boundaries while still extracting actionable data.</p><h4>Practical Example: The Breach-to-Reset Pipeline</h4><p>Let me walk you through a real investigative flow.</p><p><strong>Point A</strong> — Breach Lookup Reveals a Partial Identity</p><p>You run the scammer’s email, <strong>shadow.trader88@protonmail.com</strong>, through Have I Been Pwned and DeHashed. The breach data returns a hit. The compromised account is tied to a <strong>Facebook account </strong>with a partial name: &quot;<strong>Marcus T</strong>.&quot;</p><p><strong>Point B</strong> — Forgot Password Technique on Facebook</p><p>You go to <strong>facebook.com/login/identify</strong>. Enter <strong>shadow.trader88@protonmail.com.</strong>click Continue.</p><p><strong>Facebook responds with a recovery screen showing</strong>:</p><ul><li>A real profile picture</li><li>A display name: “Marcus Thompson”</li><li>A partially redacted recovery email: <strong>m*****t@gmail.com</strong></li><li>A partially redacted phone number: <strong>+1 ******47</strong></li></ul><p>You have not triggered a notification. The scammer has no idea you ran this. But you now have a full display name, a second email fragment, and a phone number fragment.</p><p>Take <strong>m*****t@gmail.com</strong> and reason: &quot;<strong>Marcus Thompson</strong>&quot; starts with <strong>M </strong>and ends with <strong>T</strong>. The recovery email likely follows the same pattern. Utilize a simple email permutation technique &gt; <strong>marcus.thompson@gmail.com</strong>, <strong>m.thompson@gmail.com</strong>, and <strong>marcust@gmail.com</strong> through the same breach databases. One of them might returns hit directly to the scammer’s hidden main entity.</p><p>Now you have a professional profile &gt; a real name &gt; a corporate footprint.</p><p><strong>This is the pipeline</strong>: Breach data gives you a fragment. Forgot Password gives you the platform. Platform response gives you the name. Name gives you the next pivot.</p><h3>LinkedIn Origin: Mapping Contact Details</h3><p>If the scammer’s footprint traces back to a LinkedIn profile, you have a different set of tools at your disposal. LinkedIn is a professional network, and professional networks are contact-rich.</p><p><strong>SignalHire </strong>and <strong>ContactOut </strong>are your primary tools here. Both are designed for recruiters and sales teams, but their capabilities translate directly into OSINT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y9dGl__3JcHPHeiw8fO69w.png" /></figure><p><strong>SignalHire</strong> maintains a database of over 850 million profiles with verified email and phone data. For a LinkedIn profile, it can return:</p><ul><li>Business emails (company domain-based)</li><li>Personal emails (Gmail, Yahoo, Rocketmail, etc.)</li><li>Phone numbers (mobile and workplace)</li><li>Current and historical job titles</li></ul><p><strong>ContactOut</strong> works similarly, with a database of 350 million profiles. Its Chrome extension can extract contact details directly from a LinkedIn profile page, and its API supports reverse lookups from email or phone back to a profile.</p><h4>How you use these tools in a scammer investigation:</h4><ol><li>Take the suspected name or email fragment from the Forgot Password technique.</li><li>Search SignalHire or ContactOut for that identity on LinkedIn.</li><li>If a match is found, extract the verified email and phone number.</li><li>Run those new identifiers through breach databases and Forgot Password checks on other platforms.</li><li>Each new contact point becomes a pivot to another platform, another account, another fragment of identity.</li></ol><p><strong>Important caveat</strong>: These tools are commercial products built for sales and recruiting. They are not designed for law enforcement or legal attribution. Their data is aggregated from public sources, but accuracy varies. Treat their output as leads, not conclusions. Corroborate every finding with a second source before you assert it in a report.</p><h3>GitHub Commit Email Analysis</h3><p>If the scammer has any technical footprint — and many do, especially those running phishing infrastructure or crypto scams — GitHub is a goldmine. Every Git commit carries an author email. Every public repository exposes the commit history.</p><h4>How you extract it:</h4><p>Identify the scammer’s GitHub username from other pivots (a personal website’s source code, a forum signature, a leaked config file). Then, pull their commit history.</p><p><strong>Navigate to</strong>:</p><pre>https://api.github.com/repos/[owner]/[repo]/commits</pre><p>Replace <strong>[owner]</strong> with the username or organization name, and <strong>[repo]</strong> with the repository name.</p><p><strong>Example</strong>:</p><pre>https://api.github.com/repos/techenthusiast167/WebRecon/commits</pre><p>This opens a raw JSON page containing every commit on the default branch. The page is plain text, but all the data is there.</p><h4>What the commit emails tell you:</h4><p>The email in a commit is the email the developer configured locally. It might be:</p><ul><li>A personal email (<strong>marcust@gmail.com</strong>)</li><li>A work email (<strong>marcus@fakecompany.com</strong>)</li><li>A noreply GitHub address (<strong>12345+username@users.noreply.github.com</strong>)</li></ul><p>If it is a real email, you now have a direct identifier tied to a specific GitHub account. Run it through breach databases. Check it on other platforms via Forgot Password and reverse email lookup. Look for the same email in other repositories across GitHub.</p><h3>The Integrated Workflow</h3><ol><li>Start with<strong> breach lookup</strong> on the <strong>known email.</strong> Extract any partial identities, usernames, or platforms revealed.</li><li>Run <strong>Reverse email lookup</strong> and <strong>Forgot Password technique </strong>on that<strong> email across major platforms</strong> (Facebook, Instagram, LinkedIn, X) to confirm account existence and extract display names, profile pictures, and recovery fragments.</li><li>If LinkedIn is confirmed, use <strong>SignalHire</strong> or <strong>ContactOut </strong>to extract verified emails and phone numbers from the professional profile.</li><li>Run those new emails through breach databases and Forgot Password checks on other platforms. Repeat until the identity loop closes or you exhaust the pivots.</li><li>If GitHub is in the footprint, extract <strong>commit emails </strong>and cross-reference them against the emails you have already collected.</li></ol><p>The goal is a chain of small confirmations, each one tightening the noose around the scammer’s real identity. The Forgot Password technique is the quiet workhorse of that chain. It does not alert the target. It does not violate platform terms. It simply reads what the platform already shows you.</p><p>And in scammer investigations, the quiet techniques are often the ones that work.</p><h3>Phone Analysis:</h3><p>Phone numbers are the connective tissue of digital identity. A scammer can change their username, their email, their profile picture, and even their narrative. But a phone number is harder to abandon. It is tied to verification codes, two-factor authentication, and contact syncing across every major messaging platform. When you have a phone number, you have a pivot point that can unlock a network of accounts the scammer thought were separate.</p><p><strong>Your phone analysis workflow has three layers</strong>: technical validation, platform mapping, and reverse lookup. Move through them in sequence, documenting every finding and preserving every artifact.</p><h3>Layer 1: Technical Validation with TrueCaller / PhoneInfoga</h3><p>Start with <strong>TrueCaller / PhoneInfoga</strong>. It is the most advanced open-source tool for scanning international phone numbers using only free resources. Run the number through them and extract three critical data points:</p><p><strong>Country and area code</strong>: This tells you where the number was issued. Not where the scammer is located, but where the number originates. A US number does not most times mean the scammer is in the US. Sometimes, it means they bought a US number.</p><p><strong>Carrier</strong>: This identifies the telecommunications provider. Some carriers are more popular with scammers than others because they offer cheap, disposable numbers.</p><p><strong>Line type</strong>: This is the most important field. TrueCaller / PhoneInfoga tells you whether the number is a mobile line, a landline, or a VoIP number.</p><p><strong>VoIP numbers</strong> are heavily favored by scammers because they are cheap, disposable, and difficult to trace. <strong>Google Voice, TextNow</strong>, and <strong>Twilio </strong>are the usual suspects. A VoIP number tells you the scammer is operating with some level of operational security awareness. It does not tell you who they are, but it tells you they took steps to hide.</p><p><strong>TrueCaller</strong> / <strong>PhoneInfoga </strong>also performs OSINT footprinting by checking the number against external APIs, phone books, and search engines. This can surface reputation reports, social media associations, and attach email address.</p><p><strong>Important limitation</strong>: TrueCaller / PhoneInfoga does not track a phone or its owner in real time. It does not provide precise location. It does not hack anything . It validates and enriches. Nothing more.</p><p><strong>Document the TrueCaller / PhoneInfoga output as structured data</strong>: country, carrier, line type, reputation flags, and any associated footprints.</p><h3>Layer 2: Contact Syncing for Platform Mapping</h3><p>If TrueCaller / PhoneInfoga confirms the number is real — not a known disposable VoIP service — pivot to contact exploitation. This is the technique of saving the target number to a clean device or emulator, then syncing it against messaging platforms that offer “<strong>Find Friends</strong>” functionality.</p><h3>Why This Works</h3><p>Every major messaging platform has a feature that lets users discover contacts by uploading their address book. When you save a number to your phone and grant the app access to your contacts, the app compares that number against its registered user database. If the number is linked to an account, the platform surfaces that account.</p><p>Most scammers are dumb AF! They do not know this is happening. The platform do not notify them. The sync is passive. You are simply reading what the platform already knows.</p><h3>The Setup</h3><p>Use a clean Android emulator or a dedicated investigation device. No personal contacts. No personal accounts. Save the target phone number as a contact. Format it correctly, including the country code.</p><p>Then install the target platforms — WhatsApp, Telegram, Snapchat — and grant each one access to your contacts. Wait for the sync to complete. Then you check the friend suggestions or contact matches for any intelligence collection.</p><h3>What Each Platform Reveals</h3><p><strong>WhatsApp</strong>: When you save a number and sync, WhatsApp displays the account associated with that number if it exists. You see the profile picture, the display name, and the “<strong>About</strong>” status . This is direct identity mapping. The scammer’s WhatsApp profile may not match their Facebook profile, but if it does, you have a confirmed link between two platforms.</p><p><strong>Telegram</strong>: Telegram imports contacts by phone number using the <strong>contacts.importContacts</strong> method. If the number is registered, Telegram returns the user&#39;s profile information . You see their display name, username (if they have one), and profile picture. Telegram also allows you to add contacts without actually using their phone number, which can be useful for deeper enumeration.</p><p><strong>Snapchat</strong>: Snapchat’s Find Friends feature matches uploaded contacts against its user database. If the number is linked to a Snapchat account, the account appears in your friend suggestions . Snapchat does not display the phone number to other users, but it does surface the account . <strong>One caveat</strong>: Snapchat users can disable the “<strong>Let others find me using my mobile number</strong>” setting, which prevents their account from appearing through contact sync.</p><h3>Documenting the Results</h3><p>For each platform where the number produces a match, log:</p><ul><li>Platform name and user ID</li><li>Display name associated with the number</li><li>Username (if visible)</li><li>Profile picture (screenshot and reverse image search)</li><li>Any other visible profile data (bio, status, last seen)</li></ul><p>Then, you cross-reference. If the display name on WhatsApp matches the name fragment from your email investigation, that is corroboration. If the profile picture on Telegram matches the stolen image you flagged in Step 1, that is a confirmed link. If the Snapchat account is a dead end, you note it and move on.</p><h3>Layer 3: Forgot Password Technique on Facebook</h3><p>Phone numbers work for the Forgot Password technique exactly the same way emails do. And in scammer investigations, this is often the most direct path to a real identity.</p><p>Go to Facebook’s login page and click “<strong>Forgot Password</strong>” . Enter the phone number with the country code. Facebook searches its database.</p><p>If the number is linked to an account, Facebook displays a recovery screen showing:</p><ul><li>Partial name (e.g., <strong>“Marcus T</strong>.”)</li><li>Profile picture</li><li>Partially redacted recovery email (e.g., <strong>m*****t@gmail.com</strong>)</li><li>Partially redacted phone number (if different)</li></ul><p>If the number is not linked, Facebook says “<strong>No account found</strong>”</p><p><strong>Why this matters</strong>: The Forgot Password technique is passive. You do not click any verification link. You do not reset any password. You do not trigger any notification. You simply read what Facebook shows you before you authenticate . The scammer has no idea you ran the check.</p><h3>Google Dorks for Phone Number Lookup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*idPNO0oIjZcBL10e_6EDYg.png" /></figure><p>Search engines index more than people realize. Phone numbers appear in forum posts, business directories, leaked documents, social media bios, and cached pages. A well-crafted Google dork can surface those mentions.</p><p><strong>Basic search</strong>: Enclose the number in quotation marks to force an exact match.</p><pre>&quot;123-456-7890&quot;</pre><p><strong>Format variations</strong>: Phone numbers appear in multiple formats. Run each variation separately.</p><pre>&quot;(123) 456-7890&quot;<br>&quot;1234567890&quot;<br>&quot;+1 123 456 7890&quot;<br>&quot;123.456.7890&quot;</pre><p><strong>Site-restricted search</strong>: If you suspect the number is associated with a specific platform or organization, I restrict the search.</p><pre>site:facebook.com &quot;123-456-7890&quot;<br>site:linkedin.com &quot;1234567890&quot;<br>site:pastebin.com &quot;123-456-7890&quot;</pre><p><strong>File type filtering</strong>: Phone numbers often appear in documents, spreadsheets, and PDFs. Use <strong>filetype</strong>: to target those formats.</p><pre>filetype:pdf &quot;123-456-7890&quot;<br>filetype:xlsx &quot;1234567890&quot;<br>filetype:doc intext:&quot;123-456-7890&quot;</pre><p><strong>Combining operators</strong>: The real power comes from stacking filters. If you have a partial name from the Forgot Password technique and a phone number, you combine them.</p><pre>&quot;Marcus Thompson&quot; &quot;123-456-7890&quot;<br>&quot;Sarah M&quot; &quot;+1 123 456 7890&quot;</pre><p><strong>Forum and paste site targeting</strong>: Scammers and their victims often post numbers on forums, complaint sites, and paste bins. I target those domains specifically.</p><pre>site:reddit.com &quot;123-456-7890&quot;<br>site:pastebin.com &quot;123-456-7890&quot;<br>site:ripoffreport.com &quot;123-456-7890&quot;</pre><p><strong>What you are looking for</strong>: Any mention of the number that connects it to a name, a business, a location, or another online identity. A single forum post can break an investigation open.</p><h3>The Phone Analysis Workflow</h3><p>Here is the sequence you follow:</p><ol><li><strong>TrueCaller / PhoneInfoga scan</strong>: Extract country, carrier, line type, and any reputation flags.</li><li><strong>Contact sync</strong>: Save the number to a clean device. Sync it across WhatsApp, Telegram, and Snapchat. Document any matches.</li><li><strong>Forgot Password check</strong>: Run the number through Facebook’s recovery flow. Extract name fragments, profile pictures, and recovery email fragments.</li><li><strong>Google dork</strong>: Search the number in multiple formats across general web, social media, forums, and file-sharing sites.</li><li><strong>Cross-reference</strong>: Match findings against data from email analysis, breach lookups, and reverse image search.</li><li><strong>Document</strong>: Log every platform, every result, every timestamp. Archive everything.</li></ol><p>The phone number is not the end of the investigation. It is a bridge between platforms. When you have a phone number, you have a way to connect the scammer’s Facebook identity to their WhatsApp account, their Telegram account to their Snapchat account, and all of it to a real name and email address. That is the goal of phone analysis. Not the number itself, but the network it unlocks.</p><h3>Step 6: Logical Correlation and Validation</h3><p>This is where the investigation becomes intelligence. Individual data points are not conclusions. You need to connect them, test them, and validate them.</p><h3>What you do:</h3><p><strong>Build a timeline</strong>. Every artifact has a timestamp. Domain registration dates, email sending times, phone activity, social media posts. Plot these on a timeline and look for patterns .</p><p><strong>Create a relationship map</strong>. Maltego is your tool of choice for visualizing connections between entities: email addresses, phone numbers, domains, wallet addresses, social media profiles. Look for clusters and shared attributes.</p><p>Apply the<strong> Analysis of Competing Hypotheses</strong> (ACH) method. Generate multiple explanations for the evidence. For each hypothesis, you ask:<strong> what evidence would be inconsistent with this</strong>? Eliminate hypotheses that contradict the evidence.</p><p><strong>Validate with independent sources</strong>. A single source is never enough. If you believe a phone number is linked to a specific person, you need corroboration from at least two independent sources. Shared infrastructure alone does not prove ownership .</p><p>Use calibrated confidence language. In your reports, distinguish between:</p><ul><li><strong>Confirmed</strong>: Multiple independent sources, high confidence</li><li><strong>Probable</strong>: Strong evidence, but some gaps</li><li><strong>Possible</strong>: Some evidence, but significant uncertainty</li><li><strong>Unknown</strong>: Insufficient evidence</li></ul><p><strong>Tools</strong>: Maltego, Excel/Google Sheets for timelines, ACH methodology, OSINT Forge for evidence preservation.</p><h3>A Note on Operational Security</h3><p>Never investigate from your personal accounts. Use burner emails, VPNs, virtual machines, and dedicated research personas. Never interact with the scammer unless authorized and under controlled conditions. Strip metadata from any files you share. Encrypt your case files .</p><p>The scammer may be watching. Your OPSEC is not optional!</p><h3>What You Produce</h3><p>At the end of an investigation, produce a structured report:</p><ul><li><strong>BLUF (Bottom Line Up Front)</strong>: The key finding in one paragraph</li><li><strong>Key Judgments</strong>: What you assess with confidence</li><li><strong>Evidence</strong>: Every artifact, preserved and referenced</li><li><strong>Analysis</strong>: How you connected the dots</li><li><strong>Alternatives</strong>: What you considered and rejected</li><li><strong>Implications</strong>: What this means for the client or case</li><li><strong>Outlook</strong>: What is likely to happen next</li></ul><p>The report is evidence-backed, reproducible, and calibrated. It is not a collection of screenshots. It is intelligence!</p><h3>A Note on Expectations: OSINT Is Not Magic</h3><p>I need to be honest with you about something.</p><p>You can follow every step in this framework. You can run the reverse image searches, extract the User IDs, analyze the headers, pivot through the Forgot Password technique, correlate the phone numbers, and build the relationship map. And you might still come up empty.</p><blockquote>That is not failure. That is the nature of the work.</blockquote><p><strong>OSINT is not a magic wand</strong>. It is not a single tool that spits out an answer. It is a discipline. And like any discipline, it has limits.</p><p>Sometimes the data is not there. The scammer used a stolen photo that was never indexed by any search engine. The email was created on a privacy-focused provider with no breach history. The phone number was a disposable VoIP line that was deactivated last week. The domain was registered behind privacy protection with a cryptocurrency payment. Every trail is cold because the scammer covered their tracks — or because they simply got lucky.</p><p>Sometimes the data is there, but it does not connect. You have a phone number. You have an email. You have a profile picture. But none of them link to each other. They are fragments floating in isolation, and no amount of correlation reveals a pattern because there is no pattern to find. The scammer may have used entirely separate infrastructure for each phase of the operation.</p><p><strong>Sometimes you need patience</strong>. This is the hardest lesson. Investigations are not solved in an hour. They are built over days, weeks, sometimes months. A new breach surfaces. A domain registration expires and the WHOIS history becomes visible. The scammer makes a mistake — reuses a username, posts from a location they did not intend to reveal, contacts a new victim who reports it. The picture sharpens over time.</p><h4>What you can do:</h4><ul><li><strong>Document everything</strong>. Even if it does not connect today, it might connect tomorrow. The email fragment you cannot use now might be the pivot that breaks the case when a new breach database goes public.</li><li><strong>Build the intelligence profile incrementally</strong>. You are not looking for a single “aha” moment. You are building a mosaic. Each piece, no matter how small, adds to the picture. The picture may be incomplete, but it is still intelligence.</li><li><strong>Know when to pause</strong>. Sometimes the best move is to step back, archive what you have, and wait. Set alerts. Monitor for new activity. Let the scammer make the next move.</li><li><strong>Accept ambiguity</strong>. Not every investigation ends with a name and an address. Sometimes it ends with a probability assessment, a set of indicators, or a warning to the client. That is still valuable. Calibrated uncertainty is better than false confidence.</li></ul><h4>The professional mindset:</h4><p>An amateur expects instant results. A professional understands that intelligence is cumulative. The scammer’s greatest vulnerability is not a single mistake. It is the accumulation of small traces over time. Your job is to collect those traces, preserve them, and wait for the moment they converge.</p><p><strong>OSINT is not a solve button</strong>. It is a discipline of collection, analysis, and patience. Sometimes you get the answer. Sometimes you get closer. And sometimes you plant a seed that someone else will harvest later.</p><h4>That is the work. It is not glamorous. But it is honest.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09aac8a432c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Short, Practical OSINT Guide to Investigating a Pseudo Account]]></title>
            <link>https://preciousvincentct.medium.com/a-short-practical-osint-guide-to-investigating-a-pseudo-account-77b0f88a2e4a?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/77b0f88a2e4a</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 22:32:13 GMT</pubDate>
            <atom:updated>2026-10-11T21:44:05.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdahKIQdIONLu275dMDN2Q.png" /><figcaption>The core factor here does not lie in exaggerated tool usage but in real OSINT tradecraft.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8AEsmEOGbWuJ4x3UwxMAIg.png" /></figure><p>In this article, I will share the different techniques, methodology, and tools you can use to investigate a pseudo account online. The core factor here does not lie in exaggerated tool usage but in real OSINT tradecraft.</p><p>Take a look at the GitHub profile above. In a real setting, it would have a strong bio, email address, website, linked accounts, location clue, among others. Unfortunately, we did not find any on the target profile, making it somewhat void of intelligence collection. Regardless, we can pivot our investigation via:</p><ul><li><strong>Username and display name</strong></li><li><strong>Profile picture and potential reuse across platforms</strong></li><li><strong>Repositories and profile README</strong></li></ul><h3>Observation</h3><p>The target username/display name, profile image, follower/following counts, achievements, and public repositories are visible. Email, location, website, and linked accounts are not apparent in the supplied view. Their absence from this screenshot does not establish that they are unavailable elsewhere. We will find that with time.</p><p>The first important data collection I will focus my investigation on is the target<strong> email address</strong>. Unfortunately, it is not publicly available on their account, but we can get that via their commit email analysis. Keep in mind that this is an important collection point because Git commit metadata can disclose information that is not shown on a GitHub profile.</p><p>Our aim here is to get hold of this email address, validate it, and pivot it to build an intelligence profile. We will achieve this by:</p><ul><li><strong>Analysing the target repositories for commit email addresses</strong> (if available)</li><li><strong>Searching the exact username and reasonable spelling variations</strong></li><li><strong>Comparing the display name and profile image with other public profiles</strong></li><li><strong>Correlating public commit emails with other voluntarily published contact details</strong></li></ul><blockquote><em>Keep in mind to treat a matching username, image, or name as a lead, not proof of common ownership.</em></blockquote><h3>Step 1: Target Repositories Analysis (Commit Email Extraction)</h3><p>Since the target did not publicly expose their email address, the first step is to analyse their repositories to find potential email addresses that could lead us to a broader footprint. We can achieve this intelligence collection by simply using the browser-based tool “<strong>BrainGainSoft</strong>” or <strong>GitHub API lookup</strong>.</p><p>The tool aspect is a lot easier. You can simply open it and input the target GitHub username, and it will fetch their email address (if exposed) as shown in the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6EsylWjR9323XcGiNFgasg.png" /></figure><p>Next, we can also achieve this same result by using the GitHub API lookup technique:</p><pre>https://api.github.com/repos/[owner]/[repo]/commits</pre><p>Replace <strong>[owner]</strong> with the username or organization name, and <strong>[repo]</strong> with the repository name.</p><p><strong>Example</strong>:</p><pre>https://api.github.com/repos/techenthusiast167/WebRecon/commits</pre><p>This opens a raw JSON page containing every commit on the default branch. The page is plain text, but all the data is there.</p><p>Now, press <strong>Ctrl + F</strong> and search for <strong>&quot;email&quot;</strong>. Every match is a commit author’s email address embedded in the JSON. You will see lines like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvD2szEyBzyt0xf_kw0POw.png" /></figure><p>Scroll through the results. Each email is tied to a specific commit with a timestamp and a committer name. You can pull every email address ever used in that repository without cloning anything, without running a single command, just by reading the API output in your browser.</p><p>To make this even easier, use Firefox, which natively formats JSON with collapsible trees. If you are on Chrome, install a JSON Formatter extension. With formatted JSON, you can expand each commit object, navigate to <strong>commit → </strong><strong>author → </strong><strong>email</strong>, and the email is right there.</p><p>Note: You can aslo achieve this same result by using the the <strong>.patch</strong> Method. If you need to preserve a single commit as evidence, or if the API is not returning the data you expect, the <strong>.patch</strong> method gives you the raw, unprocessed commit output. I have explained all these techniques and methodology in my course, <strong>The Professional OSINT Practitioner</strong>. You can get it here: <a href="https://d4rkintel.substack.com/p/the-professional-osint-practitioner"><strong>https://d4rkintel.substack.com/p/the-professional-osint-practitioner</strong></a></p><h3>STEP 2: Email Analysis</h3><p>Now that we have successfully achieved our aim by getting the target email address, the next step is to validate its integrity: <strong>Is the email address valid</strong>? <strong>Is it tied to other accounts online</strong>? <strong>What is the domain</strong>? Having genuine answers to these questions would help us a lot in our pivot and perhaps correlation.</p><p>There are many email intelligence tools out there, but for the moment, my favourite one is <strong>OSINTly</strong>, a freemium OSINT intelligence platform that offers intelligence collection on email lookup, username enumeration, domain analysis, among others.</p><p>Luckily, I was offered some tokens by the team behind it for a test run, and since then, I have been a little hooked on the platform.</p><p>So, with the tool in place, we can have a broader and clearer view of the target email address footprint as shown in the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TgosjIAGPRaiHCrWajhUoA.png" /></figure><p>Now, with a single click, we have gotten a broader digital footprint of the target, making us understand our main pivoting points and that of useful data collection for correlation. The results here are just a fragment of what the tool offers. There are way more results it showed, but I cannot post them here for privacy reasons.</p><p><strong>Have a look</strong>: Our first correlation points now lie across two <strong>distinctive profiles</strong>, the one found on their <strong>GitHub </strong>and another found on their <strong>Google account</strong>. Both will be useful in our next pivot.</p><p>In real investigation, never rely on a single source of information. Always endeavour to pivot across two to three sources to validate and form a strong intelligence collection on your target.</p><p>Keep in mind that if the target email has a professional domain like <strong>sarah.jenkins@acmecorp.com</strong>, this can give rise to their website that can be reversed using the <strong>Internet Archive</strong> for additional intelligence collection:</p><ul><li>Historical Employee Directories and Org Charts</li><li>Physical Locations and Infrastructure</li><li>Acquisitions and Mergers</li><li>Former Technology Stacks</li><li>Subdomains &amp; Hidden Portals</li><li>Deleted Media &amp; Press Releases</li><li>Direct File Downloads</li></ul><p>Additionally, using a<strong> WHOIS</strong> lookup on the target domain (e.g., <a href="https://acmecorp.com/"><strong>acmecorp.com</strong></a>) is another foundational OSINT technique. While the <strong>Internet Archive</strong> provides a look at the content of a website over time, WHOIS provides intelligence on the ownership, registration, and technical infrastructure of the domain itself.</p><p>Even with modern privacy regulations (like GDPR) obscuring a lot of public registration data, a WHOIS query can still yield critical investigative points:</p><h4>Corporate &amp; Ownership Footprints</h4><ul><li>The Registrar</li><li>Organization Name</li><li>Historical WHOIS Data</li></ul><h4>Infrastructure &amp; Hosting Intelligence</h4><ul><li>Name Servers (DNS)</li></ul><h4>Timeline &amp; Behavioral Analysis</h4><ul><li>Creation Date</li><li>Expiration &amp; Update Dates</li></ul><h4>Pivoting and Connected Asset Mapping</h4><ul><li>Registrant Email/Phone (If Unmasked): If a specific corporate email address is listed in the WHOIS contact info (e.g., <strong>sarah.jenkins@acmecorp.com</strong>), you can perform a “<strong>reverse WHOIS</strong>” lookup. This allows you to find every other domain on the internet registered by that same email address, mapping out the target’s entire digital empire or network of dummy sites.</li></ul><h3>Step 3: Google Dorking (Username Enumeration)</h3><p>Since we already have the target username and email address, the third step we can take is using Google dorking to find potential documents or footprints that might yield useful intelligence to our collection. Remember, in<strong> Step 2</strong>, all accounts found were void of the target’s main identity (profile picture), which has been the primary reason behind our investigation. We need to know the person behind this GitHub account beyond the generic profile.</p><p>In this context, there are many dorks we can use depending entirely on the purpose of our investigation. We can start our approach by using a reverse image search, but I will not do that since it is not potent in this context, and my aim is finding the true identity of the target. We can start our approach at this phase by using a simple Google dork like:</p><pre>&quot;teogorqui1&quot; -site:AI</pre><p>I love approaching investigation like this by using simple dorks followed by advanced ones. The first focuses on the main entity, helping me to refine my pivot with a productive outcome. The second one below helps narrow it down to see if the target username appears inside publicly indexed documents (PDFs, Word docs, spreadsheets), which sometimes reveal real names or organizational links:</p><pre>&quot;teogorqui1&quot; filetype:pdf OR filetype:txt OR filetype:docx</pre><p>The first dork gave me a good lead: the <strong>target YouTube channel</strong> with their linked accounts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M2M_DpWeZ-Ef_yn2mECB6w.png" /></figure><p>This was a great catch at first sight but still required deeper correlation and verification nevertheless.</p><p>By analysing the target YouTube channel, I found a strong lead, and that was their <strong>profile picture</strong> that has the same <strong>identity </strong>as the one found on their <strong>Google account</strong> in <strong>Phase 2</strong>. Now, I believed the investigation was getting closer to finding out the main entity behind the generic GitHub account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ih_0lNht5ETbZ09EIwvTOw.png" /></figure><p>Next was to analyse the “<strong>Description</strong>” feature on the target YouTube channel, as that often holds linked profiles which comprise the target’s Instagram, Spotify, SoundCloud, additional email address, and location clue.</p><p>By analysing each data point found, I was able to find out the main entity behind the generic GitHub account, which lies among their <strong>SoundCloud </strong>account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8-7SgdNVwQmzzKre_NuqA.png" /></figure><p><strong>Now, here lies the honest truth</strong>: one of the most important factors at this phase lies in good correlation.<strong><em> </em></strong><em>It is not all about the mass collection of different data points but on good correlation analysis that forms a coherent bond on each point gotten</em>: <strong>username enumeration</strong> + <strong>profile uniformity</strong> + <strong>linked accounts</strong> = <strong>produce a coherent bond</strong> that yields a <strong>stronger intelligence</strong> collection.</p><p>From analyzing the target’s YouTube description, I found an additional email address that opened another entry point into their digital footprint:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvMoe1O5zfoQQMOsbVuEkQ.png" /></figure><p>Taking an additional lookup into the newly found email address, I pivoted to test it against a bigger social media platform, since I had an initial clue that their account might be registered on <strong>Facebook</strong>. Perhaps I was right. <strong>Facebook </strong>is a global social media platform, and many people out there publicise their information unlike on other social media platforms.</p><p>To verify if the target has an active presence on Facebook, I utilised the “<strong>Forgot Password</strong>” technique. This technique works by entering the target’s email address or phone number into the platform’s password recovery flow, which then reveals partial information about the target associated account, such as a masked phone number, a complete profile picture, and their username, without ever triggering a password reset or alerting the target.</p><p>In OSINT investigation, its usefulness lies in confirming whether a target holds an account on a given platform, and in extracting pivot points like a partially redacted phone number that can be further enumerated. In this case, it exposed the target additional profile, a partially redacted phone number contact, and their full username, giving me a complete clue into their online presence over there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iHTn5tygK4GP3qKTmgLMfQ.png" /></figure><p>This is just a short demonstration that shows how a simple technique can reveal a pseudo account in minutes. And of course, there are lots of tools out there that can automate this task in minutes, but understanding the core manual aspect of it is very important for cross-validation.</p><p>At times, all it takes to find a fake persona account is a simple <strong>Google dork</strong>, <strong>stylometric analysis,</strong> <strong>email permutation</strong> using their<strong> username variation</strong>, and<strong> logical pivot</strong>.</p><p>Happy OSINT4Fun. For those looking to deepen their practical OSINT tradecraft, I have a free course that covers that — available on my Substack account. Feel free to utilize the course and share your feedback -:) !</p><p><a href="https://d4rkintel.substack.com/p/the-professional-osint-practitioner">The Professional OSINT Practitioner</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77b0f88a2e4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Professional OSINT Practitioner Course]]></title>
            <link>https://preciousvincentct.medium.com/the-professional-osint-practitioner-course-2aff4247e613?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aff4247e613</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 18:58:46 GMT</pubDate>
            <atom:updated>2026-10-07T18:58:46.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ooIZklxzBofFQTb72BWBhg.png" /></figure><h4>The Course Has Been Restructured — Here Is What Changed</h4><p>When I first published this OSINT course on Medium, I packed everything into one place. One massive volume. Every module, every lecture, every technique crammed together. For some readers, it worked. For most, it was overwhelming.</p><p>I heard the feedback. It was hard to navigate. Hard to find what you needed. Hard to know where to start.</p><blockquote>That has changed.</blockquote><p>The course is now split into two volumes. Each volume has a clear focus. Each volume stands on its own. You can start with the foundation and build up. Or jump straight to the advanced technical work if that is where your interest lies.</p><h3>Volume 1: Foundations, Geospatial &amp; Target Footprint Analysis</h3><p>This is where you start.</p><p>Volume 1 covers the core skills every investigator needs. How search engines work. How to find hidden data. How to geolocate an image. How to trace an email to a real identity. How to investigate every major social media platform.</p><p>It is practical. It is hands-on. It is built for people who want to learn by doing.</p><h4>What is inside Volume 1:</h4><ul><li><strong>Module 0</strong>: The OSINT Foundation &amp; Ethical Framework</li><li><strong>Module 1</strong>: Advanced Search Engine Mastery &amp; The Art of the Google Dork</li><li><strong>Module 2</strong>: Image Intelligence (IMINT) — Geolocation, Verification, and Metadata</li><li><strong>Module 3</strong>: Email &amp; Username Intelligence — The Digital Skeleton</li><li><strong>Module 4</strong>: Social Media Intelligence (SOCMINT) — Platform Deep Dives</li></ul><p>Volume 1 ends with a full practical assignment. You will trace a target from a single piece of intelligence to a complete attribution report.</p><h3>Volume 2: Technical Intelligence, Network Analysis &amp; Advanced Attribution</h3><p>This is where you go deeper.</p><p><strong>Volume 2</strong> is for the investigator who has mastered the basics and wants to operate at a professional level. Dark web intelligence. Breach data attribution. Image forensics. Geospatial analysis. Transportation OSINT. Fraud investigation. Python automation. Report writing.</p><p>This volume turns you from someone who can find information into someone who can build intelligence.</p><h4>What is inside Volume 2:</h4><ul><li><strong>Module 5</strong>: Communication, Business, Historical Intelligence &amp; People OSINT</li><li><strong>Module 6</strong>: Website OSINT &amp; Technical Intelligence</li><li><strong>Module 7</strong>: Advanced Investigative Tradecraft</li><li><strong>Module 8</strong>: Dark Web Intelligence &amp; .onion Investigation</li><li><strong>Module 9</strong>: Image Forensics &amp; Hidden Data Recovery</li><li><strong>Module 10</strong>: Transportation OSINT — Tracing Cars, Vessels, and Aircraft</li><li><strong>Module 11</strong>: Geospatial Intelligence (GEOINT)</li><li><strong>Module 12</strong>: HUMINT-OSINT Hybrid — Trawling Forums and Online Communities</li><li><strong>Module 13</strong>: OSINT for Fraud &amp; Scam Investigation</li><li><strong>Module 14</strong>: Python for OSINT Automation</li><li><strong>Module 15</strong>: Intelligence Report Writing &amp; Entity Graph Visualization</li></ul><p>Volume 2 ends with a full capstone investigation. A complete real-world case file with grading criteria.</p><h3>Why the Split Matters</h3><p>You can start where you are.</p><p>If you are <strong>new to OSINT</strong>, start with V<strong>olume 1</strong>. It gives you the foundation. Every technique builds on the last. By the end, you will be conducting full investigations.</p><p>If you already <strong>know the basics</strong>, jump to <strong>Volume 2</strong>. It assumes you understand the fundamentals and gets straight to advanced work.</p><blockquote>You can navigate easily.</blockquote><p>No more scrolling through hundreds of pages trying to find a specific lecture. Each volume has a clear structure. Each module has a clear focus.</p><p>You can learn at your pace.</p><p>Volume 1 is the foundation. Volume 2 is the advanced work. Take your time with each. Master one before moving to the next.</p><h3>The Course Links</h3><p>Volume 1: Foundations, Geospatial &amp; Target Footprint Analysis<br><a href="https://d4rkintel.substack.com/p/the-professional-osint-practitioner">https://d4rkintel.substack.com/p/the-professional-osint-practitioner</a></p><p><strong>Volume 2</strong>: Technical Intelligence, Network Analysis &amp; Advanced Attribution<br><a href="https://d4rkintel.substack.com/p/the-professional-osint-practitioner-d50">https://d4rkintel.substack.com/p/the-professional-osint-practitioner-d50</a></p><h3>What Is Next</h3><p>More content is coming. More challenges. More practical exercises. More real-world case studies.</p><p>If you have been following along, thank you. If you are new, welcome.</p><p>The course is now easier to use. Easier to navigate. Easier to learn from.</p><p>Start with Volume 1. Build your foundation. Then move to Volume 2. That is the path.</p><p>For educational purposes only.</p><p><strong>Precious Vincent </strong>(D4rk_Intel)<br><strong>X</strong>: @d4rk_intel<br><strong>LinkedIn</strong>: <a href="https://linkedin.com/in/precious-vincent-669279263">linkedin.com/in/precious-vincent-669279263</a><br><strong>GitHub</strong>: <a href="https://github.com/techenthusiast167">github.com/techenthusiast167</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aff4247e613" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Professional OSINT Practitioner: From Foundations to Advanced Attribution]]></title>
            <link>https://preciousvincentct.medium.com/the-professional-osint-practitioner-from-foundations-to-advanced-attribution-0baa7ce97e6f?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0baa7ce97e6f</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Fri, 26 Jun 2026 21:29:45 GMT</pubDate>
            <atom:updated>2026-07-12T01:24:45.951Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EZYMt7vI5vmhvgwXt6ZkDA.png" /></figure><p>This is not a theoretical course. It is a practical, hands-on deep dive into the mindset and methodologies of a professional OSINT investigator. Every module is designed to answer not just the “<strong>what</strong>,” but the “<strong>how</strong>” and the “<strong>why</strong>,” with a strict focus on legal, ethical, and operational security (OPSEC) considerations. The goal is to transform a student from a curious beginner into a capable, analytical investigator.</p><h3>TABLE OF CONTENTS</h3><h4>Module 0: The OSINT Foundation &amp; Ethical Framework</h4><ul><li><strong>Lecture 0.1</strong>: What OSINT Is and Is Not</li><li><strong>Lecture 0.2</strong>: A Brief, Practical History</li><li><strong>Lecture 0.3</strong>: The OSINT Trinity — Ethics, Law, and OPSEC</li><li><strong>Practical Exercise</strong>: OPSEC Environment Setup</li></ul><h4>Module 1: Advanced Search Engine Mastery &amp; The Art of the Google Dork</h4><ul><li><strong>Lecture 1.1</strong>: How Search Engines Index the World</li><li><strong>Lecture 1.2</strong>: The Dorking Syntax Bible</li><li><strong>Going Deeper</strong>: The Art of the Query</li></ul><h4>Module 2: Image Intelligence (IMINT): Geolocation, Verification, and Metadata</h4><ul><li><strong>Lecture 2.1</strong>: The Art and Science of Image Geolocation</li><li><strong>Lecture 2.2</strong>: Reverse Image Search is a Starting Point, Not a Conclusion</li><li><strong>Lecture 2.3</strong>: EXIF, the Hidden Storyteller</li><li><strong>Practical Exercise</strong>: The “Where in the World” Geolocation Capstone</li></ul><h4>Module 3: Email &amp; Username Intelligence: The Digital Skeleton</h4><ul><li><strong>Lecture 3.1</strong>: Email Deconstruction &amp; Intelligence</li><li><strong>Lecture 3.2</strong>: The Forgotten Art of Verification &amp; Password Reset Intel</li><li><strong>Lecture 3.3</strong>: Username-Driven Attribution</li><li><strong>Email Investigation Graph</strong> (Visual Workflow)</li><li><strong>Practical Exercise</strong>: The Operation “SHADOW TRACE” challenge</li></ul><h4>Module 4: Social Media Intelligence (SOCMINT): Deep Dive &amp; Platform-Specific Tactics</h4><ul><li><strong>Lecture 4.1</strong>: Facebook — The Graph API and Beyond</li><li><strong>Lecture 4.2</strong>: LinkedIn — The Corporate Org Chart</li><li><strong>Lecture 4.3</strong>: Instagram — The Locational and Relational Graph</li><li><strong>Lecture 4.4</strong>: Reddit — The Unfiltered Psyche</li><li><strong>Lecture 4.5</strong>: X (Formerly Twitter) — The Real-Time Signal</li><li><strong>Lecture 4.6</strong>: GitHub Recon — The Developer’s Digital Shadow</li><li><strong>Lecture 4.7</strong>: YouTube OSINT — The Video Investigator’s Toolkit</li><li><strong>Lecture 4.8</strong>: Telegram OSINT — Investigating the Encrypted Messenger</li><li><strong>Lecture 4.9</strong>: TikTok OSINT — Investigating Short-Form Content</li><li><strong>Lecture 4.10</strong>: Bluesky OSINT — Investigating the Decentralized Network</li><li><strong>Lecture 4:11</strong>: Discord OSINT — Investigating the Chat Platform</li></ul><h4>Module 5: Communication, Business, Historical Intelligence &amp; People OSINT</h4><ul><li><strong>Lecture 5.1</strong>: Phone Number OSINT</li><li><strong>Lecture 5.2</strong>: Wayback Machine &amp; The Internet Archive</li><li><strong>Lecture 5.3</strong>: Business Intelligence for the Investigator</li></ul><h4>Module 6: Website OSINT &amp; Technical Intelligence</h4><ul><li><strong>Lecture 6.1</strong>: Domain Reconnaissance — WHOIS, DNS, and Registration History</li><li><strong>Lecture 6.2</strong>: Subdomain Discovery &amp; Enumeration</li><li><strong>Lecture 6.3</strong>: Technology Stack Fingerprinting</li><li><strong>Lecture 6.4</strong>: Directory Enumeration &amp; Exposed Files</li><li><strong>Lecture 6.5</strong>: SSL/TLS Certificate Analysis</li><li><strong>Lecture 6.7</strong>: Automated Email Discovery with EmailCrawl</li><li><strong>Lecture 6.8</strong>: Advanced Document Discovery — Extracting Hidden Files from Target Websites</li></ul><h4>Module 7: Advanced Investigative Tradecraft</h4><ul><li><strong>Lecture 7.1</strong>: Sock Puppet Management &amp; Anti-Suspension Tactics</li><li><strong>Lecture 7.2</strong>: Structured Analytic Techniques for OSINT</li><li><strong>Lecture 7.3</strong>: The Art of Pivoting</li></ul><h4>Module 8: Python for OSINT Automation — Building Your Own Tools</h4><ul><li><strong>Lecture 7.1</strong>: The Automation Development Framework</li><li><strong>Lecture 7.2</strong>: Setting Up Your Kali Linux Development Environment</li><li><strong>Lecture 7.3</strong>: Using AI as Your Coding Assistant</li><li><strong>Scripting Lab 1</strong>: Multi-Engine Dork Orchestrator</li><li><strong>Scripting Lab 2</strong>: Bulk EXIF Extractor &amp; Geolocation Plotter</li><li><strong>Scripting Lab 3</strong>: Intelligent Permutation &amp; Availability Engine</li><li><strong>Scripting Lab 4</strong>: Username-to-User ID Cross-Reference Tool</li><li><strong>Scripting Lab 5</strong>: Reddit Historical Monitoring Bot</li><li><strong>Lecture 7.4</strong>: Building Your Personal Automation Toolkit</li></ul><h4>Module 9: Intelligence Report Writing &amp; Entity Graph Visualization</h4><ul><li><strong>Lecture 8.1</strong>: Structuring the Intelligence Report</li><li><strong>Lecture 8.2</strong>: Writing for Your Audience — Client, Legal, or Internal</li><li><strong>Lecture 8.3</strong>: Evidence Documentation &amp; Source Citation Standards</li><li><strong>Lecture 8.4</strong>: Entity Graph Visualization — Tools &amp; Methodology</li><li><strong>Lecture 8.5</strong>: Building the Final Intelligence Package</li><li><strong>Practical Exercise</strong>: Produce a Client-Ready Intelligence Report with Entity Graph</li></ul><h4>Capstone Course: The Integrated Investigation</h4><ul><li><strong>Case File</strong>: Michael Hall &amp; HALL OR NOTHING MANAGEMENT LIMITED</li><li>Full-Spectrum Intelligence Report</li><li>Final Submission &amp; Grading Criteria</li></ul><h4>Appendices</h4><ul><li><strong>Appendix A</strong>: Glossary of OSINT Terms</li><li><strong>Appendix B</strong>: Complete Tools Index</li><li><strong>Appendix C</strong>: Quick Reference — Google Dorking Operators</li><li><strong>Appendix D</strong>: Quick Reference — Social Media User ID Extraction Methods</li><li><strong>Appendix E</strong>: Quick Reference — Investigation Workflow Checklists</li></ul><h3>Module 0: The OSINT Foundation &amp; Ethical Framework</h3><p>Before you open a single tool, before you run a single search, before you touch any data, you need to understand what you are doing, why you are doing it, and how to do it without destroying yourself in the process. This module sets the baseline. Everyone starts here.</p><h4><strong>Lecture 0.1</strong>: What OSINT Is and Is Not</h4><p>OSINT is Open Source Intelligence. The official definition is simple: <strong>intelligence produced from publicly available information that is collected, exploited, and disseminated in a timely manner to an appropriate audience.</strong></p><h4><strong>Let me break that down</strong></h4><p>Publicly available means the information is accessible without special access. No passwords. No breaches. No hacking. If you need to log in, bypass a paywall, or exploit a vulnerability, that is not OSINT. That is something else entirely.</p><p>Collected, exploited, and disseminated means you do not just find data. You process it. You analyze it. You turn it into something actionable. Then you deliver it to someone who can use it. <em>Raw data is not intelligence</em>. <strong>Intelligence </strong>is <strong>data </strong>that has been <strong>verified, contextualized</strong>, and <strong>presented </strong>with <strong>meaning.</strong></p><h4><strong>The Intelligence Cycle Applied to OSINT</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bWaSpjNFkdmmONqyf9BQ9w.png" /></figure><p>Every professional investigation follows a cycle. Skip a step, and your product suffers.</p><ul><li><strong>Planning &amp; Direction</strong>: What is the question? What does the client actually need? Define your scope before you start, or you will drown in data.</li><li><strong>Collection</strong>: Gather the raw information. Search engines, social media, public records, domain tools, archives.</li><li><strong>Processing &amp; Exploitation</strong>: Organize the raw data. Strip out noise. Convert formats. Prepare for analysis.</li><li><strong>Analysis &amp; Production</strong>: Connect the dots. Identify patterns. Draw conclusions. Produce a report that answers the original question.</li><li><strong>Dissemination</strong>: Deliver the finished intelligence to the client in a format they can use.</li></ul><h4>Distinguishing OSINT from Adjacent Disciplines</h4><p>OSINT is one intelligence discipline among many. Do not confuse them.</p><ul><li><strong>HUMINT —</strong> is human intelligence. Talking to people. Recruiting sources. Running informants. That is not OSINT.</li><li><strong>SIGINT —</strong> is signals intelligence. Intercepting communications. That is not OSINT.</li><li><strong>GEOINT —</strong> is geospatial intelligence. Satellite imagery analysis. OSINT can include GEOINT when the satellite data is publicly available, but the classified stuff is not OSINT.</li></ul><h4>What OSINT Is Not</h4><p>Let me be absolutely clear on this.</p><p><strong>OSINT </strong>is not <strong>hacking</strong>. You do not bypass security. You do not exploit vulnerabilities. You do not access systems without authorization.</p><p><strong>OSINT </strong>is not <strong>doxxing</strong>. Doxxing is publishing private information with malicious intent. OSINT is collecting and analyzing publicly available information for legitimate purposes. The difference is intent, consent, and dissemination.</p><p><strong>OSINT </strong>is not <strong>illegal access</strong>. If a file is publicly accessible on a server but the server owner did not intend for it to be public, accessing it may still be legal in some jurisdictions. That does not make it ethical. We will cover this boundary in depth.</p><p>If you want to be a <strong>hacker</strong>, this is the <strong>wrong course</strong>. If you want to be a professional investigator who operates within the law and maintains ethical standards, you are in the right place.</p><h4><strong>Lecture 0.2</strong>: A Brief, Practical History</h4><p>OSINT sounds new. It is not. Governments have been doing this for over eighty years.</p><h4>The Early Days</h4><p>During World War II, the United States created the Foreign Broadcast Information Service, or FBIS. Their job was simple. Monitor foreign radio broadcasts. Transcribe them. Translate them. Analyze them. This was open source intelligence before the term existed.</p><p>The BBC performed a similar function for the United Kingdom. Both organizations understood that publicly available information, when systematically collected and analyzed, produces intelligence as valuable as anything from a spy.</p><h4>The Digital Revolution</h4><p>The commercial internet changed everything. Suddenly, information that used to require a physical presence to access became available to anyone with a modem. Search engines organized it. Forums and early social media created new sources of human behavior data.</p><p>The 2010s saw the rise of platforms like Facebook, Twitter, YouTube, and LinkedIn. Billions of people began voluntarily publishing their locations, relationships, opinions, and activities. For an intelligence analyst, this was unprecedented.</p><h4>The Open Source Revolution</h4><p>The 2020s marked a turning point. The conflict in Ukraine demonstrated that open source intelligence had matured into a primary intelligence discipline. Civilian analysts using commercial satellite imagery, social media posts, and public flight tracking data were able to document military movements, verify attacks, and expose disinformation in near real-time.</p><p>This was not a niche hobby. It was a strategic capability. Governments, corporations, and investigative organizations now recognize OSINT as essential. That is the world you are entering.</p><h4>Lecture 0.3: The OSINT Trinity: Ethics, Law, and OPSEC</h4><p>Three things govern every investigation you will ever conduct. <strong>Ethics</strong>. <strong>Law</strong>. <strong>Operational Security</strong>. Ignore any one of them, and you are not a professional. You are a liability.</p><h4>Ethics</h4><p>Ethics is not the same as law. Something can be legal and still be wrong. Your ethical framework is what separates you from a stalker, a harasser, or a vigilante.</p><h4>Key principles:</h4><ul><li><strong>Respect for privacy — </strong>Just because information is publicly available does not mean the person intended for it to be public. Consider context. A photo posted to a public Facebook group is public. A photo extracted from an unsecured cloud storage bucket is also technically public, but the subject did not consent to its distribution. Understand the difference.</li><li><strong>Data minimization — </strong>Collect only what you need for the investigation. Do not hoard personal data. When the investigation is complete, securely dispose of what you no longer require.</li><li><strong>Intent — </strong>Ask yourself why you are investigating. Is the purpose legitimate? Due diligence for a business partnership? Locating a missing person? Supporting a legal case? These are legitimate purposes. Investigating an ex-partner out of jealousy? That is stalking.</li><li><strong>When does investigation become stalking</strong>? When the purpose is personal rather than professional. When the collection is obsessive rather than systematic. When the subject has a reasonable expectation of privacy and you violate it. If you are not sure, ask a colleague. If you cannot explain your purpose to a third party without sounding creepy, stop.</li></ul><h4>Law</h4><p>Laws vary by jurisdiction, but some principles apply broadly.</p><ul><li><strong>GDPR — </strong>(General Data Protection Regulation) governs the processing of personal data in the European Union and the UK. It applies even if you are outside the EU but processing data about EU residents. Understand the basics. Public availability is not an automatic defense.</li><li><strong>CFAA — </strong>(Computer Fraud and Abuse Act) in the United States makes it illegal to access a computer system without authorization. If a site has terms of service and you violate them, you may be committing a federal crime. Read terms of service. Know what you are agreeing to.</li><li><strong>Terms of service are legally binding contracts — </strong>If a platform prohibits automated scraping, and you automate scraping, you are in violation. This may be civil rather than criminal, but it can still get you sued or banned.</li><li><strong>Publicly available does not mean legal to collect or process —</strong> This is the most important legal lesson in this course. A document sitting on an open server is publicly available. If you access it for a legitimate purpose, you may be fine. If you download it, republish it, or use it for harassment, you may be committing crimes. Context and jurisdiction matter. When in doubt, consult a lawyer.</li></ul><h4>Operational Security (OPSEC)</h4><p>Your own security is your first priority. If your investigation exposes you, you become the story. Your target may retaliate. The platform may ban you. Your employer may face legal consequences.</p><h4>Practical Setup: The Investigation Environment</h4><p>Every investigation starts with a clean, isolated environment.</p><ul><li><strong>Virtual Machine</strong> (VM): Use VirtualBox or VMware. Install a clean operating system. This VM is only for investigations. Nothing personal lives here.</li><li><strong>Dedicated Browser: </strong>Use Firefox or Brave within the VM. Configure privacy settings. Disable telemetry. Install essential extensions only.</li><li><strong>VPN or Dedicated Connection</strong>: Your investigation traffic should not originate from your home IP address. Use a VPN with a kill switch, or a dedicated mobile hotspot.</li><li><strong>No Cross-Contamination</strong>: Never log into personal accounts from your investigation VM. Never check your email. Never browse social media. This VM touches the target. Nothing else.</li></ul><h4>Sock Puppets, Not Sloppy Puppets</h4><p>A sock puppet is a fabricated online identity used for investigation. Done right, it is a professional tool. Done wrong, it is a liability that exposes you in seconds.</p><p><strong>Creating a credible sock puppet requires:</strong></p><ul><li><strong>A believable backstory</strong>: The persona needs a name, a location, an occupation, and a plausible history. Do not invent a neurosurgeon if you do not know what a neurosurgeon does. Keep it simple. Keep it close to what you actually know.</li><li><strong>Aged accounts</strong>: Create accounts and let them sit. A brand-new account with zero friends, zero posts, and zero history is immediately suspicious. Build the persona over weeks or months before using it for investigation.</li><li><strong>Consistent activity</strong>: Post occasionally. Follow people. Build a presence. The account should look lived-in.</li><li><strong>Dedicated infrastructure</strong>: Each sock puppet gets its own email address, its own phone number (for verification), and its own profile picture. Never reuse details across puppets.</li><li><strong>Browser fingerprinting countermeasures</strong>: Websites track your browser fingerprint, a combination of your screen resolution, installed fonts, timezone, language settings, and more. Use anti-fingerprinting browser extensions or dedicated tools like the Brave browser’s fingerprinting protection. Your sock puppet’s fingerprint must not match your real fingerprint.</li><li><strong>VM escape risks</strong>: If malware on the target’s site breaks out of your VM and reaches your host machine, you are compromised. Keep your VM software updated. Do not download files from suspicious sites directly. Use a sandbox.</li><li><strong>Canary tokens</strong>: These are hidden trackers you can embed in documents or links. If someone opens a file you planted, the token alerts you. This is how you detect if your sock puppet has been discovered and someone is investigating you back.</li></ul><h3>Module 1: Advanced Search Engine Mastery &amp; The Art of the Google Dork</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3MV71_9IVMgSo38lys8fFg.png" /></figure><p>This module moves beyond simple search into the syntax-based exploitation of search engine indexes.</p><h4>Lecture 1.1: How Search Engines Index the World</h4><p>Search engines like <strong>Google</strong>, <strong>Yandex</strong>, <strong>Bing</strong>, and others are far more than everyday query tools. For the OSINT investigator, they are the primary gateway to an immense, continuously updated repository of publicly available intelligence. These platforms systematically crawl, index, and organize billions of web pages, documents, and exposed directories, often surfacing data that website owners never intended to be discoverable.</p><p>Security analysts and professional investigators have long recognized this power. For years, they have relied on search engines not merely for casual research, but as precision instruments to gather actionable intelligence and uncover evidence. Whether the task involves mapping the digital footprint of a person of interest, tracing infrastructure in a cybercrime investigation, or conducting comprehensive due diligence on a corporation, mastery of search engine mechanics separates the professional from the amateur. This lecture establishes the foundational understanding of how that indexing process works because you cannot exploit what you do not understand.</p><h4>Understanding crawlers, indexes, and why dorks work.</h4><p>Let us get one thing straight before we touch any dork or type any command: <strong>you need to understand what happens behind the scenes when a search engine does its job</strong>. If you skip this part, you will just be memorizing syntax without knowing why it works, and that is not how a real investigator operates.</p><p>Search engines use automated bots, often called crawlers or spiders. These bots are constantly moving across the web, jumping from one link to another, downloading page content, and following new paths wherever they lead. They are not smart. They are just fast and relentless. They land on a page, read the text, the titles, the links, the file names, and then they move on. Whatever they find, they take back to the search engine’s main database, which we call the index.</p><p>Now, the index is basically a gigantic, constantly updating library of everything the crawlers have seen. But here is the part most people miss: crawlers do not just index the obvious stuff. They also index things like directory listings that someone forgot to secure, backup files with weird extensions, server error messages that leak software versions, and even login portals that were never meant to be found through a simple search. They just crawl and capture. They do not judge whether something should be public or not. That is where we come in.</p><h4><strong>This brings us to Dorks</strong></h4><p>A Google dork is not some magic hack. It is simply a search query that uses advanced operators to tell the search engine exactly what we want from that massive index. Think of it like this: the index holds everything the crawler saw. Most<strong> people just type random words</strong> and hope for the best. We, on the other hand, <strong>use operators </strong>to <strong>filter out the noise</strong> and <strong>pull back only what is valuable</strong>. We are not breaking anything. We are not accessing anything illegally. We are simply asking the search engine a smarter question.</p><p>So when you use a dork like <strong>intitle:&quot;index of&quot;</strong>, you are basically telling Google: &quot;<strong>Hey, from your entire index, show me only pages where the title tag literally says &#39;index of&#39;</strong>.&quot; That is it. The power does not come from the tool. It comes from you understanding how the data got there in the first place and knowing how to ask for it properly.</p><p>This is the foundation. Once you internalize this, every operator, every filter, every combination will make sense because you will know what you are actually doing under the hood.</p><h4>Lecture 1.2: The Dorking Syntax Bible</h4><p>Now we get to the part everyone thinks they already know. Most people can type `<strong>site</strong>:` into Google and feel like a hacker. But there is a massive difference between knowing a few operators and truly understanding how to combine them for precise, repeatable results. That is what this lecture is about.</p><p><strong>Let us break down the core operators one by one, not just as definitions, but as tools with specific intelligence purposes</strong></p><h4><strong>site</strong>:</h4><p>This one restricts your search to a single domain or top-level domain. Sounds simple, right? But here is what most people miss. `<strong>site:example.com</strong>` searches that domain and all its subdomains. So if you are investigating a company, you are not just searching their main website. You are also pulling results from their support portal, their dev environment, their staging server, whatever is publicly exposed and indexed. You can also flip this. `<strong>site:gov</strong>` restricts results to government domains. `<strong>site:edu</strong>` targets educational institutions. For an investigator, this operator is your scope control. Use it first, then layer everything else on top.</p><h4>intitle:</h4><p>This operator searches only within the HTML title tag of a page, the text that appears on your browser tab. Why is this important? Because the title tag often contains the most descriptive, structured information about what a page actually is. Directory listings have “<strong>Index of</strong>” in the title. Login pages often have “<strong>Login</strong>” or “<strong>Sign In</strong>.” Camera feeds have the device model. When you use `<strong>intitle</strong>:`, you are not just searching for words on a page. You are searching for the page’s identity.</p><h4>inurl:</h4><p>This one hunts inside the URL itself. URLs carry structure. They reveal file paths, directory names, parameters, and sometimes even usernames. If you see `<strong>/admin/</strong>` in a URL, you know what that likely points to. If you see `<strong>/uploads/</strong>`, you know files might be sitting there openly. The `<strong>inurl</strong>:` operator lets you target those structural clues directly. This is how you find login portals, exposed admin panels, and configuration files that were never meant to be public.</p><h4>intext:</h4><p>This searches only within the body text of a page. It ignores titles, URLs, and metadata. Why does this matter? Because sometimes the thing you are looking for, like a password, an internal project name, or a specific phrase from a leaked document, only exists in the body content. `<strong>intext</strong>:` lets you cut straight to it without getting distracted by pages that merely mention your keyword in a title or link.</p><h4>Combining Operators</h4><p>Here is where the real skill comes in. Any amateur can use one operator. A professional combines them to build a precise query that returns exactly what they need and nothing else.</p><p>Let me give you an example. Say you are doing a corporate investigation and you want to find Excel files on the target’s domain that contain the word “<strong>confidential</strong>.”</p><p>You do not just type “<strong>confidential</strong>” into Google. You build this:</p><p>`<strong>filetype:xlsx site:company.com intext:”confidential</strong>”`</p><p>Now let us break down what this does. `<strong>site:company.com</strong>` locks your search to their domain. `<strong>filetype:xlsx</strong>` tells Google you only want Excel spreadsheets. `intext:”confidential”` instructs it to look inside the body of those spreadsheets for that specific word. Three operators, one query, and suddenly you are looking at documents that were probably meant to stay internal.</p><p>That is the mindset. Every operator is a filter, and your job is to stack filters until only the gold remains.</p><h4>The Often-Overlooked Operators</h4><p>Nobody talks about these enough, and that is a mistake.</p><p>`<strong>daterange</strong>:` lets you restrict results to a specific time period using Julian date format. This is critical for investigations where you need to see what was indexed during a particular time-frame, like before a company claimed they removed certain content, or during the period when a cyberattack was happening.</p><p><strong>Number ranges</strong>, accessed through the numrange operator or simply by using two dots between numbers, are another underused weapon. Let us say you are looking for a specific model of a vulnerable IoT device. Instead of guessing, you can search for a range of serial numbers or firmware versions that are known to be exploitable. This turns a broad search into a surgical strike.</p><p>`<strong>filetype</strong>:` we already touched on, but understand how deep this goes. Beyond `<strong>xlsx</strong>` and `<strong>pdf</strong>`, you can hunt for `<strong>.sql</strong>` database backups, `<strong>.env</strong>` configuration files, `<strong>.log</strong>` server logs, `<strong>.bak</strong>` backup files, and more. Each file type tells a different story. A `<strong>.sql</strong>` file might contain user credentials. A `.<strong>env</strong>` file might leak API keys. A `.<strong>log</strong>` file might expose internal IP addresses and server paths.</p><h3>Practical Application</h3><p>Let me give you real scenarios so you understand how this plays out in actual investigations.</p><h4>Finding Exposed Directories:</h4><p>When a web server has directory listing enabled, it creates a page titled “<strong>Index of</strong>” showing every file in that folder like a file explorer. To find these, you use:</p><p>`<strong>intitle:”index of” site:target.com</strong>`</p><p>This returns every open directory on the target’s domain. From there, you browse manually and look for interesting filenames. I have found internal strategy documents, employee photos, database backups, etc using this dorks.</p><h4>Finding Specific File Types:</h4><p>Maybe you are looking for PDF reports a company published but never meant to be easily discovered. You would use:</p><p>`<strong>filetype:pdf site:target.com intitle:”internal</strong>”`</p><p>Or you are hunting for exposed spreadsheets:</p><p>`<strong>filetype:xlsx site:target.com intext:”salary</strong>”`</p><p>Every combination tells a different story and targets a different type of exposed data.</p><h4>Finding Login Portals:</h4><p>Many organizations expose login pages to the internet without realizing how easily they can be discovered. Try this:</p><p>`<strong>inurl:admin site:target.com intitle:”login</strong>”`</p><p>Or for network devices:</p><p>`<strong>inurl:/cgi-bin/ site:target.com</strong>`</p><p>These queries surface routers, cameras, and management interfaces that might still be using default credentials.</p><h4>Finding IoT Devices and Vulnerable Software:</h4><p>Shodan is great, but Google also indexes device interfaces. Cameras, printers, and other IoT devices often have web-based control panels. You can find them with queries like:</p><p>`<strong>intitle:”webcam” inurl:/view/</strong>`</p><p>Or for a specific vulnerable version of software:</p><p>`<strong>intext:”Powered by phpMyAdmin 4.7&quot; site:target.com</strong>`</p><p>This tells you exactly which version is running, and from there you can cross-reference known vulnerabilities.</p><h4>The Mindset</h4><p>Do not memorize dorks. That is a beginner’s game. Understand what each operator does, then think logically about what kind of page would contain the information you are looking for. What would its title be? What would its URL look like? What file type would the data live in? Answer those questions, translate them into operators, and you will be able to build dorks for any situation, not just the ones someone else gave you.</p><h4>Going Deeper: A Resource I Wrote for You</h4><p>Before we close out this lecture on dorking syntax, I want to point you toward a resource I created specifically to deepen your understanding of what we just covered.</p><p>I wrote an article called <strong>The Art Of The Query</strong>, and I did not write it to give you a list of dorks to memorize. I wrote it to teach you how to think. How to approach a target with logic instead of guesswork. How to see operators not as commands, but as building blocks you can combine and recombine based on what you’re hunting for.</p><p>In that piece, I break down the mental framework behind crafting queries that surface what others miss. I walk through real examples and show the thought process behind each query, because once you internalize that process, you stop needing cheat sheets. You start building your own dorks on the fly, tailored to whatever investigation is in front of you.</p><p>If you want to go beyond what we covered today and really sharpen your search game, take the time to study it.</p><p>Here is the link: <a href="https://medium.com/p/ab129564af38"><strong>https://medium.com/p/ab129564af38</strong></a></p><p>Read it carefully. Practice the techniques. That is how you move from knowing about dorks to mastering them.</p><h3>Module 2: Image Intelligence (IMINT): Geolocation, Verification, and Metadata</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLJ2N3eEZoHVONtoBsDMVQ.png" /></figure><p>If there is one skill set that has defined modern OSINT investigations, it is image intelligence. We have all seen it play out in real time. An image surfaces online, and within hours, sometimes minutes, investigators have pinpointed the exact location where it was taken. That is not luck. That is not some secret tool. That is a trained, systematic approach to extracting every possible clue from an image.</p><p>This module is where you learn to do exactly that. We are covering geolocation, verification, and metadata, not as separate concepts, but as parts of a single investigative workflow. By the end, you will not just look at images. You will dissect them.</p><h4>Lecture 2.1: The Art and Science of Image Geolocation</h4><p>Let me start by telling you what geolocation is not. It is not guessing. It is not scrolling around Google Earth hoping to stumble across a matching building. That is what amateurs do, and amateurs burn hours for nothing.</p><p>Professional geolocation is a methodical, checklist-driven process. You move from the big picture down to the smallest detail, and you document every single step along the way. You never, ever guess. If you can not prove it, you do not have it yet.</p><h3><strong>I am going to break this into two phases</strong>:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LPlp6ghp_AIpT8V_jOIQJA.png" /></figure><p><strong>Foreground analysis</strong> and <strong>Background analysis</strong>. In practice, you will jump between both as clues present themselves, but understanding them separately builds the mental framework.</p><h4>Foreground Analysis</h4><p>The foreground is everything close to the camera. This is often where the richest clues live, so start here.</p><p><strong>Signage is your best friend</strong> (as illustrated in the image above). A store name, a street sign, a billboard, even a warning label on a piece of equipment. Every sign tells you something. A shop name gives you a business to search. A street sign gives you an intersection. A warning label in a specific language narrows your geographic region instantly. Do not just read the sign. Ask what the sign implies. A sign in French does not just mean France. It could be Belgium, Switzerland, Senegal, or parts of Canada. That distinction is where the real work begins.</p><p><strong>Language is another immediate filter</strong>. Text visible in the image, whether on signs, products, or clothing, can narrow your search to a handful of countries. But go deeper. Is it Brazilian Portuguese or European Portuguese? Simplified or Traditional Chinese? These distinctions matter, and a trained investigator learns to spot them.</p><p><strong>Flags seem obvious, but be careful</strong>. A flag tells you what someone wants you to see. It does not always tell you where the image was actually taken. I have seen images with Russian flags that were geolocated to Ukraine, and images with American flags taken in the Middle East. Use flags as a starting point, not a conclusion.</p><p><strong>License plates are pure gold when you can see them clearly</strong>. Even a partial plate, combined with the color and format of the plate itself, can narrow a location to a specific country or even a specific region within that country. Different countries use different colors for commercial versus private vehicles. Some regions have unique formats. Learn to recognize these patterns.</p><p><strong>Architecture tells a story too</strong>. Building materials, window styles, roof types, and construction methods vary dramatically across the world. A building with thick stone walls and small windows suggests a hot climate. A steep, snow-shedding roof suggests northern winters. Balconies, shutters, brick patterns, all of these are regional fingerprints.</p><p><strong>Vegetation is another clue most beginners ignore</strong>. Palm trees narrow things down, but which palm trees? A coconut palm and a date palm grow in very different environments. Deciduous trees versus evergreens tell you about climate. The color of the soil, the type of crops in a field, even the weeds growing through a crack in the pavement can provide hints.</p><p><strong>People in the image also provide clues</strong>, but you have to be careful here too. Clothing styles, uniforms, and traditional dress can indicate region. Face masks during certain periods pointed toward countries with specific public health policies. But people travel. People immigrate. A person’s appearance is a clue, not a confirmation.</p><h4>Background Analysis</h4><p>Once you have exhausted the foreground, you move to what is behind the subject. This is background analysis, and for many investigators, this is where the real challenge begins.</p><p><strong>Skyline analysis is one of the most powerful techniques we have</strong>. If you can see a city skyline, you can often match the silhouette of buildings to known locations. But even without a full skyline, individual structures help. A distinctive church spire, a uniquely shaped skyscraper, a water tower on a hill. These are landmarks, and landmarks are searchable.</p><p><strong>Topography is the shape of the land itself</strong>. Is the location flat or hilly? Are there mountains in the distance? If so, what do they look like? Rounded, ancient mountains versus sharp, young peaks. The presence of snow on peaks in summer tells you about elevation and latitude. You can use tools like <strong>PeakVisor</strong> to identify mountain profiles from a single ridgeline.</p><p><strong>Mountain profiles are particularly useful in rural or wilderness areas</strong>. If you have a clear view of a mountain range, you can often match the skyline to topographic data and pinpoint your location with surprising accuracy. I have seen investigators geolocate a photo taken in the middle of nowhere based entirely on the shape of a distant peak.</p><p><strong>Utility poles and power lines are forensic gold</strong>. Different countries, and sometimes different regions within countries, use distinct pole designs, insulator types, and wiring configurations. Japan’s utility poles look different from Germany’s. Even the number of crossarms and the way wires are arranged can narrow your search. This is a niche skill, but once you learn it, you will never unsee it.</p><p><strong>Road markings are equally valuable</strong>. The color of lane lines, the pattern of dashed versus solid, the font used on road signs, the design of guardrails. All of these differ by country and sometimes by state or province. A yellow center line means something very different in North America versus Europe. Learn these standards.</p><h4>Annotation for Verification</h4><p>Now we come to the most important part of this entire lecture, and I need you to take this seriously.</p><p>Finding a location is only half the job. A professional investigator proves their finding. You do this through annotation, which is simply the process of visually demonstrating the correlation between your source image and your reference imagery.</p><p><strong>Here is what this looks like in practice</strong></p><p>You have an image from social media. You have identified a potential location. You now open Google Earth Pro or QGIS and you capture a screenshot of that location from the same approximate angle. Then, using any basic tool that lets you draw on images, you highlight the points of correlation.</p><p>You draw an arrow to the distinctive crack in the pavement visible in both images. You circle the unique arrangement of windows on a building. You highlight the matching street sign. You annotate every single point that proves your case.</p><p><strong>Why is this so important</strong>?</p><p>Two reasons. First, it forces you to verify your own work. If you can not clearly highlight multiple matching points, you are not done yet. Second, this is how you present findings to clients, to colleagues, or in a report. You do not just say “<strong>this photo was taken at these coordinates.</strong>” You show them, with visual proof, exactly how you know.</p><p>The tools for this do not need to be fancy. QGIS is free and powerful. Google Earth Pro is free and familiar. Even basic screenshot tools with markup capabilities work fine. What matters is the rigor of your process, not the price of your software.</p><p>This is the standard. No guesses. No assumptions. Just methodical analysis documented with clear, visual proof. That is what separates a professional geolocator from someone playing around on Google Maps.</p><h4>Lecture 2.2: Reverse Image Search is a Starting Point, Not a Conclusion</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZFJwFdmOZFSypdsRJT2pw.png" /></figure><p>Let me be blunt. Most people think reverse image search is the entire game. You drop an image into Google Images, see if it pops up somewhere else, and call it a day. That is not investigation. That is step one.</p><p>Reverse image search is a starting point. It tells you where else an image has appeared. It can help you find a higher resolution version, an uncropped version, or an earlier posting date. All of that is useful. But it does not confirm anything on its own. You still need to verify what you find.</p><p>Now, the tool landscape for this is broader than most people realize. Each engine sees a different slice of the internet.</p><p><strong>Google Lens</strong> and<strong> Google Images </strong>are the obvious starting points. Google’s index is massive, and Lens in particular has gotten good at identifying objects within images, not just matching the whole frame. If you have a photo of a building, Lens might tell you what building it is without needing to find that exact photo elsewhere. That is powerful.</p><p><strong>Yandex </strong>is, in my experience, often superior to Google for facial matching and for finding images that originated in Eastern Europe or Russia. Yandex’s index covers parts of the web that Google does not crawl as deeply. If you are investigating something with a Russian or Eastern European connection, you check Yandex. No exceptions.</p><p><strong>Bing </strong>is the underdog nobody talks about enough. Its image matching algorithm sometimes catches results that Google misses entirely. I do not know why. I just know I have found crucial matches on Bing that appeared nowhere else. Use it.</p><p><strong>TinEye </strong>is old but still useful, especially for tracking when an image first appeared. TinEye indexes images and tracks their first appearance date, which helps with timeline analysis. The downside is its index is smaller than the big players, but for certain investigations, that timestamp data is worth the extra step.</p><p><strong>Baidu </strong>is essential if your investigation touches China. Baidu’s image search covers the Chinese internet ecosystem, which is largely invisible to Western search engines. If your image might have originated on Weibo, WeChat, or Chinese forums, Baidu is where you go.</p><h4>Here is a practical technique that will immediately improve your results: crop first, search second.</h4><p>Most people drop an entire image into the search engine and hope for the best. That works sometimes. But when it does not, you need to isolate unique details. <strong>Crop the image</strong> down to a <strong>specific lamp post</strong>. A distinct <strong>logo </strong>on<strong> </strong>a <strong>shirt</strong>. A unique <strong>architectural feature</strong>. A piece of graffiti. Then search that cropped section alone.</p><p>Why does this work? Because the search engine stops getting distracted by the whole scene and focuses entirely on matching that one distinctive element. I have cracked cases by cropping an image down to a single street sign that was barely visible in the corner of the original photo. The full image returned nothing. The cropped sign returned an exact match.</p><p>Remember, reverse image search is a tool, not a result. Use it. Exhaust it. But do not stop there.</p><h4>Lecture 2.3: EXIF, the Hidden Storyteller</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8edE5yYdKiyAY4rLypl8cA.png" /></figure><p>Now we get into something that separates serious investigators from everyone else.<strong> EXIF data</strong>.</p><p>Every time a digital camera or smartphone takes a photo, it embeds information into the file. This is called <strong>metadata</strong>, and EXIF, which stands for <strong>Exchangeable Image File Format</strong>, is the standard that defines what gets stored. Most people have no idea this data exists. You are about to become someone who exploits it.</p><p>Let us talk about what metadata actually is. It is a data dictionary attached to the image file. Think of it as a hidden document that describes the photo in detail. And I do not just mean GPS coordinates, though those are obviously valuable. The full picture is much bigger.</p><p>Metadata can include the make and model of the device, the software version the device was running, the exact date and time the photo was taken, whether the flash fired, the shutter speed, the aperture, the ISO, and sometimes even the direction the camera was pointing if the device had a compass. It can tell you if the image was edited, what software was used to edit it, and when that edit happened.</p><p><strong>Here is why this matters for an investigator</strong></p><p>Let us say someone posts a photo online claiming it was taken on an iPhone last week. You extract the metadata and discover the device was actually a Samsung Galaxy from three years ago and the photo was modified in Photoshop last month. That is a deception you just caught, and you caught it because you checked what the file itself had to say.</p><h4>Practical Extraction and Analysis</h4><p>The tool for this job is <strong>ExifTool</strong> by <strong>Phil Harvey</strong>. It is command-line based, it is free, and it is the gold standard for metadata extraction. Every investigator should have it installed and know how to use it.</p><p>Basic usage is straightforward. You point ExifTool at an image file, and it dumps everything it finds. Here is what that looks like:</p><p><strong>exiftool image.jpg</strong></p><p><strong>{ Note</strong>: Kali Linux is case-sensitive. Gaining proficiency at it will help you a lot in utilizing these command-line tools effectively }</p><p>That single command spits out every metadata field embedded in that file. The output can be overwhelming at first, but you will learn to scan it for the fields that matter most.</p><p><strong>Make and Model</strong> — tell you what device captured the image. This is useful for attribution. If a suspect claims they do not own a particular phone model, but every image they post comes from that exact model, you have got a problem for them.</p><p><strong>Software version is often overlooked — </strong>It tells you what operating system or firmware the device was running. This can help you identify if a device was jailbroken, if it was running outdated software with known vulnerabilities, or if the version matches a device known to be used by a particular individual.</p><p><strong>Timestamps are critical for timeline analysis — </strong>The Date/Time Original field tells you exactly when the shutter was pressed. Compare this against alibis, against other events, against when the image was actually posted. Time gaps between capture and posting can be revealing.</p><p><strong>Modify Date — </strong>tells you if and when the file was altered. If the modify date is different from the capture date, someone edited that image. Dig deeper.</p><p><strong>GPS coordinates — </strong>are the obvious prize, and when they are present, they can give you an exact location. But here is what most people do not consider. Even without GPS, the timestamp alone can help with geolocation. If you know the photo was taken at <strong>3 PM</strong> local time and <strong>you can see the position of shadows</strong>, you can <strong>estimate longitude</strong>. Combine that with other visual clues, and you are narrowing the map.</p><h4>The Serial Number OSINT Trick</h4><p>This is a technique that does not get enough attention, and it is incredibly powerful once you understand it.</p><p>Some camera manufacturers embed the device serial number directly into the EXIF data. This is not a bug. It is a feature for tracking and warranty purposes. But for an investigator, it is a gift.</p><h4><strong>Here is why</strong></h4><p>If you <strong>extract </strong>the <strong>serial number </strong>from one<strong> photo</strong>, you can then<strong> search </strong>for that<strong> exact serial number </strong>across other<strong> images</strong>. And because it is a <strong>unique identifier tied</strong> to a<strong> </strong>specific <strong>physical device</strong>, you can now<strong> link multiple photos </strong>to the<strong> same camera</strong>, even if those photos were posted across different platforms, under different usernames, at different times.</p><p><strong>Think about what that means — </strong>A target posts photos on <strong>Instagram under one name</strong>, on a<strong> forum </strong>under<strong> another name</strong>, and on a <strong>dark web marketplace</strong> under a <strong>third name</strong>. If all those<strong> photos </strong>came from the<strong> same camera</strong> and the <strong>serial number </strong>is <strong>embedded</strong>, you have just<strong> connected three separate online personas </strong>to<strong> one physical device</strong>. That is attribution.</p><p>This is not theoretical. I have done it. Others in this field have done it. It is a technique that produces hard, undeniable links between seemingly unconnected accounts.</p><h4>Case Study: The Smartphone and the Seized Laptop</h4><p>Let me walk you through a real-world scenario so you understand how this plays out in an actual investigation.</p><p>Authorities seized a laptop from a suspect involved in a cybercrime case. On that laptop, they found a photo that appeared to be a screenshot of something incriminating. The suspect claimed the laptop was not his and he had no idea how that photo got there.</p><p>Investigators extracted the EXIF data from that photo. It was not a screenshot at all. It was a photo taken with a smartphone, and the metadata revealed the exact make, model, and serial number of the device.</p><p>They then obtained the suspect’s smartphone, extracted its internal serial number, and matched it to the serial number embedded in the photo. It was the same device. The photo had been taken with that specific phone, then transferred to the laptop. The suspect’s story fell apart immediately.</p><p>That is the power of metadata. It tells the story the suspect does not want told. Your job is to listen to what the file is saying.</p><h3>Practical Exercise: The “Where in the World” Geolocation Capstone</h3><p>Alright. You have absorbed the theory. You understand foreground analysis, background analysis, the checklist approach, and the annotation standard. Now it is time to prove you can actually do this.</p><p>This exercise is not a quiz. It is a simulation of what a real investigation demands. You are going to receive an image. Your job is to answer three questions with absolute precision. But more importantly, your job is to show your work.</p><h4>The Scenario</h4><p>An image has surfaced on an obscure forum. The user who posted it claims it was taken “somewhere in Europe” and offers no further details. The image itself appears to show a scene of some significance. Your task is to determine exactly where this image was captured, identify what incident is connected to that location, establish the timestamp of that incident, and confirm the country.</p><p>But here is the thing. Anyone can guess a country. Anyone can drop a pin randomly and hope it lands close. That is not what we do.</p><h4>Your Deliverables</h4><p>You will produce a concise intelligence report containing the following:</p><p><strong>1. The Exact Location</strong><br>Provide coordinates. Not a neighborhood. Not a city. I want latitude and longitude. The kind you can paste into Google Earth and land directly on the spot where the photographer stood. If you give me a city name without coordinates, you have not finished the job.</p><p><strong>2. The Incident Behind the Image</strong><br>This location has a story. Something happened there. It might be a crime scene. It might be the site of a protest. It might be connected to a historical event. Your job is to research the location and identify the specific incident that makes this image relevant. What happened at this place? Why does it matter? Provide a brief, factual summary with sources.</p><p><strong>3. The Timestamp of the Incident</strong><br>When did this incident occur? I want a date, and if the information is available, a time. Not when the image was posted. Not when someone wrote an article about it. The actual date and time the event took place. If you can not find an exact time, explain why, but give me the most precise date you can confirm.</p><p><strong>4. The Country</strong><br>This should be straightforward after everything above, but state it clearly. No ambiguity.</p><h4>The Annotation Requirement</h4><p>This is non-negotiable.</p><p>Alongside your written answers, you will provide an annotated comparison image. Take a screenshot of the original image and a screenshot of the same location from Google Earth Pro, Google Street View, or satellite imagery. Place them side by side. Then, using any markup tool you have, highlight the points of correlation.</p><p>Draw arrows. Circle matching structures. Label distinctive features. Show me the crack in the pavement visible in both. Show me the unique roofline. Show me the arrangement of windows. Show me at least three distinct matching points that prove your geolocation is correct.</p><p>If you submit coordinates without an annotated verification image, your work is incomplete.</p><h4>What I am Looking For</h4><p>I am not just testing your ability to find a location. I am testing your process. Your annotation tells me whether you actually worked through the clues or just got lucky. Your incident research tells me whether you understand that geolocation is only valuable when it provides context. Your timestamp tells me whether you can distinguish between when an image was captured and when an event occurred.</p><p>This is what a client would expect. This is what a court would demand. This is the standard.</p><h4>The Image:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*IP-rxQKcSINCuX93N2TSxQ.png" /></figure><h3>Submission Format</h3><h4>Your submission should follow this structure:</h4><ul><li><strong>Location Coordinates</strong>: [Latitude, Longitude]</li><li><strong>Country</strong>: [Country Name]</li><li><strong>Incident Description</strong>: [Brief, factual summary with sources cited]</li><li><strong>Incident Timestamp</strong>: [Date and time, with explanation of source]</li><li><strong>Annotated Verification</strong>: [Side-by-side image with correlation points clearly marked]</li><li>Report to be submitted to <strong>cybershieldmentor@gmail.com</strong></li></ul><p>Take your time. Be methodical. Check your work. And remember, if you can not prove it, you do not have it yet.</p><h3>Module 3: Email &amp; Username Intelligence: The Digital Skeleton</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*9agoDTSVf31IPM5ZGPegVw.png" /></figure><p>If you have been paying attention so far, you know that every investigation needs a starting point. Sometimes you have a name. Sometimes you have a phone number. But very often, what you actually have is an email address or a username. And here is the thing most investigators do not fully appreciate: an email address is not just a way to contact someone. It is a skeleton key. Woven into that single string of characters is an entire digital life waiting to be mapped.</p><p>This module is about extracting every possible drop of intelligence from an email address or a username. We will start with the address itself, breaking it down to understand what it tells us before we even run a single search. Then we will move into verification techniques that reveal hidden recovery details without alerting the target. Finally, we’ll tackle username-driven attribution, where a single pseudonym becomes the thread that unravels a person’s entire online presence.</p><p>By the end of this module, you will not look at an email address the same way again.</p><h4>Lecture 3.1: Email Deconstruction &amp; Intelligence</h4><p>Before you plug an email into any tool, any database, any search engine, stop. Look at the address itself. The structure of an email contains intelligence, and if you skip this step, you are leaving free information on the table.</p><p>Every email address has two parts: the <strong>local </strong>part, which is everything before the <strong>@ symbol</strong>, and the <strong>domain </strong>part, which is everything after it. Let us break both down.</p><h4>Local-Part Analysis</h4><p>The local part is chosen by the user or assigned by an organization. It is personal. It often reflects how the person sees themselves or how they want to be seen. That makes it a behavioral artifact, and behavioral artifacts are intelligence.</p><h4>Start by categorizing what you are looking at</h4><p><strong>Is it a name-based pattern</strong>? Something like <strong>john.doe@</strong>, <strong>jdoe@</strong>, <strong>doe.john@</strong>, <strong>john.doe84@</strong>. If so, you now have a probable first name, last name, and possibly a birth year or significant number. Right out of the gate, with zero tools, you have extracted personal identifiers. Document everything. John. Doe. Possibly born in <strong>1984</strong>. These become your pivot points later.</p><p><strong>Is it a profession or interest-based handle</strong>? Something like <strong>cyberwolf.security@ </strong>or <strong>tokyo.photographer@</strong>. This tells you how the person identifies. They see themselves as a security professional or a photographer based in Tokyo. Whether that is true or aspirational does not matter yet. What matters is this gives you keywords to search, forums to check, and a psychological profile to build.</p><p><strong>Is it a random alphanumeric string</strong>? Something like <strong>xz17q42@</strong>. This often indicates a throwaway account, a service-generated address, or someone with operational security awareness. Random strings do not happen by accident. If someone is using an address with no personal connection, ask yourself why. What are they trying to hide?</p><p><strong>Is it a combination</strong>? Maybe <strong>john.xz17q42@</strong>. That is interesting. The local part starts personal, then becomes random. This could indicate a corporate naming convention mixed with an employee ID, or it could indicate someone who started with their real name and added obfuscation. Either way, it is a pattern worth noting.</p><h4><strong>Here is a practical example</strong></h4><p>You are investigating a phishing email that came from <strong>sarah.consulting.2023@</strong>. Right away, you know a few things. The name <strong>Sarah </strong>is likely fake or the operator&#39;s real name. The word &quot;<strong>consulting</strong>&quot; suggests a business facade. The number 2023 suggests the account was created that year. This tells you the account is likely purpose-built and recent. You are not dealing with someone&#39;s decade-old personal inbox. You are dealing with a disposable operational asset. That is valuable context before you have run a single search.</p><h4>Domain Analysis</h4><p>Now shift your attention to the domain part. This tells you where the email lives, and that opens up a whole new investigation path.</p><p>Start simple. Is it a free provider like Gmail, Yahoo, Protonmail, or Outlook? If so, the domain itself will not tell you much about the user’s affiliation, but the choice of provider can. <strong>Protonmail </strong>suggests privacy consciousness. A legacy <strong>Yahoo </strong>address suggests an older account or an older user. <strong>Gmail </strong>is the default for most. These are small signals, but signals add up.</p><p>If the domain is custom, like <strong>@companyname.com</strong>, you now have an organizational affiliation. That is huge. You can investigate the company itself, find employees, map the corporate structure, and potentially identify your target through organizational context alone.</p><p>Now dig deeper into that domain. The first technical step is checking MX records, which stands for Mail Exchange records. These DNS records tell you which servers handle email for that domain. This can reveal whether the domain uses Google Workspace, Microsoft 365, or a self-hosted mail server. A self-hosted server might expose the organization’s IP address range, server software, and potential vulnerabilities. Even knowing they use Google Workspace tells you their login portal is at a standard URL, which can be useful later.</p><p>To check MX records, you can use command-line tools like <strong>dig </strong>or <strong>nslookup</strong>, or you can use any online MX lookup tool. The command is simple:</p><p><strong>dig mx targetdomain.com</strong></p><p>The output shows you the mail servers and their priority order. Read it. Understand it. Add it to your intelligence file.</p><p>Next, <strong>WHOIS history</strong>. Current WHOIS data is often redacted due to privacy protections, but historical WHOIS records are a different story. Tools like <a href="https://whois.domaintools.com/"><strong>whois.domaintools.com</strong></a><strong> </strong>let you look up historical registration data for a domain. You might find the name, address, phone number, and email of the person who registered the domain years ago, before privacy protections were in place or before they thought to enable them.</p><p>I have found personal phone numbers in WHOIS records from 2015 that still worked in 2024. People change their numbers less often than you would think. I have found home addresses. I have found alternative email addresses used during registration that led to entirely new investigation paths.</p><p>Associated IP address space is the final piece. When you look up a domain, find the IP addresses it resolves to. Then check what other domains are hosted on those same IPs. Reverse IP lookup tools can show you every website sharing that server. A target might have one domain you know about and five others you do not, all sitting on the same IP. That is how you uncover hidden infrastructure.</p><h4>Lecture 3.2: The Forgotten Art of Verification &amp; Password Reset Intel</h4><p>Now let us talk about something most courses skip entirely. Before you dive into massive automated searches across hundreds of platforms, there is a quiet, precise, and extremely effective technique you need to master. I call it the “<strong>no-click</strong>” method, and it is all about using the password reset and account recovery flows built into major email providers to extract intelligence without ever alerting your target.</p><h4>The “No-Click” Dork for Google and Yahoo</h4><p>Here is how it works. When you go to Google’s account recovery page and enter an email address, Google asks you to confirm your identity. But before you do anything, Google often displays a partially obscured recovery email or phone number associated with that account. You will see something like <strong>j*****e@gmail.com</strong> or a phone number ending in <strong>**23</strong>.</p><p>You have not clicked anything. You have not triggered any notification. The target has no idea you are doing this. Yet you have just learned that their recovery email starts with a<strong> J</strong> and ends with an <strong>E</strong>, or that their phone number ends in <strong>23</strong>. That is intelligence.</p><p>Now take it further. If you see <strong>j*****e@gmail.com</strong>, and you already suspect the target&#39;s name is <strong>John Doe</strong>, you can make an educated guess that the recovery email is something like <strong>johndoe@gmail.com</strong>. You can then investigate that address separately. You have just pivoted from one email to another without sending a single alert.</p><p>Yahoo’s recovery flow works similarly. Microsoft’s does too, though they have tightened things in recent years. The key is to approach the recovery page, observe everything displayed on the screen, and document it carefully. You are not bypassing security. You are reading what the page voluntarily shows you before you authenticate. That is passive intelligence gathering at its finest.</p><h4>A practical walkthrough</h4><p>You have a target email: <strong>unknownuser@gmail.com</strong>. You navigate to Google&#39;s account recovery page at <a href="http://accounts.google.com/signin/recovery"><strong>accounts.google.com/signin/recovery</strong></a>. You enter the email. The next page shows &quot;Get a verification code&quot; with options to send to a recovery email or phone. The recovery email is partially redacted: <strong>m*****l@yahoo.com</strong>. You now know the target&#39;s backup email is a Yahoo address, and you can see the first and last characters. If you know the target&#39;s name is Michael, you just confirmed a connection. If you did not know the name, you now have a strong lead.</p><h4>“Create Account” Probing</h4><p>This is a related technique that works across virtually every platform. When you attempt to create a new account using a target email address, most sites will tell you if that email is already registered. They do this to prevent duplicate accounts, but for an investigator, it’s a presence checker.</p><h4><strong>The process is simple</strong></h4><p>Go to a site’s sign-up page. Enter the target email. If the site throws an error like “<strong>An account with this email already exists</strong>,” you have just confirmed the target has an account there. If it proceeds to the next step asking for a password, the email is not registered.</p><p>Now, I need to be clear about the ethical boundary here. This should be done manually, sparingly, and only on major platforms relevant to your investigation. You are not running a script that tests 500 sites. You are checking a handful of key providers like Facebook, LinkedIn, Instagram, Twitter, Amazon, and a few others based on your investigative needs. This is about targeted intelligence, not mass data harvesting.</p><h4><strong>Why does this matter</strong>?</h4><p>Because if you discover your target has an Amazon account under an email that seems otherwise inactive, you now have another platform to investigate. If they have a LinkedIn account, you have professional history. If they have an Instagram account, you have personal photos and social connections. Each confirmed registration is a new door to walk through.</p><h4>Lecture 3.3: Username-Driven Attribution</h4><p>Now we shift from email to usernames. This is where the investigation often becomes truly expansive, because while people might have a few email addresses, they often have dozens of accounts scattered across the internet, many of them tied to a single username or a predictable set of variations.</p><h4>The Single Username is the Key</h4><p>People are creatures of habit. When someone creates an online identity, they tend to reuse the same username or small set of usernames across multiple platforms. This is not laziness. It is human psychology. We like consistency. We like being recognizable. We like not having to remember fifty different login names.</p><p>This means a single username can unlock an entire digital footprint. But you need to understand how people create these names in the first place.</p><p><strong>Some usernames are identity-based — </strong><strong>john.doe</strong>, <strong>john_doe84</strong>, <strong>doe.john</strong>. These directly reflect the person&#39;s real name. If you already know the target&#39;s name from email analysis or other sources, generating these variations is straightforward.</p><p><strong>Some usernames are persona-based —</strong> <strong>silentwolf</strong>, <strong>night_crawler_adventures</strong>, <strong>cyber_panther</strong>. These reflect an interest, a self-image, or a subculture affiliation. A username like <strong>silentwolf </strong>might indicate interest in wolves, nature, or a particular gaming community. <strong>cyber_panther</strong> suggests an interest in hacking culture or cybersecurity. These keywords become additional search terms and community indicators.</p><p><strong>Some usernames are hybrid — </strong><strong>john.silentwolf</strong>. This combines a real name with a persona. These are especially valuable because they bridge the gap between someone&#39;s real identity and their chosen online persona.</p><p>When you encounter a username, spend time thinking about it before you start searching. What does this name say about the person who chose it? What communities might they belong to? What other variations might they use?</p><h4>Permutation Engines: The Logic Behind the Script</h4><p>This is where we move from theory to practice. If a target uses <strong>silentwolf_adventures</strong> on one platform, they might use <strong>silentwolf</strong>, <strong>silent.wolf</strong>, <strong>silent_w0lf</strong>, <strong>silentwolf_hiker</strong>, or <strong>the_silent_wolf</strong> on others. These are not random guesses. They follow predictable patterns.</p><p>Let me teach you the logic so you understand what a permutation engine is actually doing, whether you build one yourself or use an existing tool.</p><h4>The patterns fall into categories</h4><p><strong>Character substitution</strong> — is replacing letters with similar-looking numbers or symbols. <strong>o </strong>becomes <strong>0</strong>. <strong>e </strong>becomes <strong>3</strong>. <strong>a </strong>becomes <strong>4</strong>. <strong>i </strong>becomes <strong>1</strong>. So <strong>silentwolf</strong> could become <strong>silentw0lf</strong>, <strong>s1lentwolf</strong>, or <strong>silentw0lf</strong>.</p><p><strong>Separator variation</strong> — is changing how words connect. Underscores become periods become hyphens become nothing. <strong>silent_wolf</strong> becomes <strong>silent.wolf</strong>, <strong>silent-wolf</strong>, <strong>silentwolf</strong>.</p><p><strong>Suffix and prefix addition — </strong>is appending or prepending numbers, years, or keywords. <strong>silentwolf</strong> becomes <strong>silentwolf84</strong>, <strong>the_silentwolf</strong>, <strong>silentwolf_official</strong>, <strong>silentwolf_adventures</strong>.</p><p><strong>Word order reversal</strong> — is flipping the sequence. <strong>silentwolf</strong> becomes <strong>wolfsilent</strong>.</p><p><strong>Truncation and abbreviation</strong> — is shortening the name.<strong> </strong><strong>silentwolf</strong> becomes <strong>silent</strong>, <strong>swolf</strong>, <strong>silentw</strong></p><p>A proper permutation engine applies these rules systematically to generate a list of candidate usernames — <a href="https://mailmeteor.com/email-permutator"><strong>https://mailmeteor.com/email-permutator</strong></a>. The logic is rule-based, not random, because human creativity follows patterns. Once you understand the patterns, you can predict what variations a target is likely to use.</p><h4>Here is a practical example. Target username: dark_phoenix_88</h4><p>Immediate observations: “<strong>dark</strong>” and “<strong>phoenix</strong>” are persona words, likely indicating interest in mythology, gaming, or hacker culture. “<strong>88</strong>” is likely a birth year or a significant number. The underscores suggest the user is comfortable with that separator style.</p><h4><strong>Permutations to check</strong>:</h4><p><strong>darkphoenix88</strong>, <strong>dark.phoenix.88</strong>, <strong>dark-phoenix-88</strong>, <strong>darkphoenix1988</strong>, <strong>dark_phoenix</strong>, <strong>phoenix_dark_88</strong>, <strong>d4rk_phoenix_88</strong>, <strong>dark_ph03nix_88</strong>, <strong>the_dark_phoenix</strong>, <strong>dark_phoenix_official</strong>.</p><p>Each of those is a query waiting to happen. You can generate these manually, but the process is repetitive and eats time you should be spending on analysis. The smarter approach is to split the target username into its base components, feed them into a permutation engine or an LLM with a structured prompt, and let it generate the full list of rule-based variations for you.</p><h4>Example given below:</h4><p>Using the email permutation <strong>web-based tool — MailMeteor: </strong><a href="https://mailmeteor.com/email-permutator">https://mailmeteor.com/email-permutator</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iISt5bw9sw7BLSZ6fk8qBA.png" /></figure><p>Using LLM: <strong>Gemini</strong>, <strong>ChatGPT</strong>, etc</p><ul><li><a href="https://gemini.google.com/">https://gemini.google.com</a></li><li><a href="https://chatgpt.com/">https://chatgpt.com</a></li><li><a href="https://chat.deepseek.com/">https://chat.deepseek.com</a></li></ul><p><strong>Target Identity Email Permutation Analysis — simple logic</strong></p><p>“As an OSINT investigator, I require a comprehensive email permutation matrix for the target identity <strong>‘Chris Evans</strong>’ across major providers like Gmail and Yahoo to map and uncover the subject’s digital footprint.”</p><p>You can adjust the above to fit the context of your investigation.</p><h4>OUTPUTS:</h4><h4>1. Core Structural Permutations</h4><p>These patterns use standard naming conventions with common separators (<strong>.</strong>, <strong>_</strong>, <strong>-</strong>, or no separator).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0wobriCbtgwjsxXjKlUWkg.png" /></figure><h4>2. Common Appendices (Year / Numbers)</h4><p>If the baseline names are taken, users frequently append birth years, graduation years, or sequential numbers.</p><h4>Common Year Formats (Assuming 1970–2005 range)</h4><p>Replacing <strong>YY</strong> with 2-digit years (e.g., <strong>81</strong>, <strong>92</strong>, <strong>00</strong>) and <strong>YYYY</strong> with 4-digit years (e.g., <strong>1981</strong>, <strong>1995</strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2AW2LGunE3gflaS9P5Qz9g.png" /></figure><p>Once you have the output, your job is to run those usernames through your search tools { <strong>Epieos</strong>, <strong>Intelbase</strong>, <strong>BehindTheEmail }</strong>, and manually verify each hit for intelligence value. The machine generates the possibilities. You do the investigative thinking.</p><h4>Practical Tooling: Going Beyond the Button</h4><p>Now, there are tools that automate username searching across platforms. <strong>Sherlock</strong>, <strong>Maigret</strong>, <strong>WhatsMyName.app</strong>. These are useful, but I need you to understand something critical. The tool is not the investigator. You are!</p><p><strong>Sherlock </strong>takes a username and checks it against a list of sites. <strong>Maigret </strong>does the same with more advanced features and better reporting. <strong>WhatsMyName.app</strong> is a web-based alternative with a large database of sites to check.</p><p>Here is the problem with how most people use these tools. They type a username, press enter, and then scroll through the results looking for green checkmarks. They find a list of “<strong>found</strong>” profiles and call it done. That is not analysis. That is data collection.</p><p>When you run one of these tools and get results, your real work is just beginning. You need to <strong>parse the output manually</strong>. Visit each found profile. Look at the <strong>content</strong>. Does the<strong> writing style match your target</strong>? Are the<strong> interests consistent</strong>? Are the p<strong>rofile pictures the same or similar</strong>? When was the<strong> account created</strong>? When was it <strong>last active</strong>? Does it <strong>link </strong>to other<strong> accounts or platforms</strong>?</p><p>A tool might tell you <strong>silentwolf</strong> exists on Reddit, Twitter, Instagram, and a hiking forum. That is a list. Your job is to determine whether those accounts all belong to the same person, and if so, what the connections are between them.</p><p>The tool saves you the time of manually typing <strong>silentwolf</strong> into fifty different signup pages. That is valuable. But the analysis, the attribution, the link-building. That is all you.</p><h3>Practical Exercise: Operation SHADOW TRACE</h3><p>Now it is time to put everything from this module into practice. This exercise is designed to test your ability to start with almost nothing and build a complete attribution picture.</p><p><strong>Classification</strong>: TRAINING EXERCISE // OSINT-2026–042<br><strong>Threat Vector</strong>: Anonymous Harassment / Cyberstalking<br><strong>Target</strong>: Public Figure (Victim)<br><strong>Subject</strong>: @Allen123 / @Allen3sop1 (Threat Actor)<br><strong>Objective</strong>: Identify the real-world identity and location of the threat actor through progressive open-source intelligence techniques.</p><h4>Intelligence Brief</h4><p>A public figure has received a direct message from the locked X (Twitter) account <strong>@Allen123</strong> containing the following threat:</p><blockquote><em>“Last warning. Stop your public appearances, or I’ll make sure your next morning walk ends differently.”</em></blockquote><p>The account presents a dead end for standard social media review. It is locked. It has zero followers. The profile image is a generic cartoon avatar. The bio reads: <em>“My main account </em><strong><em>Allen123 </em></strong><em>got banned. Follow me on my new account.”</em> The account follows only five others.</p><p>Intelligence further indicates the subject has become aware of investigative scrutiny. As a counter-surveillance measure, the active username has been rotated to <strong>@Allen3sop1</strong>. Despite this operational security maneuver, enumeration efforts have successfully leveraged the legacy handle Allen123 as the primary pivot point for historical cross-platform correlation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*QZRYvctXIMuqHRsh.png" /><figcaption>“Digital breadcrumbs are the unintentional map of a person’s online life. Enumerating these accounts allows us to connect the dots between anonymous aliases and real-world identities, ensuring no part of the target’s digital presence remains siloed.”</figcaption></figure><h3>Your task is to unmask this individual</h3><h4>Phase 1: Initial Reconnaissance</h4><p>An anonymous account with no public engagement and a locked profile offers nothing through standard review. You must collect foundational metadata passively, without interaction or authentication requests.</p><p><strong>Mission</strong>: Enumerate the account’s unique numeric ID and exact creation timestamp to establish a temporal baseline.</p><p><strong>Flag Format</strong>: OSINT{account_id_account_creation_timestamp}</p><h4>Phase 2: Username Pivot &amp; Cross-Platform Enumeration</h4><p>Threat actors frequently recycle handles or variations across services. The suffix “123” may indicate a birth year, a significant date, or padding to secure a unique username.</p><p><strong>Mission</strong>: Search major social platforms, forums, and code repositories for all profiles utilizing the string “<strong>Allen123</strong>” or logical derivatives.</p><p><strong>Flag Format</strong>: OSINT{target_platforms_found_@handles}</p><h4>Phase 3: Visual Intelligence &amp; Travel Pattern Analysis</h4><p>Content from alternative platforms reveals the subject has inadvertently shared geolocatable imagery.</p><p><strong>Mission</strong>: Analyze public media uploads to identify:</p><ol><li>The specific park or trail where the subject habitually takes a “morning walk.”</li><li>The name of the hotel the subject booked and the prominent landmark visible directly opposite their room window.</li></ol><p><strong>Flag Format</strong>: OSINT{trail_location_coordinates_hotel_name_landmark_name}</p><h4>Phase 4: Geospatial Analysis</h4><p>A photograph taken from inside the subject’s hotel room provides a clear line of sight to a distinct architectural structure.</p><p><strong>Mission</strong>: Using Google Earth Pro or QGIS, establish a precise visual line-of-sight between the hotel coordinates and the identified landmark. Calculate the straight-line ground distance from the subject’s observation point to the structure.</p><p><strong>Flag Format</strong>: OSINT{hotel_name_distance}</p><h4>Phase 5: Target Email Lookup</h4><p>A clue left in a comment section suggests the subject maintains a personal blog or manifesto site expressing political views outside their main social channels.</p><p><strong>Mission</strong>: Conduct deep web searches to uncover the personal email address associated with the subject’s alternative online presence.</p><p><strong>Hint</strong>: The target email is encoded with a Caesar cipher. Decode it to reveal the real address — (target email domain is gmail.com).</p><p><strong>Flag Format</strong>: OSINT{target_email_address}</p><h4>Phase 6: Property Records &amp; Identity Attribution</h4><p>With the subject’s real name obtained, shift to public government records to confirm physical presence and demographic data.</p><p><strong>Mission</strong>: Cross-reference the name against public record aggregators to establish a comprehensive identity profile.</p><p><strong>Flag Format</strong>: OSINT{target_real_name_current_address_age_phone_number_property_relative}</p><h4>Phase 7: Social Media Attribution &amp; Visual Confirmation</h4><p>A concrete link between the anonymous persona and the identified individual requires irrefutable visual or content-based correlation.</p><p><strong>Mission</strong>: Compile a short-form evidence correlation report.</p><p><strong>Correlation Sample — Example</strong>:<br><em>The cartoon image used as @Allen123’s profile header on X matches the SHA-1 hash and EXIF thumbnail data of a photograph posted to [Subject Name]’s Facebook timeline dated [Date]. This constitutes direct visual attribution; the subject reused proprietary personal imagery across both anonymous and verified accounts.</em></p><h4>Report:</h4><ul><li>Evidence Item 1: ____________________________________</li><li>Evidence Item 2: ____________________________________</li><li>Evidence Item 3: ____________________________________</li></ul><h4>Phase 8: Timeline Synthesis &amp; Attribution Report</h4><p>Finalize the investigation into a coherent, evidence-based narrative suitable for legal or internal security referral.</p><p><strong>Mission</strong>: Construct a chronological synthesis of events and produce a final attribution statement.</p><p><strong>Timeline Synthesis</strong>:</p><p><strong>Date____________________Event</strong></p><p>_______________________________________________</p><p>_______________________________________________</p><h4>Final Attribution Statement:</h4><p><em>The anonymous X account @Allen123 is operated by [Subject Full Legal Name], DOB [MM/DD/YYYY], residing at [Full Address]. Attribution is established through: (1) Cross-platform username correlation linking X to [Alternative Platform], (2) Geospatial analysis confirming travel history consistent with hotel booking records, (3) Public property and voter registration records confirming identity and residence, and (4) Visual match of specific imagery between the anonymous account and the subject’s verified personal accounts.</em></p><p><strong>Final Flag</strong>:</p><p>OSINT{target_real_name_country_current_location_account_handles_found_relative}</p><h4>Intelligence Summary</h4><p><strong>Field_______________________Value</strong></p><ul><li>Subject Name ____________</li><li>Country of Residence ______________________</li><li>Current Location _____________________</li><li>Anonymous Handle ___ @Allen123</li><li>Linked Accounts ______________</li><li>Time to Attribution ___________________</li><li>Legal Status ___ Pending Referral</li></ul><h4>Submission Requirements</h4><ul><li>Completed phase flags (Phases 1–8).</li><li>Evidence correlation report (Phase 7).</li><li>Timeline synthesis and final attribution statement (Phase 8).</li><li>Entity graph visualization (link chart) mapping all discovered accounts and their connections to the identified individual.</li><li>Submit all deliverables via secure training email: <strong>cybershieldmentor@gmail.com</strong></li></ul><p><strong>Disclaimer</strong></p><p>This OSINT challenge is designed for educational and training purposes only. All scenarios, entities, email addresses, domains, and geospatial references are either fictional, reconstructed from publicly available information, or used solely as instructional examples within a controlled environment.</p><p>Happy ethical hunting, analysts.</p><h4>Going Deeper: A Resource I Wrote for You</h4><p>Before we close out this lecture on dorking syntax, I want to point you toward a resource I created specifically to deepen your understanding of what we just covered.</p><p>I wrote an article called <strong>How To Investigate A Person Of Interest In 2026</strong>, and I did not write it to give you a list of tools to memorize. I wrote it to teach you how to think. How to approach a target with logic instead of guesswork. How to see tools and operators not as commands, but as building blocks you can combine and recombine for effective intelligence collection.</p><p>In that piece, I break down the mental framework behind investigating a person of interest that surface what others miss. I walk through real examples and show the thought process behind each tools, because once you internalize that process, you stop needing cheat sheets. You start building your own methodologies, techniques, and tools tailored to whatever investigation is in front of you.</p><p>If you want to go beyond what we covered today and really sharpen your search game, take the time to study it.</p><p>Here is the link:<strong> </strong><a href="https://preciousvincentct.medium.com/how-to-investigate-a-person-of-interest-in-2026-77dfaadbe7e7"><strong>https://preciousvincentct.medium.com/how-to-investigate-a-person-of-interest-in-2026-77dfaadbe7e7</strong></a></p><p>Read it carefully. Practice the techniques. That is how you move from knowing merely about tools to mastering them for effective intelligence collection.</p><h3>Module 4: Social Media Intelligence (SOCMINT): Deep Dive &amp; Platform-Specific Tactics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6PyKmDH4DgR6dg0uVFjrPA.png" /></figure><p>Social media is where people live their lives out loud. They post their opinions, their locations, their relationships, their frustrations, their achievements. For an investigator, this is not just data. This is behavioral gold. Every platform has its own architecture, its own quirks, its own hidden data layers. Knowing how to exploit each one individually is what separates a SOCMINT operator from someone who just scrolls through profiles.</p><p>This module is built for mastery. We go platform by platform, covering exact techniques for user ID extraction, attribution, search methodology, and evidence collection. No theory without practice. No tool without understanding what it’s doing under the hood.</p><p>By the end, you will not need a checklist. You will know where to look because you understand how each platform structures its data and how users behave within it.</p><h4>Lecture 4.1: Facebook — The Graph API and Beyond</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8rlmh1y_x7rYQ9Zj0srFAg.png" /></figure><p>Facebook is the most data-rich platform on the planet for OSINT investigators, and most people only scratch the surface. The key to Facebook intelligence is understanding that every users on the platform has a <strong>numeric ID</strong>, and that ID is globally unique, unchangeable, and often exposed in places users never check.</p><h4>User ID Extraction: The Core Technique</h4><p>Every Facebook profile, page, group, photo, comment, and like has a numeric ID. This ID never changes, even if the user changes their vanity URL, their name, or their profile picture. If you capture the ID once, you can track that entity forever.</p><h4>Method One: <strong>View Page Source technique</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KE6ZT3hKM0BH8Fw8ybmkIg.png" /></figure><p>Navigate to any Facebook profile. Right-click and select <strong>View Page Source</strong>. Inside that HTML, press <strong>Ctrl + F </strong>and<strong> </strong>search for <strong>profile_id</strong> or <strong>userID </strong>or simply <strong>&quot;id&quot;:&quot;</strong>. You will find something like &quot;<strong>profile_id&quot;:&quot;100000123456789</strong>&quot; { Example given in the image above }. That number is the target&#39;s unchangeable Facebook ID. Copy it. Document it. It will outlast any username change.</p><h4>Method Two: Vanity URL</h4><p>This works when you only have a vanity URL. Facebook allows custom URLs like <strong>facebook.com/john.doe</strong>. Behind that friendly name is still a numeric ID. Use the Facebook ID finder tools available online { <a href="https://lookup-id.com/"><strong>https://lookup-id.com</strong></a><strong> </strong>} to automate this process, or use a simple API call to <strong>graph.facebook.com/john.doe</strong> which returns a JSON object containing the numeric ID. This is passive, and unfortunately, it is no longer working as before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5uWrKenl3D4EMwXHQdoSQ.png" /></figure><h4>Method Three: Profile Picture URL Analysis — Explained with Examples</h4><p>Let me walk you through exactly how to extract intelligence from a Facebook profile picture URL. This method works because Facebook stores images on its Content Delivery Network, and the file-naming structure embeds identifiers that are unique to each user. You just need to know how to read them.</p><h4>Step 1: Open the Profile Picture</h4><h4>Method A: Right-Click (Quick, When Available)</h4><p>Go to any public Facebook profile. Right-click directly on the profile picture and select “<strong>Open image in new tab</strong>.” Do not right-click and save. Do not screenshot. You want the direct URL to the image file itself, not a download, not a screen capture. If the option appears, click it, and the image will open in its own tab with the full CDN URL visible in the address bar. Copy that URL. That is your data.</p><h4>Method B: Inspect Element (The Reliable Fallback)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TejOL4nOUhM2_knQDWEz4A.png" /></figure><p>Sometimes Facebook’s front-end code blocks the right-click option or overlays interactive elements on top of the profile picture. When that happens, the Inspect Element method gets you there anyway. Here is how.</p><p>First, right-click anywhere on the page background, not on the image itself. Select “<strong>Inspect</strong>” or “<strong>Inspect Element</strong>” from the menu. This opens the browser’s developer tools panel.</p><p>Now, look at the top left corner of that developer tools panel. You will see a small icon that looks like a <strong>dotted square</strong> with a <strong>cursor arrow</strong>. This is the element selector tool. You can also activate it with the keyboard shortcut <strong>Ctrl + Shift + C</strong>. Click that icon once. Your cursor is now in inspection mode.</p><p>Move your cursor over the target’s profile picture and click on it. The developer tools panel will jump to the specific line of HTML code that renders that image. You are looking for an attribute called<strong> </strong><strong>xlink:href</strong> within an <strong>&lt;image&gt;</strong> tag, or a standard <strong>src</strong> attribute within an <strong>&lt;img&gt;</strong> tag. It will look something like this:</p><pre>xlink:href=&quot;https://scontent.flos5-1.fna.fbcdn.net/v/t39.30808-6/456789012_1016123456789_987654321_n.jpg?_nc_cat=111...&quot;</pre><p>Double-click the URL inside the quotation marks to select it fully. Copy it. That is your direct CDN link. Open it in a new tab, and you will see the exact same image file, isolated, with the full URL visible in the address bar. This is the URL you will analyze in Step 2.</p><h4>Why This Method Matters</h4><p>The Inspect Element approach bypasses any right-click restrictions Facebook might implement. It also gives you the raw URL directly from the page source, including any parameters Facebook appends. You do not need to rely on the browser’s context menu. You go straight to the code and pull what you need. That is the investigator’s mindset. When one path closes, you find the one the developers left open.</p><h4>Step 2: Read the URL Structure</h4><p>The URL you get will look something like this:</p><pre>https://scontent.flos5-1.fna.fbcdn.net/v/t39.30808-6/456789012_1016123456789_987654321_n.jpg?_nc_cat=111&amp;ccb=1-7&amp;_nc_sid=abc123&amp;_nc_ohc=xyz789&amp;_nc_ht=scontent.flos5-1.fna&amp;oh=00_AQHDKSLSJDKEI...</pre><p>I know it looks like a mess. Let me break it down.</p><h4>The Base URL Before the Question Mark:</h4><pre>https://scontent.flos5-1.fna.fbcdn.net/v/t39.30808-6/456789012_1016123456789_987654321_n.jpg</pre><p>This is the important part. Everything after the question mark is tracking and session parameters. You can strip those. The core filename is:</p><p>You can strip those. The core filename is:</p><pre>456789012_1016123456789_987654321_n.jpg</pre><h4>Step 3: Decode the Filename Structure</h4><p>Facebook profile picture filenames follow a pattern of three numeric segments separated by underscores, ending with <strong>_n.jpg</strong>.</p><p>Let me use a real example from a test profile. Here is an actual Facebook profile picture filename:</p><pre>123456789_987654321098765_654321098765432_n.jpg</pre><h4>Break it down.</h4><p>The first segment, <strong>123456789</strong>, is the most valuable. In many cases, this is one of three things:</p><ul><li>The user’s Facebook numeric ID directly.</li><li>A hash derived from the user’s ID that Facebook uses for CDN routing.</li><li>The photo’s unique object ID assigned by Facebook’s storage system.</li></ul><p>The second segment, <strong>987654321098765</strong>, is a random or sequential identifier Facebook assigns to the specific image crop or resolution version.</p><p>The third segment, <strong>654321098765432</strong>, is another internal identifier tied to the CDN node or image processing batch.</p><p>The <strong>_n</strong> suffix indicates it is a normalized, processed version of the original upload.</p><h4>Step 4: The Practical Application</h4><p>Now, here is why this matters for an investigation.</p><p>Say you are tracking a target who uses different names across platforms. On Facebook they are “<strong>John Doe</strong>.” On Instagram they are “<strong>vintage_bike_77</strong>.” You suspect they are the same person, but you need evidence.</p><p>You extract the Facebook profile picture URL and get the filename:</p><pre>100000987654321_456123789012345_789012345678901_n.jpg</pre><p>You extract the Instagram profile picture using a tool like <strong>imginn.com </strong>{ <a href="https://imginn.com/"><strong>https://imginn.com</strong></a> }or by inspecting the page source for the <strong>property=”og:image”</strong> field. The Instagram CDN filename is:</p><pre>100000987654321_456123789012345_789012345678901_n.jpg</pre><p>They match. Exactly. Not similar. Not “<strong>looks alike</strong>.” The same file, same CDN, same internal identifiers. That is not coincidence. That is the same <strong>Facebook account linked to an Instagram profile</strong>. The <strong>user connected</strong> their <strong>Instagram</strong> to their <strong>Facebook account</strong>, and Facebook stores the <strong>profile picture </strong>across <strong>both platforms </strong>using the same<strong> internal object ID</strong>.</p><p>In some cases, that first numeric segment is the user’s raw Facebook ID. Let me show you how to verify this.</p><p>Take the first segment from the filename: <strong>100000987654321</strong>. Now, construct a Facebook profile URL using that number directly:</p><pre>facebook.com/100000987654321<br><br>OR <br><br>https://www.facebook.com/100000987654321<br><br>OR<br><br>https://www.facebook.com/profile.php?id=100000987654321<br></pre><p>If it redirects to the target’s vanity URL or profile page, you just confirmed the ID. If the user ever changes their vanity URL, deletes their account and returns, or blocks you, you still have this numeric link. You can still track them.</p><p>Even if Facebook changes the CDN structure tomorrow, the logic remains the same. Files stored on a CDN carry identifiers. Those identifiers connect back to the uploader. Learn to read them, and you add another passive extraction method to your toolkit.</p><h4>Step 6: Documenting the Evidence</h4><p>For your investigation report, capture the following:</p><ul><li>The full CDN URL with timestamp of extraction.</li><li>The filename segments broken down and annotated.</li><li>If cross-platform, the matching filename from the second platform side by side.</li><li>Screenshot of both URLs with the matching segments highlighted.</li></ul><p>This is not circumstantial. This is technical evidence. The same file hash, same CDN path, same internal object ID appearing on two separate platforms proves the accounts share a single upload source. That is attribution.</p><h4>One More Thing</h4><p>This technique also works for Facebook Pages and Groups. When you open the profile picture of a Page, the same filename structure appears. If an anonymous Page is spreading disinformation, extracting the profile picture filename and cross-referencing it with other known assets can tie that Page back to an individual operator. I have used this. It works.</p><h4>Search Capabilities</h4><p>Facebook’s internal search is deliberately limited. Google, Yandex, etc is your external search engines for Facebook. Use the dork <strong>site:facebook.com &quot;public profile&quot; &quot;works at&quot;</strong> to find profiles associated with specific companies. Layer additional operators. <strong>site:facebook.com &quot;public profile&quot; &quot;lives in London&quot; &quot;works at Barclays&quot;</strong>. This pulls profiles that Facebook&#39;s own search might hide.</p><p>The About section is a transparency goldmine. Facebook logs the history of username changes, profile picture updates, and contact information. The “Recent Profile Pictures” album is particularly important because it is undeletable. Even if a user removes all their current photos, the “<strong>Recent Profile Pictures</strong>” album retains every profile picture they have ever used, in chronological order. This is a behavioral timeline sitting in plain sight.</p><h4>Practical Methodology:</h4><ul><li>Always extract the numeric ID first. It is your anchor.</li><li>Check the About section for transparency history and contact info.</li><li>Review “Recent Profile Pictures” for historical imagery.</li><li>Use Google dorks with <strong>site:facebook.com</strong> for external search.</li><li>Check public groups the target belongs to. Group membership is often visible and reveals interests, locations, and associations.</li></ul><h4>Lecture 4.2: LinkedIn — The Corporate Org Chart</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZpvwNocKOxV08PmJ3b-0A.jpeg" /></figure><p>LinkedIn is not a social network. Not for us. LinkedIn is an organizational mapping tool that happens to have a newsfeed. Every profile is a data point. Every job change is a timestamp. Every comment is a window into internal team dynamics and individual expertise.</p><p>Most investigators use LinkedIn wrong. They search a name, scroll the profile, and move on. That is surface-level. The real intelligence is in the hidden identifiers, the activity patterns, the cross-platform bridges, and the contact discovery tools that extract what LinkedIn tries to hide behind premium paywalls.</p><p>I am going to walk you through every technique, tool, and method you need to extract maximum intelligence from LinkedIn. Pay attention. This is dense, and every piece matters.</p><h4>Part 1: Discrete Search via Google</h4><p>LinkedIn limits what you see if you do not pay. They cap search results. They hide profiles outside your network. They notify users when you view them if you are logged in. Google does none of these things.</p><h4>The Google dork is your external search engine for LinkedIn. The base query is:</h4><blockquote><em>site:linkedin.com/in “company name”</em></blockquote><p>This returns every public LinkedIn profile associated with that company, current and former, without hitting LinkedIn’s internal search limits and without generating any profile view notifications. You are not on LinkedIn when you do this. You are on Google. That is passive.</p><h4><strong>Now refine. Add a title</strong>:</h4><blockquote><em>site:linkedin.com/in “company name” “security engineer”</em></blockquote><h4>Add a location:</h4><blockquote><em>site:linkedin.com/in “company name” “security engineer” “London”</em></blockquote><p>Add a date range using Google’s date filter under Tools. This catches profiles that were indexed during a specific period, which can help you find people who recently joined or left.</p><h4>Add boolean logic to broaden the net:</h4><blockquote><em>site:linkedin.com/in “company name” AND (“security” OR “cyber” OR “infosec”)</em></blockquote><p>This returns anyone in the security space at that company, regardless of exact title wording.</p><p>The key insight here is that you are not searching people. You are searching Google’s index of LinkedIn. Google crawled those profiles. Google stored them. You are just asking Google to show you what it already has. This is not hacking. This is not bypassing. This is using the tool that LinkedIn itself allowed to index its public profiles.</p><h4>Part 2: LinkedIn User ID Extraction</h4><p>Every LinkedIn profile has a unique identifier embedded in the page source. This ID is not the vanity URL. It is not the public profile link. It is a numeric or alphanumeric string that LinkedIn assigns internally. Extracting this ID allows you to track a profile even if the user changes their name, vanity URL, or headline.</p><h4>Here is the method.</h4><p>Navigate to any public LinkedIn profile. Right-click on the page background, not on any image or button. Select “<strong>Inspect</strong>” or “<strong>Inspect Element</strong>” to open the browser’s developer tools.</p><p>Now, inside the developer tools panel, press <strong>Ctrl + F</strong> to open the search bar within the HTML source. Search for the term <strong>urn:li:member: —</strong> You are looking for a line that contains something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8sSqhhWmpcu-6GYqphYVnA.png" /></figure><p>“member”:”123456789&quot;</p><h4>OR</h4><p>urn:li:fsd_profile:ACoAABc12345</p><p>The number after <strong>member </strong>or the string after <strong>urn:li:fsd_profile:</strong> is the internal LinkedIn profile ID. This ID is globally unique. It never changes. If the user deletes their account and recreates it with the same name, this ID will be different. But for the life of that profile, this ID is constant.</p><p>Another method is to look at the page source for <strong>objectUrn</strong>. Search for:</p><p><strong>“objectUrn”:”urn:li:member:123456789&quot;</strong></p><p>The numeric portion is the member ID.</p><h4>However, there are a few things to keep in mind:</h4><ul><li>The exact field name is <strong>not fixed</strong>. Depending on LinkedIn’s frontend version and the endpoint, you might see <strong>objectUrn</strong>, <strong>entityUrn</strong>, <strong>trackingUrn</strong>, <strong>profileUrn</strong>, or other URN fields.</li><li>LinkedIn frequently changes its frontend implementation, so a field that exists today may not exist tomorrow.</li><li>Not every <strong>objectUrn</strong> you find refers to the profile you&#39;re viewing. Some may identify posts, companies, comments, connection invitations, or other objects. You need to inspect the surrounding JSON to determine what object the URN represents.</li></ul><h4>For OSINT or debugging purposes, the approach is generally:</h4><ol><li>Open the profile you are authorized to view.</li><li>Inspect the page source or browser developer tools.</li><li>Search for terms like:</li></ol><ul><li>&quot;<strong>objectUrn</strong>&quot;</li><li>&quot;<strong>entityUrn</strong>&quot;</li><li>&quot;<strong>profileUrn</strong>&quot;</li><li>&quot;<strong>urn:li:member:</strong>&quot;</li><li>&quot;<strong>urn:li:fsd_profile:</strong>&quot;</li></ul><p>4. Verify from the surrounding data (such as the profile’s name, headline, or other attributes) that the URN corresponds to the profile you’re examining.</p><p>Why does this matter? Because many third-party LinkedIn tools and APIs use this internal ID rather than the public profile URL. If you are building a target list, storing the internal ID ensures you can always reference the correct profile, even if the vanity URL breaks.</p><h4>Part 3: LinkedIn Comment and Post ID Extraction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*myEDonPj7NJdQzEWFWS_YQ.png" /></figure><p>When a target comments on a LinkedIn post, that comment has its own unique ID. Extracting this allows you to track specific interactions, monitor threads, and map relationship networks.</p><p>Find a public post where the target has commented. Scroll to their comment. <strong>Right-click </strong>on the <strong>timestamp </strong>of the comment, the small text that says “<strong>3 days ago</strong>” or “<strong>1 week ago</strong>.” Select “<strong>Inspect Element</strong>.”</p><p>Inside the HTML, look for an attribute called <strong>data-urn</strong> or search for <strong>urn:li:activity:</strong> or <strong>urn:li:comment:</strong>. You will see something like:</p><pre>urn:li:comment:(activity:7123456789,123456789)</pre><p>The<strong> first number</strong> after <strong>activity:</strong> is the post ID. The <strong>second number</strong> is the <strong>comment ID</strong>. This tells you exactly which post they commented on and uniquely identifies that comment.</p><p>If you are tracking a disinformation campaign, these IDs let you map which accounts are commenting on which posts, whether they are interacting with each other, and whether they are amplifying specific narratives in coordination. You are not guessing. You are pulling hard identifiers.</p><h4>Part 3 (Addendum): Converting LinkedIn Comment and Post IDs to Readable Timestamps</h4><p>You extracted the comment ID. You have the post ID. That tells you who commented where. But there is another piece of intelligence embedded directly inside those numeric IDs that most investigators miss entirely: the timestamp.</p><p>LinkedIn encodes the creation time of posts and comments directly into their numeric IDs using the Unix epoch format in milliseconds. If you know how to extract and convert that number, you know exactly when that content was created, down to the millisecond.</p><h4>Here is how it works.</h4><p><strong>Step 1: Extract the Numeric ID</strong></p><p>You already know how to find the comment ID from the HTML. You will have something like:</p><pre>urn:li:comment:(activity:7123456789,123456789)</pre><p>The second number, <strong>123456789</strong>, is the comment ID. The first number, <strong>7123456789</strong>, is the post ID. Both are numeric. Both encode a timestamp.</p><h4>Step 2: Understand the Encoding</h4><p>LinkedIn uses a format called “snowflake” or a variation of it, similar to how Twitter and Discord generate unique IDs. The ID is a 64-bit integer, and a portion of those bits represents the timestamp in Unix milliseconds.</p><p><strong>The practical takeaway is this</strong>: you can extract the first 41 bits of the ID to get the timestamp. But you do not need to do bitwise math yourself. The simpler method works for most LinkedIn IDs because they are large enough to contain the timestamp in the higher-order bits.</p><h4>Step 3: The Conversion Method</h4><p>Take the numeric ID. Let us use a real-world example from a public LinkedIn comment:</p><pre>Comment ID: 7256123456789012345</pre><p>To extract the timestamp, you need to apply a bit shift operation that LinkedIn uses. The formula is:</p><pre>Timestamp (Unix milliseconds) = ID &gt;&gt; 17</pre><p>Then add the LinkedIn epoch offset. LinkedIn’s epoch starts at a different base than standard Unix epoch. The standard Unix epoch starts at January 1, 1970. LinkedIn’s internal epoch starts at January 1, 2017. This means you need to add the difference.</p><h4>Here is the full formula:</h4><pre>Unix Timestamp (milliseconds) = (ID &gt;&gt; 17) + 1483228800000</pre><p>Where <strong>1483228800000</strong> is the Unix timestamp in milliseconds for January 1, 2017, 00:00:00 UTC.</p><h4>Step 4: Practical Conversion Without Manual Math</h4><p>You do not need to do this by hand. There are tools that automate this.</p><p>One method is to create a Python script to run this for you.</p><h4>Step 5: Manual Conversion Using Online Tools</h4><p>If you do not want to run a script, use a browser-based approach.</p><p>First, go to a website that performs the bit shift calculation. You can use any online tool that supports bitwise operations. Enter the LinkedIn ID, apply <strong>&gt;&gt; 17</strong>, and note the result.</p><p>Then, add <strong>1483228800000</strong> to that result.</p><p>Now take the final number and go to a<strong> Unix timestamp converter</strong> like <strong>epochconverter.com</strong>. Paste the number in milliseconds. The site converts it to a human-readable date and time in UTC.</p><h4>Step 6: Why This Matters</h4><p>This technique gives you the exact creation time of a post or comment, not the relative “<strong>3 days ago</strong>” display that LinkedIn shows. Relative timestamps are vague. “3 days ago” does not tell you if the post was made at <strong>2 PM</strong> or <strong>2 AM</strong>. The Unix timestamp does.</p><h4>In a disinformation investigation, you can now:</h4><ul><li>Establish the exact sequence of posts and comments across multiple accounts.</li><li>Identify coordinated activity by finding comments posted within seconds of each other from different accounts.</li><li>Reconstruct the timeline of a narrative as it was amplified.</li><li>Compare the creation timestamp against other known events to establish context.</li></ul><p>This is not a rough estimate. This is forensic-level precision extracted from an ID that LinkedIn hands you in the page source.</p><h4>Practical Example: Full Walkthrough</h4><p>A target comments on a LinkedIn post. You inspect the element and find:</p><pre>urn:li:comment:(activity:7123456789012345678,7256123456789012345)</pre><p>The comment ID is <strong>7256123456789012345</strong>.</p><p>You run the Python script or do the manual math:</p><pre>ID: 7256123456789012345<br>ID &gt;&gt; 17: 55371093750000 (approximate)<br>Add epoch offset: 55371093750000 + 1483228800000 = 56854322550000</pre><p>Convert <strong>56854322550000</strong> milliseconds to a date. It resolves to:</p><pre>August 15, 2025, 14:32:30 UTC</pre><p>You now know this comment was posted on <strong>August 15, 2025, at 2:32 PM</strong> <strong>UTC</strong>. Not “<strong>several months ago</strong>.” Not “<strong>around mid-August</strong>.” The exact second.</p><p>That is how you turn a numeric ID into a timestamp. Document it. Add it to your timeline. This is the level of precision professionals operate at.</p><h4>Part 4: Activity Feed Analysis</h4><p>The Activity feed on a LinkedIn profile is a behavioral goldmine. Every post, like, comment, and share is logged with a timestamp. This feed is often public even when other parts of the profile are restricted.</p><p>Open the target’s profile and click on “<strong>Activity</strong>” or scroll to the “<strong>Activity</strong>” section. Click “<strong>See all activity.</strong>” You now have a chronological feed of everything this person has done on LinkedIn.</p><p><strong>First, analyze the timestamps</strong>. If someone consistently posts or comments between <strong>11 PM </strong>and <strong>4 AM Eastern Standard Time</strong>, they are either a night owl in <strong>North America </strong>or they are operating from a different timezone entirely. Cross-reference this with their stated location. Discrepancies are intelligence.</p><p><strong>Second, analyze the content</strong>. Look at the technical depth of their comments. Someone who writes “<strong>Great insights</strong>!” on every post is not a practitioner. Someone who writes a <strong>paragraph about the specifics of AWS Lambda</strong> cold starts or the nuances of a particular <strong>NIST framework</strong> is revealing their actual<strong> hands-on knowledge</strong>. This tells you their real skill level.</p><p><strong>Third, map the relationships</strong>. Click on the posts the target comments on. Who wrote the original post? Is it a colleague? A competitor? An industry influencer? Note who responds to the target’s comments. <strong>Note the tone</strong>. <strong>Supportive</strong>? <strong>Combative</strong>? <strong>Familiar</strong>? You are mapping internal team structures and external professional relationships from public interactions alone.</p><h4>Part 5: Internal Team Mapping and Organizational Friction</h4><p>When multiple employees from the same company comment on each other’s posts, you can infer reporting structures and team dynamics. A <strong>manager </strong>who consistently <strong>praises a specific employee’s posts</strong> is signaling <strong>mentorship </strong>or <strong>favoritism</strong>. An employee who never interacts with their supposed team lead is signaling distance or friction.</p><p>Comment chains where two employees from the same company disagree, especially on technical or strategic topics, reveal internal divisions. Note the language. Is the disagreement respectful or dismissive? Is one party pulling rank? These are signals about company culture, internal politics, and potential insider threat vectors.</p><p><strong>This is not gossip</strong>. This is organizational intelligence. If you are investigating a company for fraud, for due diligence, or for insider threat assessment, knowing who is aligned with whom and where the fractures are is actionable intelligence.</p><h4>Part 6: Email and Phone Number Discovery with ContactOut and SignalHire</h4><p>LinkedIn does not want you to have direct contact information without a premium subscription. But the data exists elsewhere. <strong>ContactOut </strong>and <strong>SignalHire </strong>are two tools that aggregate publicly available contact data and link it to LinkedIn profiles.</p><h4>ContactOut</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MMdw-QTK4qU5NdmaTwkd9g.png" /></figure><p>ContactOut is a browser extension that overlays email addresses and phone numbers onto LinkedIn profiles. It works by cross-referencing the profile you are viewing against its database of publicly sourced contact information. When you install the extension and visit a LinkedIn profile, ContactOut displays any email addresses and phone numbers it has associated with that person.</p><p>The data comes from public sources. Corporate websites. Conference attendee lists. Academic publications. Press releases. Patent filings. SEC documents. All of it is open source. ContactOut just aggregates and surfaces it.</p><h4>How To Use ContactOut</h4><p>Install the extension on your investigation browser. Navigate to the target’s LinkedIn profile. Look for the<strong> ContactOut sidebar</strong> or <strong>icon</strong>. If data is available, it will display. Copy it. Verify it. Document where you found it.</p><h4>SignalHire</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhY_86b0P0SEpshcY7PVeA.png" /></figure><p>SignalHire operates similarly but with a stronger focus on internal company data. It aggregates email patterns and phone numbers based on company domain formats. If a company uses the format <strong>firstname.lastname@company.com</strong>, SignalHire can often generate or verify the target&#39;s email address based on that pattern.</p><p>SignalHire also provides a dashboard for managing multiple leads and exporting data. For an investigator building a target list across an organization, this is more efficient than looking up profiles one at a time.</p><p>Both tools have free tiers with limited lookups. Paid tiers unlock more data. For professional investigative work, the paid tier is a necessary operational expense.</p><h4>Important Note on Methodology</h4><p>These tools do not access private data. They do not breach LinkedIn’s security. They aggregate information that is already public, just scattered across the internet. Your job as an investigator is to verify everything they return. If <strong>ContactOut </strong>gives you an <strong>email</strong>, send a test email from a disposable address to see if it bounces. If <strong>SignalHire </strong>gives you a phone number, run it through a <strong>carrier lookup</strong> to confirm it is active and associated with the target’s geography.</p><p>The tool is the starting point, analyst. Verification is the work!</p><h4>Part 7: Practical Methodology Summary</h4><p>Here is your LinkedIn investigation workflow, step by step.</p><ol><li>Google Dork the Organization. Start with <strong>site:linkedin.com/in &quot;company name&quot;</strong> and refine by title, location, and boolean combinations. Collect every relevant profile URL into a spreadsheet.</li><li><strong>Extract the Internal ID</strong>. For each profile, open the page source or Inspect Element and extract the <strong>member </strong>ID. Store it alongside the public URL. This is your permanent identifier.</li><li><strong>Analyze the Activity Feed</strong>. For high-value targets, review their activity chronologically. Note posting times for timezone analysis. Note comment content for technical skill assessment. Note interaction patterns for relationship mapping.</li><li><strong>Map the Organization</strong>. Build a visual org chart based on titles, reporting relationships inferred from interactions, and tenure data from profile start dates.</li><li><strong>Extract Contact Information</strong>. Run ContactOut and SignalHire on key profiles. Verify every email and phone number returned.</li><li><strong>Cross-Reference Skills</strong>. Take the skills listed on the LinkedIn profile and search for matching usernames, forum posts, GitHub repositories, and subreddit activity. This bridges LinkedIn to the wider digital footprint.</li><li><strong>Document Everything</strong>. Every ID, every email, every timestamp, every inferred relationship. If it is not documented, it did not happen.</li></ol><h3>Lecture 4.3: Instagram — The Locational and Relational Graph</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/881/1*XPkrI-z74og8bFFC5BO5Dw.jpeg" /></figure><p>Instagram looks simple. Photos, videos, stories that disappear. Most people scroll through it without thinking. You are not most people. To an investigator, Instagram is a mapping tool. It maps where someone goes, who they know, what they care about, and how they present themselves to different audiences.</p><p>The intelligence is not just in what they post. It is in the connections they do not realize they are exposing. The tagged photos they forgot about. The bio link that bridges to another platform. The profile picture that hashes to the same image on a LinkedIn account under their real name. The location tag on a story that places them in a city they claimed they never visited.</p><p>This lecture is about extracting every drop of that intelligence. I will walk you through each step as if you have never opened Instagram before. Follow this process, and you will never look at an Instagram profile the same way again.</p><h4>Phase 1: Initial Reconnaissance and Documentation</h4><p>Before you do anything else, open the target Instagram profile. Do not scroll yet. Do not click on photos. Just look at what is in front of you and document everything.</p><p><strong>Open a blank document or your investigation notebook. Record the following</strong>:</p><ul><li>Username exactly as displayed.</li><li>Display name (this can be different from the username and changed anytime).</li><li>Profile picture. Screenshot it. Save the image file separately.</li><li>Bio text. Copy it word for word, including emojis and line breaks.</li><li>Any links in the bio. Copy the full URL.</li><li>Number of posts, followers, and following at the time of your visit.</li><li>Whether the account is public or private.</li><li>Any highlights covers visible on the profile.</li></ul><p>This takes sixty seconds. It creates a snapshot of the account at this moment in time. If the target later changes their bio, removes a link, or goes private, you have the original state documented. This is basic, and most people skip it. Do not skip it.</p><h4>Phase 2: Bio Link Extraction and Cross-Platform Bridging</h4><p>The bio link is one of the most valuable pieces of data on an Instagram profile. Instagram only allows one clickable link in the bio. Users get around this by using link aggregation services like <strong>Linktree</strong>, <strong>Beacons</strong>, or Milkshake, or they <strong>link directly to a single external platform</strong>.</p><p><strong>Click the link</strong>. If it goes to a Linktree page, <strong>document every link on that Linktree</strong>. Users often list their <strong>YouTube</strong>, <strong>TikTok</strong>, <strong>OnlyFans</strong>, <strong>personal website</strong>, <strong>Discord server</strong>, and other platforms there. Each of those is a new investigation path.</p><p>If the link goes directly to a YouTube channel, you now have a Google account associated with the Instagram profile. Subscribe to that channel from a sock puppet account. Analyze the video content, the posting frequency, the comments the target leaves on their own videos.</p><p>If the link goes to a <strong>personal website</strong>, run a <strong>WHOIS </strong>lookup on the domain. Check the <strong>Wayback Machine</strong> for <strong>historical versions</strong> of the site. Look for contact pages, about pages, and any embedded email addresses.</p><p>If the link goes to an OnlyFans or similar subscription platform, note the username format. It may match or resemble the Instagram handle, or it may be a completely different alias. Either way, it is another pivot point.</p><p>Document every external platform you discover through the bio link. Each one is a new source of intelligence.</p><h4>Phase 3: Profile Picture Extraction and Perceptual Hash Matching</h4><p>The profile picture is small on Instagram. You cannot right-click and save it at full resolution through normal means. But you need the highest quality version available because you are going to run it through perceptual hash matching against other platforms.</p><h4>Here is how to extract it</h4><p>The profile picture on Instagram is displayed small. You cannot right-click and save it at full resolution through normal browser actions. But you need the highest quality version available because you are going to run it through perceptual hash matching against other platforms. Instagram stores the full-resolution profile picture URL directly in the page source. Your job is to pull it out.</p><h4><strong>Here Are Two Ways To Do It</strong></h4><h4>Method A: Direct Source Search (Faster and More Reliable)</h4><p>Open the target’s Instagram profile in a browser. Right-click anywhere on the page background and select “<strong>Inspect</strong>” or “<strong>Inspect Element</strong>” to open the developer tools panel.</p><p>Once the panel is open, press <strong>Ctrl + F </strong>to open the search bar within the HTML source. Type <strong>profile_pic_url</strong> and hit Enter. Instagram embeds the full-resolution profile picture URL in a JavaScript object within the page source. You will see a line that looks something like this:</p><pre>&quot;profile_pic_url&quot;:&quot;https://instagram.fxxx1-1.fna.fbcdn.net/v/t51.2885-19/123456789_0123456789_987654321_n.jpg&quot;</pre><p>Copy the entire URL inside the quotation marks. Open it in a new browser tab. The image loads at its highest available resolution. Right-click and save it to your investigation folder. Name the file with the target’s username and the date of extraction.</p><p>This method is faster because you go directly to the data you need without manually hunting through HTML elements.</p><h4>Method B: Element Selector (Use When Source Search Fails)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rGUPJSm267tTRImwf8xVqw.png" /></figure><p>If the <strong>profile_pic_url</strong> search does not return results, or if Instagram has restructured how they embed the image, the element selector method works as a fallback.</p><p>With the developer tools panel still open, look at the top left corner of that panel. You will see a small icon that looks like a <strong>dotted square </strong>with a <strong>cursor arrow</strong>. This is the element selector tool. You can also activate it with the keyboard shortcut <strong>Ctrl + Shift + C</strong>. Click that icon once. Your cursor is now in inspection mode.</p><p>Move your cursor over the target’s profile picture and click on it. The developer tools panel jumps to the specific line of HTML code that renders that image. You are looking for an attribute called <strong>src </strong>within an <strong>&lt;img&gt;</strong> tag. It will look something like:</p><pre>&lt;img src=&quot;https://instagram.fxxx1-1.fna.fbcdn.net/v/t51.2885-19/123456789_0123456789_987654321_n.jpg&quot;&gt;</pre><p>Copy the full URL from the <strong>src </strong>attribute. Open it in a new tab. Save the image.</p><h4>What You Do With the Image</h4><p>Once you have the profile picture saved, you generate a perceptual hash. Install the required Python library if you have not already:</p><pre>pip install imagehash pillow</pre><p><strong>Then run this script</strong>:</p><pre>from PIL import Image<br>import imagehash<br><br># Load the saved profile picture<br>img = Image.open(&quot;target_username_profile.jpg&quot;)<br><br># Generate perceptual hash<br>phash = imagehash.phash(img)<br><br>print(f&quot;Perceptual Hash: {phash}&quot;)</pre><p>The output is a <strong>short alphanumeric string</strong>. This hash represents the visual fingerprint of the image. It survives resizing, minor cropping, and slight edits. If the same image appears on Facebook, LinkedIn, Twitter, or any other platform, the hash will match or be extremely close.</p><p>Now take that <strong>hash and compare it against profile pictures extracted from other suspected accounts</strong>. If the<strong> Instagram profile picture hashes </strong>to the<strong> same value </strong>as a<strong> LinkedIn profile picture </strong>under a<strong> real name, y</strong>ou just linked an <strong>anonymous Instagram account </strong>to a<strong> verified professional identity.</strong> That is attribution.</p><h4>Phase 4: Tagged Photos — The Goldmine</h4><p>Most investigators jump straight to the main profile grid. That is a mistake. The tagged photos section is separate from the main posts. It contains photos and videos that other users posted and tagged the target in. The target cannot delete these. They can only untag themselves, and most people forget to do that.</p><p>To access tagged photos on a desktop browser, go to the target’s profile and look at the tabs below the bio. You will see “<strong>Posts</strong>,” “<strong>Reels</strong>,” and a small icon that looks like a person inside a frame. That is the tagged photos tab. Click it.</p><p>On mobile, the tagged tab is located below the bio next to the posts grid, represented by the same person-in-frame icon.</p><h4>Scroll through every tagged photo. For each one, ask yourself:</h4><ul><li>Who posted this? Is the uploader’s profile public?</li><li>Where was this taken? Is there a location tag?</li><li>When was this taken? Is there a timestamp or date reference in the caption or comments?</li><li>What is the target doing? Who else is in the photo?</li><li>Does the background reveal anything about the target’s habits, relationships, or locations?</li></ul><p>I once found a target’s home address through a tagged photo. The target was careful. Their own profile had zero location tags. But a friend posted a group dinner photo, tagged the target, and added a location tag for the restaurant. That restaurant was two blocks from the target’s apartment. The friend’s caption mentioned “<strong>walking back to ****’s place after dinner</strong>.” The target never posted a single thing about that evening. They did not have to. Their friend did the work for me.</p><p>Tagged photos are the backdoor into a target’s real life. Use them.</p><h4>Phase 5: Location Tag Analysis and Pattern-of-Life Mapping</h4><p>Every Instagram post and story can carry a location tag. Even if the target does not manually add one, Instagram suggests locations based on GPS data. Many users accept these suggestions without thinking.</p><p>Go through the target’s posts one by one. For each post, check if there is a location tag below the username at the top of the post. Click that location tag. Instagram opens a page showing all public posts tagged at that location. This gives you two things.</p><p><strong>First</strong>, it confirms the target was at that location at a specific time. The post timestamp tells you when.</p><p><strong>Second</strong>, it shows you who else posts from that location. These are potential associates. People who frequent the same gym, the same coffee shop, the same park. Note their usernames. Check if the target follows them or interacts with their posts.</p><p><strong>Now map the locations</strong>. Take every location tag and plot it on Google Earth or a simple map. Look for clusters. Does the target post frequently from a specific neighborhood? That is likely their home area. Do they post from a specific office building every weekday? That is likely their workplace. Do they post from a specific bar every Friday night? That is a pattern-of-life marker.</p><p><strong>Combine this with the timestamps</strong>. If someone posts from a gym every weekday at 7 AM, you know their morning routine. If they post from an airport every other week, you know they travel frequently. Each location tag is a dot. Connect the dots, and you have a behavioral map.</p><h4>Phase 6: Story Analysis and Temporary Content</h4><p>Instagram Stories disappear after 24 hours. But highlights are saved Stories that the user chose to keep permanently visible on their profile. These are often organized into categories like “Travel,” “Food,” “Work,” or “Friends.”</p><p>Click through every highlight. Treat each highlight as a curated collection the target wants you to see. Look for:</p><ul><li>Locations visible in the background.</li><li>Other people who appear regularly.</li><li>Screenshots of conversations or posts the target found important.</li><li>Events like birthdays, weddings, or work functions.</li></ul><p>If the target has an active Story at the time of your investigation, view it from a sock puppet account that does not follow the target, if the account is public. <strong>If the account is private, you will need a sock puppet that the target has accepted as a follower</strong>. Never view a Story from your real account. <strong>Always use a properly maintained sock puppet</strong>.</p><p>Document the Story content quickly. Screenshot it. Stories vanish, and you may only have one chance.</p><h4>Phase 7: Comment Analysis and Relationship Mapping</h4><p><strong>Comments are conversations</strong>. They reveal who the target interacts with, how they speak to different people, and what topics trigger engagement.</p><p><strong>Go through the target’s posts</strong>. Read the comments. Note every user who comments regularly. These are the target’s inner circle. Note the tone. Is it friendly? Flirtatious? Professional? Argumentative?</p><p><strong>Click on the profiles of frequent commenters</strong>. Are their accounts public? Do they post photos with the target? Do they share the same locations? You are mapping the target’s social graph through their interactions.</p><p><strong>Also, read the comments the target leaves on other people’s posts.</strong> Instagram allows you to see comments someone has made on public posts through third-party tools or manual searching. If the target has a consistent commenting pattern on certain accounts, those accounts are part of their social orbit.</p><h4>Phase 8: Instagram User ID Extraction &amp; Validation</h4><p>Every Instagram account has a permanent numeric User ID. The username can change. The display name can change. The User ID stays the same forever. If you capture this ID once, you can track the account through any rebranding.</p><h4>Method 1: Page Source Extraction</h4><p>Open the target’s Instagram profile. Right-click anywhere on the page background and select “View Page Source.” Press <strong>Ctrl + F</strong> and search for <strong>profilePage_</strong>. You are looking for a string like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okOv_R_0r1ULUVzL0xxpCA.png" /></figure><p>The number after the underscore is the User ID. Copy it. Store it.</p><h4>Method 2: Using the Custom Instagram Parser Tool</h4><p>I built a custom Python tool that automates this entire process. You feed it the Instagram page source code, and it extracts the User ID, profile picture URL, bio, external links, follower counts, business details, and more. It is faster than manual extraction and produces a structured JSON report for your evidence folder.</p><p>The tool is not included with this course, nevertheless:</p><pre>python3 instagram_parser.py</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g25v-avO4-c4VnOb6cQp2w.png" /></figure><p>Enter the path to your saved source code file. The tool outputs a complete intelligence report including the User ID.</p><h4>Why the User ID Matters</h4><p>The User ID is your permanent anchor. If the target changes their username from <strong>@oldhandle</strong> to <strong>@newhandle</strong>, you lose them if you are tracking by username alone. But if you have the numeric ID, you can verify the new handle belongs to the same account. You can also use the ID to pull profile data programmatically, track the account across time, and cross-reference against breach databases that include Instagram numeric IDs.</p><h4>Phase 9: Google Dorking for Instagram — Finding What the Platform Hides</h4><p>Let me be direct. There is no Google dork that bypasses Instagram’s privacy settings. You cannot type a query and magically see a private profile’s posts, messages, or internal account data. Anyone who tells you otherwise is either lying or confused about what a dork actually does.</p><p>What you can do is use Google dorks to find the public footprints that surround an Instagram account. When someone creates an online presence, they leave trails across multiple platforms. A bio link that leads to a personal website. A username that appears in a forum signature. An email address buried in an old blog comment. These are the threads Google can pull, and these threads lead you to intelligence Instagram itself will never show you.</p><h4>The Dork Chain: Finding Public Footprints</h4><p>The methodology is simple. You are not searching Instagram for private data. You are searching the entire indexed web for places where the target’s Instagram identity overlaps with other information.</p><p>Start with the username. If the target is <strong>@vintage_bike_77</strong>, the username itself is your first search term. But do not stop at searching the bare handle. People link their Instagram accounts in bios, forum signatures, blog posts, and comment sections. They write things like &quot;<strong>Follow me on Instagram</strong> <strong>@vintage_bike_77</strong>&quot; or &quot;<strong>DM me on IG</strong>: <strong>vintage_bike_77</strong>.&quot;</p><p><strong>Use These Dorks To Find Those Mentions:</strong></p><pre>&quot;vintage_bike_77&quot; &quot;instagram&quot;<br>&quot;vintage_bike_77&quot; &quot;ig&quot;<br>&quot;vintage_bike_77&quot; &quot;DM me&quot;<br>&quot;vintage_bike_77&quot; &quot;follow me&quot;</pre><p>These queries return pages where the target’s Instagram handle is mentioned alongside those common phrases. You might find a forum profile, a blog comment, a Reddit post, or a YouTube channel description. Each result is a new platform to investigate.</p><p>Now, find public <strong>bios </strong>and <strong>links</strong>. Instagram profiles often include an email address in the bio for business inquiries. Even if the current bio does not show one, an older version might have been indexed by Google before the target removed it.</p><p><strong>Use These Dorks:</strong></p><pre>site:instagram.com &quot;vintage_bike_77&quot; &quot;gmail.com&quot;<br>site:instagram.com &quot;vintage_bike_77&quot; &quot;yahoo.com&quot;<br>site:instagram.com &quot;vintage_bike_77&quot; &quot;protonmail.com&quot;<br>site:instagram.com &quot;vintage_bike_77&quot; &quot;outlook.com&quot;</pre><p>These queries restrict Google’s search to Instagram’s domain and look for the username paired with common email domains. If the target ever included an email in their bio, and Google indexed that version of the page, it will appear in the results.</p><p><strong>Extend This To Other Contact Information:</strong></p><pre>site:instagram.com &quot;vintage_bike_77&quot; &quot;contact&quot;<br>site:instagram.com &quot;vintage_bike_77&quot; &quot;business&quot;<br>site:instagram.com &quot;vintage_bike_77&quot; &quot;WhatsApp&quot;<br>site:instagram.com &quot;vintage_bike_77&quot; &quot;Telegram&quot;</pre><p>Each query looks for a different type of contact detail the target might have publicly listed. Business inquiries. WhatsApp numbers. Telegram handles. Not everyone includes these, but when they do, you have just pulled contact information without ever interacting with the Instagram platform directly.</p><h4>Cross-Platform Username Search</h4><p>Instagram usernames are often reused across other platforms. A target who is <strong>@vintage_bike_77</strong> on Instagram might use the same handle on Twitter, Reddit, GitHub, or niche forums. Google can find these faster than manually checking each platform.</p><p><strong>Use This Dork To Search For The Exact Username Outside Of Instagram:</strong></p><pre>&quot;vintage_bike_77&quot; -site:instagram.com</pre><p>The <strong>-site:instagram.com</strong> operator excludes Instagram results. What remains are pages on other platforms where that exact string appears. It could be a Twitter profile, a Reddit post, a GitHub commit, a forum signature, or a Pinterest board. Every result is a new lead.</p><p><strong>Refine Further By Targeting Specific Platforms</strong>:</p><pre>site:twitter.com &quot;vintage_bike_77&quot;<br>site:reddit.com &quot;vintage_bike_77&quot;<br>site:github.com &quot;vintage_bike_77&quot;<br>site:youtube.com &quot;vintage_bike_77&quot;<br>site:tiktok.com &quot;vintage_bike_77&quot;</pre><p>These queries return results from individual platforms, giving you a cross-platform footprint map built entirely through Google.</p><h4>Finding Indexed Comments and Interactions</h4><p>Instagram comments are not easily searchable through Google, but if a target leaves comments on public blog posts, news articles, or forums using their Instagram handle as their display name, those comments get indexed.</p><p><strong>Use This Dork</strong>:</p><pre>&quot;vintage_bike_77&quot; &quot;comment&quot;<br>&quot;posted by vintage_bike_77&quot;</pre><p>These queries surface comment sections where the target’s handle appears. You might find them debating on a news article, reviewing a product, or posting on a motorcycle forum. Each comment is a window into their interests, writing style, and sometimes their location.</p><h4>Practical Workflow for Instagram Dorking</h4><p>Here is the sequence I run for every new Instagram target:</p><ol><li><strong>&quot;username&quot; &quot;instagram&quot;</strong> — Find all pages mentioning the account.</li><li><strong>site:instagram.com &quot;username&quot; &quot;gmail.com&quot;</strong> — Check for indexed email addresses.</li><li><strong>site:instagram.com &quot;username&quot; &quot;contact&quot;</strong> — Check for other contact details.</li><li><strong>&quot;username&quot; -site:instagram.com</strong> — Find cross-platform appearances.</li><li><strong>site:targetplatform.com &quot;username&quot;</strong> — Drill into specific platforms where the handle appears.</li><li><strong>&quot;username&quot; &quot;comment&quot;</strong> — Surface indexed comments and interactions.</li></ol><p>Document every result. Even a single email address found through these dorks can become the pivot point for an entire email investigation, which you already know how to run from Module 3. The Instagram account is the starting point. Google dorks are how you find everything connected to it.</p><h4>Phase 10: Tools for Instagram Investigation</h4><p>You can do everything manually. But tools speed up the collection process. Here are the ones I use and trust.</p><p><a href="https://imginn.com/"><strong>Imginn.com</strong></a><strong> </strong>is a web-based Instagram viewer. You paste a username, and it displays the profile, posts, stories, and tagged photos without requiring a login. It is useful for quick, passive viewing of public profiles. It also allows you to download images and videos directly.</p><p><a href="https://instasave.io/"><strong>Instasave.io</strong></a> lets you download individual Instagram photos and videos by pasting the post URL. Use this to preserve evidence before a target deletes a post.</p><p><strong>4K Stogram</strong> is a desktop application that downloads entire Instagram profiles, including posts, stories, and highlights. It requires a login, so use a sock puppet account. It is useful for bulk evidence preservation.</p><p><strong>Osintgram</strong> is a Python-based tool that runs in your terminal. It pulls profile data, followers, following lists, and location tags, and outputs structured reports. It requires a valid Instagram session, so again, use a sock puppet.</p><p><strong>ExifTool</strong> should be used on every image you download. Even though Instagram strips most EXIF data on upload, sometimes metadata survives in screenshots or images shared via direct message. Always check.</p><h4>Phase 11: Practical Investigation Workflow Summary</h4><p>Here is the step-by-step process for every Instagram investigation.</p><ol><li>Document the profile. Username, display name, bio, link, follower count, following count. Screenshot everything.</li><li>Extract the profile picture URL from the page source. Save the image. Generate a perceptual hash.</li><li>Extract the numeric User ID from the page source or using the custom Instagram parser tool. Validate it via multiple sources.</li><li>Follow the bio link. Document every external platform it connects to.</li><li>Open the tagged photos tab. Review every photo. Note uploaders, locations, and timestamps.</li><li>Review all highlights. Treat them as permanent curated content.</li><li>Analyze each post for location tags. Plot them on a map.</li><li>Read comments on the target’s posts. Identify frequent interactors.</li><li>Read comments the target leaves on other public posts. Map their social orbit.</li><li>Use tools like Imginn for passive viewing and 4K Stogram for bulk archiving.</li><li>Cross-reference everything with other platforms. The bio link, the profile picture hash, the locations, the writing style.</li></ol><p>If you do all of this, you will know the target better than they know themselves. Not because you hacked anything. Because you paid attention to what they left in the open.</p><h4>Lecture 4.4: Reddit — The Unfiltered Psyche</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*ZOwJKaW_b_aGLyY1uCvAXQ.png" /></figure><p>Reddit is different from every other platform we cover. Facebook is where people present their curated life. LinkedIn is where they wear their professional mask. Instagram is where they perform. Reddit is where the mask comes off.</p><p>On Reddit, people discuss their real problems. Their niche hobbies. Their financial struggles. Their unpopular opinions. They do this under usernames that are often completely disconnected from their real identities. This makes Reddit a psychological goldmine and an attribution challenge rolled into one.</p><p>The intelligence value is not in finding a name. It is in<strong> finding </strong>the <strong>person </strong>behind the<strong> username by mapping their interests, </strong>their<strong> writing patterns, their schedule, </strong>and their<strong> emotional state</strong> across months or years of unfiltered posting.</p><p>This lecture walks you through Reddit investigation from start to finish. Every tool, every technique, every step.</p><h4>Phase 1: Initial Profile Reconnaissance</h4><p>You have a username. Before you dive into archives and deleted content, you need to understand what is visible on the surface right now.</p><p>Open the target’s Reddit profile by navigating to <strong>reddit.com/user/USERNAME</strong>. Document everything you see.</p><h4>Account Creation Date — Getting the Exact Timestamp</h4><p>Reddit displays the account creation date in the sidebar as a relative or formatted date, something like “<strong>Created August 15, 2019</strong>” or “<strong>6 years ago</strong>.” That is useful, but it is not precise. You want the exact timestamp. Reddit stores it in the page source. Here is how to pull it.</p><p>Right-click anywhere on the page background, not on any image or button. Select “<strong>Inspect</strong>” or “<strong>Inspect Element</strong>” from the menu. This opens the browser’s developer tools panel.</p><p>Now, look at the top left corner of that developer tools panel. You will see a small icon that looks like a<strong> dotted square</strong> with a cursor arrow. This is the element selector tool. You can also activate it with the keyboard shortcut <strong>Ctrl + Shift + C</strong>. Click that icon once. Your cursor is now in inspection mode.</p><p>Move your cursor over the account <strong>creation date </strong>displayed in the <strong>sidebar</strong> and <strong>click on it</strong>. The developer tools panel will jump to the specific line of HTML code that renders that text. You are looking for a <strong>time</strong> tag or an attribute called <strong>datetime</strong> within the surrounding markup. It will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ger8eutUMiJV99fLUoOTUQ.png" /></figure><p>The <strong>datetime</strong> attribute contains the exact UTC timestamp (Cake Day) of account creation: <strong>2019-08-15T14:32:30.000Z</strong>. That is the precise second this account came into existence.</p><p>Here is how to decode that specific format, which is known as <strong>ISO 8601</strong> UTC time:</p><ul><li><strong>2005-12-02</strong>: The date (YYYY-MM-DD), which matches December 2, 2005.</li><li><strong>T</strong>: The separator that indicates the Time portion is about to start.</li><li><strong>00:00:00.000</strong>: The exact time (Hours:Minutes:Seconds.Milliseconds). Because it is exactly midnight, it usually means Reddit&#39;s database recorded the date but did not preserve the specific hour/minute of creation for that older account, or it defaulted to midnight.</li><li><strong>Z</strong>: Stands for <strong>Zulu Time</strong>, which means Coordinated Universal Time (UTC).</li></ul><p>Why does this level of precision matter? Because sometimes the exact creation time correlates with other events. An account created three minutes after another account was banned suggests the same operator. An account created during a specific incident window suggests it was purpose-built for that event. “<strong>Six years ago</strong>” does not give you that. <strong>2019-08-15T14:32:30.000Z</strong> does.</p><h4>What the Creation Date Tells You</h4><p>An account created six years ago with consistent activity is an established persona. This is someone’s real online identity. They have invested time in it. They care about it.</p><p>An account created last week with zero karma is a burner. It was made for a specific purpose. Figure out what that purpose was by looking at where they posted.</p><p>An account created years ago but with no activity until recently is a sleeper. Someone created it, sat on it, and activated it later. That is a deliberate operational choice. Ask yourself why.</p><p>Document the exact timestamp. Note what it implies. Add it to your timeline.</p><p><strong>Look at the total karma</strong>. This is the sum of post karma and comment karma. Low karma with high activity suggests the user is controversial or argumentative. High karma with moderate activity suggests the user posts content that resonates with communities.</p><p><strong>Look at the trophy case</strong>. Reddit awards trophies for account milestones, verified email status, and participation in specific events. A verified email trophy confirms the user linked an email address to the account. That does not expose the email to you, but it tells you one exists and is tied to this persona.</p><p><strong>Look at the active communities</strong>. The sidebar shows a list of subreddits the user is active in, sorted by engagement. Document every one. These are interest indicators.</p><p>Now, scroll through the visible posts and comments. <strong>Note the writing style</strong>. Is the user articulate or sloppy? Do they use proper punctuation or type in lowercase fragments? Do they use slang specific to a region? Do they mention their age, gender, location, occupation, or relationship status anywhere? Redditors leak personal details constantly, often buried in unrelated comments.</p><p>Document everything you find in this initial pass. This is your baseline.</p><h4>Phase 2: Profile Analysis Tools</h4><p>Manual scrolling gives you the surface. Profile analysis tools give you the patterns.</p><p><strong>Redective</strong> is your first stop. Go to <strong>redective.com</strong> and enter the target username. Redective pulls the account creation date, total karma breakdown, submission history, comment history, most-used words, and hourly activity distribution. The hourly activity chart is particularly valuable. It shows you when the user is most active, broken down by hour. A user who posts exclusively between <strong>9 AM</strong> and <strong>5 PM</strong> US Eastern time on weekdays has a desk job in that timezone. A user who posts at<strong> 3 AM</strong> consistently might work night shifts or live in a different timezone than they claim.</p><p><strong>Redditmetis </strong>is your second stop. Go to <strong>redditmetis.com</strong> and enter the username. This tool provides sentiment scoring across the user&#39;s comment history, activity heatmaps by day and hour, and a breakdown of which subreddits receive the most engagement. The sentiment analysis tells you whether the user is generally positive, negative, or neutral in their interactions. The heatmap visualizes their posting schedule. A consistent Monday through Friday pattern with evenings and weekends free is the signature of someone posting during work hours.</p><p>Run both tools. Save the results. These are your pattern-of-life baselines.</p><h4>Phase 3: Deep Post and Comment Search</h4><p>Reddit’s native search is limited. It does not let you filter by date, score, or specific keywords within a user’s history. External tools close this gap.</p><p><a href="https://samac.io/"><strong>Samac.io</strong></a><strong> </strong>is a Reddit search engine. You can search by author, subreddit, keyword, score threshold, and date range. Use this to find specific comments the target made months or years ago that might not surface in a manual scroll. If you know the target is interested in motorcycles, search their username plus the keyword &quot;Honda&quot; to find every comment where they discussed that specific topic.</p><p><strong>Reddit Comment Search</strong> at <a href="http://redditcommentsearch.com/"><strong>redditcommentsearch.com</strong></a> focuses specifically on comment history. Enter the target username and a keyword. The tool returns every comment the user has made containing that word, with direct links and timestamps. This is useful for finding every instance where the target mentioned a location, a person, or an event.</p><p><strong>Better Reddit Search</strong> at <a href="http://better.redditsearch.io/"><strong>better.redditsearch.io</strong></a> provides enhanced post search with filters for subreddit, flair, author, and date. Use this to search within specific subreddits for posts by the target that Reddit&#39;s native search would miss.</p><p>The key with these search tools is to be specific. Do not just search a username and scroll. Search the username plus keywords related to your investigation: <strong>Locations</strong>. <strong>Hobbies</strong>. <strong>Political views</strong>. <strong>Employers</strong>. <strong>Products</strong>. Every keyword is a thread to pull.</p><h4>Phase 4: Deleted Content Recovery — The Time Machine</h4><p>This is where Reddit investigation gets powerful. Users delete posts and comments for a reason. They said something they regret. They revealed something they should not have. They got into an argument and tried to erase it. The deletion itself is a signal.</p><p>Reveddit at <a href="http://reveddit.com/"><strong>reveddit.com</strong></a> shows content removed by moderators or Reddit&#39;s automated filters. This is not user-deleted content. This is content that someone else decided should not be visible. To use it, navigate to <strong>reveddit.com/user/USERNAME</strong>. Reveddit displays posts and comments that were removed, color-coded by removal type. Moderator removals appear in blue. Auto-mod removals appear in red. This tells you what the target posted that was deemed unacceptable, which is often exactly what you want to see.</p><p><a href="https://pullpush.io/"><strong>PullPush.io</strong></a> is the heavy hitter. It maintains an archive of Reddit content that was indexed before deletion. When a user deletes a comment, PullPush often still has it. To search, use the API endpoint directly or the web interface. The format for searching comments by author is:</p><pre>https://pullpush.io/search/comments?author=USERNAME</pre><p>Replace <strong>USERNAME </strong>with the <strong>target</strong>. The results include the full comment text, the subreddit, the timestamp, and the post it was attached to, even if the comment is no longer visible on Reddit. This is how you recover what someone tried to hide.</p><p>Arctic Shift (Photon) at <a href="http://arctic-shift.photon-reddit.com/"><strong>arctic-shift.photon-reddit.com</strong></a> is another historical archive. It allows searching by post ID, comment ID, or author. If you have a specific post URL that was deleted, Arctic Shift can often retrieve the original content.</p><p>Reddit Archive at <a href="http://redditarchive.com/"><strong>redditarchive.com</strong></a> provides multi-filter archive access including deleted and banned posts.</p><p>For all deleted content recovery tools, the workflow is the same. Enter the username. Browse the recovered content. Read every deleted post and comment. Document anything that contradicts the target’s current narrative, reveals personal information, or connects to other platforms.</p><h4>Phase 5: Scam and Threat Detection</h4><p>If your investigation involves fraud, scamming, or malicious activity, Reddit has specific tools for checking a user’s reputation.</p><p>Universal Scammer List at <a href="http://universalscammerlist.com/"><strong>universalscammerlist.com</strong></a> is a database of known Reddit scammers. Enter the target username or profile URL. If the user is listed, you will see the subreddit that banned them, the reason for the ban, and any associated alt accounts. This is critical for marketplace investigations or any case involving financial transactions on Reddit.</p><p>Snooper at <a href="http://snooper.reddit.com/"><strong>snooper.reddit.com</strong></a> analyzes comment activity distribution to detect automation. Bots and spam accounts have different posting patterns than humans. Snooper flags accounts that exhibit bot-like behavior, which helps you determine whether you are investigating a real person or an automated persona.</p><p>Always run a scammer check if the target has any involvement in trading, selling, or financial discussions. Even if they are not the primary subject of your investigation, a scammer flag provides context about their credibility and behavior.</p><h4>Phase 6: Subreddit Discovery and Interest Mapping</h4><p>The subreddits a user participates in are the most direct indicators of their interests, and interests are what you cross-reference across platforms.</p><p><strong>Subreddit</strong> at <a href="https://subreddits.org/"><strong>Subreddits.org</strong></a> is a searchable directory of over 3,000 subreddits. If the target mentions an interest but you do not know the relevant subreddit, search here. Find the community. Then search that community for the target’s username or writing patterns.</p><p><strong>Reddit List</strong> at <a href="http://redditlist.com/"><strong>redditlist.com</strong></a> is a curated directory of popular and niche subreddits organized by category. Use this to understand the landscape of communities related to the target&#39;s interests.</p><p>When you have mapped the target’s subreddits, categorize them. Group them by theme. Gaming subreddits. Finance subreddits. Location-specific subreddits. Relationship advice subreddits. Health-related subreddits. Each category tells you something about the person’s life.</p><p>Now cross-reference these categories against other platforms. If the target posts on <strong>r/cybersecurity</strong> and their LinkedIn lists a security role, that is a correlation. If they post on <strong>r/Manchester</strong> and their Instagram location tags are all in Manchester, that is a correlation. If they post on <strong>r/motorcycles</strong> and a forum you found through username search has the same user discussing carburetors, that is a correlation.</p><p>Each overlapping interest is one link in your attribution chain.</p><h4>Phase 7: Timestamp and Timezone Analysis</h4><p>Reddit timestamps are in Coordinated Universal Time. Every post and comment carries an exact UTC timestamp visible by hovering over the relative time display. “<strong>Posted 3 hours ago</strong>” becomes “<strong>2025–08–15 14:32:30 UTC</strong>” when you hover.</p><p>Collect timestamps across the target’s activity. Plot them on a 24-hour clock. Look for the active hours. A user who posts consistently between 8 AM and 4 PM UTC is likely in the UK or Western Europe. A user who posts between 2 PM and 10 PM UTC is likely on the US East Coast. A user who posts between 6 PM and 2 AM UTC is likely on the US West Coast.</p><p>Compare this against any stated location. If a user claims to live in New York but their posting hours align with London, something is inconsistent. Inconsistency is intelligence.</p><h4>Phase 8: Cross-Platform Attribution</h4><p>Reddit attribution is rarely direct. You will not find a Reddit profile that says “My name is John Doe and I work at Acme Corp.” What you will find is a pattern of interests, a writing style, a posting schedule, and occasional personal details that collectively point to one individual.</p><h4>Here is the attribution workflow</h4><ol><li>Map all subreddits the target participates in.</li><li>Extract every personal detail mentioned across all posts and comments. Age, gender, location, occupation, education, relationship status, pets, vehicles, health conditions, everything.</li><li>Identify the target’s writing style. Sentence length, punctuation habits, common phrases, misspellings, slang.</li><li>Determine the target’s active hours from timestamp analysis.</li><li>Take all of this and cross-reference against LinkedIn, Facebook, Instagram, forums, and GitHub.</li><li>Look for a profile that matches in at least three categories: interests, writing style, and schedule.</li><li>When you find a candidate, look for a single piece of hard evidence. A Reddit comment mentioning a specific photo that appears on Instagram. A Reddit post about a work project that matches a LinkedIn job description. A Reddit username that matches a GitHub handle.</li></ol><p>One match is a coincidence. Three matches is a pattern. Five matches is attribution.</p><h4>Phase 9: Google Dorking for Reddit — Finding What Reddit’s Search Misses</h4><p>Reddit has its own search. You already know the tools. Redective, Camas, PullPush. But those tools search Reddit’s internal data. Google searches Reddit from the outside, and it often finds things Reddit’s own engine buries or ignores.</p><p>Google indexes Reddit aggressively. Every public post, every public comment, every user profile page that was visible long enough gets crawled and stored. The advantage Google gives you is that its ranking algorithm surfaces content based on relevance, not just chronology. A Reddit comment from three years ago that Reddit’s search would bury on page fifty might appear on page one of Google because it matches your query exactly.</p><p>The dorking approach for Reddit is straightforward. You are using the <strong>site:</strong> operator to restrict results to Reddit&#39;s domain, then layering keywords and operators to find specific content.</p><p><strong>Finding A User’s Digital Footprint Across Reddit</strong></p><p>Start with the username. If the target is <strong>wrench_rider_77</strong>, the basic dork is:</p><pre>site:reddit.com &quot;wrench_rider_77&quot;</pre><p>his returns every indexed page on Reddit where that exact string appears. That includes their profile page, their posts, their comments, and any post where someone else mentioned their username. This is broader than Reddit’s own user search, which only shows the profile and activity. Google shows you who is talking about them too.</p><p><strong>Now, Exclude Their Own Profile To Find Mentions By Others</strong>:</p><pre>site:reddit.com &quot;wrench_rider_77&quot; -inurl:user -inurl:u</pre><p>The <strong>-inurl:user</strong> and <strong>-inurl:u</strong> operators remove the target&#39;s own profile page and user directory from results. What remains are posts and comments where other users referenced their handle. Someone calling them out in an argument. Someone thanking them for advice. Someone linking to one of their posts. These are relationship indicators.</p><p><strong>Finding Specific Content By A User</strong></p><p>If you want to find posts or comments the target made containing specific keywords, combine the username with a search term:</p><pre>site:reddit.com &quot;wrench_rider_77&quot; &quot;Honda&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;carburetor&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;London&quot;</pre><p>Each query returns Reddit pages where the target’s username and the keyword both appear. This is functionally the same as using Reddit Comment Search, but Google’s index sometimes captures content that specialized tools miss, especially older content that was indexed before deletion.</p><p><strong>Finding Deleted Content Via Google Cache</strong></p><p>This is the most valuable Google dorking technique for Reddit. When a user deletes a post or comment, Reddit removes it from their servers. But if Google crawled that page before the deletion, the cached version still exists.</p><p>If you have a specific Reddit post URL that is now deleted, paste that URL directly into Google. If Google cached it, the search result will show a small green arrow next to the URL. Click that arrow and select “<strong>Cached</strong>.” Google displays the stored version of the page as it appeared on the day it was crawled. The deleted content is visible.</p><p>If You do not have the URL but know the username and a likely keyword, use this dork:</p><pre>site:reddit.com &quot;wrench_rider_77&quot; &quot;keyword&quot;</pre><p>Then, for any result that looks relevant but returns a deleted or removed page on Reddit, click the cached version instead. Google preserves what Reddit discards.</p><p><strong>Finding Subreddit-Specific Intelligence</strong></p><p>If you are interested in what a target posts within a specific subreddit, narrow the dork to that subreddit:</p><pre>site:reddit.com/r/motorcycles &quot;wrench_rider_77&quot;<br>site:reddit.com/r/ukpersonalfinance &quot;wrench_rider_77&quot;</pre><p>This returns the target’s activity within a single community, filtered by Google’s index. Combine this with keywords to find specific discussions:</p><pre>site:reddit.com/r/motorcycles &quot;wrench_rider_77&quot; &quot;carb tuning&quot;</pre><p>This query returns only posts and comments within r/motorcycles where the target discussed carburetor tuning. You are no longer searching broadly. You are drilling into a specific topic within a specific community.</p><p><strong>Finding Email Addresses And Contact Details</strong></p><p>Reddit users rarely post their email addresses publicly, but it happens. Sometimes in classifieds subreddits, buy-sell-trade communities, or when offering services.</p><p><strong>Use These Dorks</strong>:</p><pre>site:reddit.com &quot;wrench_rider_77&quot; &quot;gmail.com&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;yahoo.com&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;protonmail.com&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;email&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;contact&quot;<br>site:reddit.com &quot;wrench_rider_77&quot; &quot;discord&quot;</pre><p>Each query looks for the username paired with a contact detail. Most will return nothing. That is expected. But when one returns a result, you have a direct line of communication or a new platform to investigate. That single hit justifies running all six queries.</p><p><strong>Cross-Referencing Reddit With Other Platforms</strong></p><p>A Reddit username often appears on other platforms. Use Google to find these cross-platform bridges:</p><pre>&quot;wrench_rider_77&quot; -site:reddit.com</pre><p>This excludes Reddit entirely and returns every other website where that exact username appears. Forums. Blogs. Twitter. GitHub. YouTube. Each result is a new platform to add to your investigation.</p><p><strong>Refine By Platform</strong>:</p><pre>site:twitter.com &quot;wrench_rider_77&quot;<br>site:github.com &quot;wrench_rider_77&quot;<br>site:youtube.com &quot;wrench_rider_77&quot;</pre><p>These targeted queries confirm whether the handle exists on specific platforms without manually visiting each one.</p><h4>Practical Workflow For Reddit Dorking</h4><p>Here is the sequence I run for every Reddit investigation:</p><ol><li><strong>site:reddit.com &quot;username&quot;</strong> — Broad search for all indexed mentions.</li><li><strong>site:reddit.com &quot;username&quot; -inurl:user -inurl:u</strong> — Find mentions by other users.</li><li><strong>site:reddit.com &quot;username&quot; &quot;keyword&quot;</strong> — Find specific discussions by topic.</li><li><strong>site:reddit.com/r/subredditname &quot;username&quot;</strong> — Drill into specific communities.</li><li><strong>site:reddit.com &quot;username&quot; &quot;gmail.com&quot;</strong> — Check for exposed contact details.</li><li><strong>&quot;username&quot; -site:reddit.com</strong> — Cross-platform handle discovery.</li><li>For any dead Reddit links found during investigation, check Google Cache for the deleted content.</li></ol><p>Document every result. Reddit content disappears. Users delete posts. Subreddits go private or get banned. Google’s cache and index are your backup. Use them before the trail goes cold.</p><h4>Quick Reference: Reddit Dorking Commands</h4><p><strong>Objective_________________Dork</strong></p><ul><li>All indexed mentions: <strong>site:reddit.com &quot;username&quot;</strong></li><li>Mentions by other users: <strong>site:reddit.com &quot;username&quot; -inurl:user -inurl:u</strong></li><li>User activity by keyword: <strong>site:reddit.com &quot;username&quot; &quot;keyword&quot;</strong></li><li>Activity in a specific subreddit: <strong>site:reddit.com/r/subreddit &quot;username&quot;</strong></li><li>Exposed email addresses: <strong>site:reddit.com &quot;username&quot; &quot;gmail.com&quot;</strong></li><li>Cross-platform handle search: <strong>&quot;username&quot; -site:reddit.com</strong></li><li>Specific platform check: <strong>site:twitter.com &quot;username&quot;</strong></li><li>Deleted content recovery: <strong>Paste dead URL into Google → Click “Cached”</strong></li></ul><h4>Phase 10: Practical Investigation Workflow Summary</h4><p>Here is the step-by-step Reddit investigation process.</p><ol><li>Open <strong>reddit.com/user/USERNAME</strong>. Document account creation date, karma, trophy case, and active subreddits.</li><li>Run the username through <strong>Redective </strong>and <strong>Redditmetis</strong>. Save the activity patterns and sentiment analysis.</li><li>Search the username on <strong>Reveddit </strong>and <strong>PullPush</strong>. Recover every deleted post and comment.</li><li>Use <a href="https://samac.io/"><strong>Samac.io</strong></a><strong> </strong>and Reddit Comment Search with specific keywords to find relevant content.</li><li>Check the <strong>Universal Scammer List</strong> if the investigation involves fraud or marketplace activity.</li><li>Map all <strong>subreddits </strong>to interest categories.</li><li>Analyze posting timestamps for timezone and schedule patterns.</li><li>Cross-reference interests, writing style, schedule, and personal details against other platforms.</li><li>Document every correlation. One is a coincidence. Five is attribution.</li><li>Preserve everything. Screenshots, timestamps, archive links. Reddit content disappears. Your evidence folder should not.</li></ol><p>This is Reddit investigation. Not scrolling. Not guessing. Systematic extraction, recovery, and cross-platform correlation. Master this, and you can build a psychological profile from nothing but a username.</p><h4>Lecture 4.5: X (Formerly Twitter) — The Real-Time Signal</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XGK_P0oAcVbRhFsA_X-niA.jpeg" /></figure><p>X is fast. People react to events within seconds. They argue, they share, they leak information without thinking. For an investigator, X is a live intelligence feed that never stops broadcasting.</p><p>But X is also messy. Accounts appear and disappear. Tweets get deleted. Usernames change. Content scrolls past and vanishes into the noise. Your job is to cut through that noise, extract the hard data, and preserve evidence before it disappears.</p><p>This lecture covers every technique you need, from pulling the hidden numeric ID that never changes, to extracting the exact account creation timestamp, to surgical search queries that find exactly what you are looking for, to recovering tweets someone thought they had erased.</p><p><strong>Part 1: User ID Extraction — The Anchor That Never Changes</strong></p><p>Every X account has two identifiers. The username, which is the <strong>@handle</strong> everyone sees, and the numeric user ID, which is the internal identifier X uses behind the scenes.</p><p>The username can change. Someone can switch from <strong>@Allen123 </strong>to <strong>@Allen3sop1 </strong>overnight. If you are tracking based on the handle alone, you lose them.</p><p>The numeric user ID never changes. It is assigned when the account is created. It stays with that account forever. If you capture the numeric ID once, you can track that account through any number of username changes, deactivations, and reactivations.</p><h4>How To Extract It</h4><h4>Method 1: View Page Source</h4><p>Open any X profile in a browser. Right-click anywhere on the page background and select “<strong>View Page Source</strong>.” This opens a new tab with the raw HTML of the page.</p><p>Press <strong>Ctrl + F</strong> to open the search bar. Type <strong>rest_id</strong> and hit Enter. You are looking for a line that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TgqF7wmephOZ2dGojxOIKA.png" /></figure><p>That number is the numeric user ID. It is globally unique. Copy it. Store it in your investigation file alongside the current<strong> @handle</strong> and the date of extraction.</p><h4>Part 1 (Addendum): Validating the Extracted User ID</h4><p>You pulled a number from the page source. You believe it is the numeric user ID. Before you build your investigation around it, validate it. Never trust a single extraction without confirmation.</p><h4>Method 1: The Custom URL Validation</h4><p>Construct this URL using the ID you extracted:</p><pre>https://x.com/intent/user?user_id=123456789</pre><p>Replace <strong>123456789 </strong>with the numeric ID you found. Paste the full URL into your browser and press Enter.</p><p>If the<strong> ID</strong> is <strong>valid</strong>, X redirects you to the <strong>account’s profile page</strong>. You will see the current <strong>@handle</strong>, display name, bio, and profile picture. The account loads. The ID is confirmed.</p><p>If the ID is invalid, X shows an error page or redirects to the home page. That means the number you extracted is not a real user ID, or the account has been permanently deleted and purged from X’s systems.</p><h4>Method 2: Cross-Check with the Current @Handle</h4><p>If you have both the numeric ID and the current @handle, validate by opening both URLs side by side:</p><pre>https://x.com/intent/user?user_id=123456789<br>https://x.com/@current_handle</pre><p>Both should resolve to the same profile page. If they do, you have double confirmation. The ID is valid, and it maps to the expected account.</p><h4>Method 3: The API Endpoint (If You Have Access)</h4><p>If you have an X developer account and API key, query the API directly:</p><pre>https://api.x.com/2/users/123456789</pre><p>A successful response returns the full user object including the current username, display name, and creation date. An empty response means the ID is invalid or the account is gone.</p><h4>Why Validation Matters</h4><p>A wrong user ID leads you to the wrong person. You might attribute tweets to an innocent account. You might submit a report with incorrect evidence. Validation takes ten seconds and prevents catastrophic errors.</p><h4>Documenting the Validation</h4><p>When you confirm an ID is valid, document:</p><ul><li>The numeric ID.</li><li>The current @handle it resolves to.</li><li>The date you validated it.</li><li>The method used (custom URL, API, cross-check).</li></ul><p>This record goes in your investigation file. If the @handle changes next month, you still have the ID and proof it was correct at the time of your investigation.</p><h4>Part 2: Account Creation Timestamp — The Temporal Anchor</h4><p>Every X account has a creation timestamp. This is just as permanent as the numeric ID, and in some ways, it is more valuable. Knowing exactly when an account was created allows you to cross-reference against other platforms, establish whether an account was purpose-built for a specific event, and build a timeline of the target’s online presence.</p><p>X does not display the full creation date on the profile. You will see something like “<strong>Joined March 2015</strong>” in the bio. That is a rough reference. It is not precise enough for forensic work. You need the exact timestamp, down to the second.</p><h4>How To Extract It</h4><p>Open any X profile in a browser. Right-click anywhere on the page background and select “View Page Source.” This opens the raw HTML.</p><p>Press <strong>Ctrl + F</strong> to open the search bar. Type <strong>created_at </strong>and hit Enter. You are looking for a line that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jobRJB_gtcmkOrcIys1RGw.png" /></figure><p>That long number is the account creation timestamp in <strong>Unix epoch format</strong>, expressed in <strong>milliseconds</strong>. It represents the exact moment the account was registered on X’s servers.</p><h4>Converting Epoch To Human-Readable Date</h4><p>The number you extracted is not directly readable. You need to convert it. Go to a Unix epoch converter tool. I recommend <strong>epochconverter.com</strong>. Paste the number you found into the input field. Make sure the tool is set to interpret the value in milliseconds, not seconds. If the number is 13 digits long, it is milliseconds. If it is 10 digits, it is seconds. X uses milliseconds.</p><p>Click “<strong>Timestamp to Human Date</strong>.” The tool outputs the <strong>exact date</strong> and <strong>time</strong> in <strong>UTC</strong>, your<strong> local time</strong>, and a <strong>relative format</strong> like “<strong>6 years ago</strong>.”</p><h4>Example:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rp2Q6u7vQPCctECaTtsaCQ.png" /></figure><h4>Validating The Result</h4><p>Now, compare what you just extracted against the profile’s displayed “<strong>Joined</strong>” date. The profile might show “<strong>Joined March 2015</strong>.” Your extracted timestamp says <strong>March 12, 2015</strong>. These align. You are on the right track.</p><p>If the profile shows “<strong>Joined March 2015</strong>” and your extracted timestamp converts to <strong>August 2017</strong>, something is off. Either you pulled the wrong data field, or the platform is displaying inaccurate information. Always validate. Trust the source code over the displayed text.</p><h4>Why This Matters</h4><p>The account creation timestamp is a cross-referencing tool. If you find a Facebook account and an X account that you suspect belong to the same person, compare their creation dates. If one was created in <strong>March 2015</strong> and the other in <strong>April 2015</strong>, that proximity is a<strong> correlation point</strong>. Most people create their social media accounts around the same period in their lives. It is not proof on its own, but combined with other evidence, it strengthens your attribution.</p><p>It is also an intent indicator. An account created the day before a major event, used to post about that event, and then abandoned was purpose-built. That tells you the operator planned their activity. An account created years ago with consistent activity is a genuine persona. The timestamp gives you context. Keep digging!</p><h4>Method 2: Online Conversion Tools</h4><p>If you do not want to dig through page source, use a service like <strong>commentpicker.com. </strong>Paste the <strong>@handle </strong>into the search bar. The site returns the numeric ID instantly with additional timestamp. This works for most accounts and is faster than manual extraction when you have multiple targets to process.</p><h4>Method 3: API Access</h4><p>If you have an X developer account and an API key, you can query the API directly. The endpoint <strong>users/by/username/:username</strong> returns the full user object including the <strong>rest_id</strong> . This is the programmatic approach for bulk lookups, but it requires authentication and is not passive.</p><p>For most investigations, Methods 1 and 2 are all you need.</p><h4>Why This Matters</h4><p>I want you to understand the practical application, not just the technique. Let me give you a real scenario.</p><p>You are tracking an account that posts harassment and then changes its handle every few weeks to avoid detection. You extracted the numeric ID on day one. On day thirty, the handle has changed three times, but every time you plug that numeric ID into your tracking tools, it resolves to the same account. The target thinks they are evading you. They are not. You have the anchor.</p><p>Document the numeric ID. It is the single most important piece of metadata you will collect from an X profile.</p><h4>Part 3: Advanced Search Operators — The Surgical Toolkit</h4><p>Most people search X by typing a word into the search bar and scrolling. That is like walking into a library and reading every book to find one sentence. The advanced search operators are your card catalog. They let you specify exactly what you want, from whom, within what timeframe, and with what type of content.</p><p>Here is every operator you need to know, explained with practical examples.</p><p><strong>from: — Tweets From a Specific Account</strong></p><p>This restricts results to a single user.</p><pre>from:Allen123</pre><p>Every tweet in the result set was posted by <strong>@Allen123</strong>. Use this as your base operator, then layer others on top.</p><p><strong>to: — Tweets Directed at a Specific Account</strong></p><p>This finds tweets that were sent as replies to a specific user.</p><pre>to:Allen123</pre><p>Use this to see who is talking to your target, even if the target has not responded.</p><p><strong>since: and until: — Date Range Filtering</strong></p><p>These operators restrict results to a specific date range using the format YYYY-MM-DD.</p><pre>from:Allen123 since:2025-01-01 until:2025-06-01</pre><p>This returns every tweet from<strong> @Allen123 </strong>posted between January 1 and June 1, 2025. You just narrowed down years of potential content to a five-month window. Use this to focus on a specific incident period, a known travel window, or any time-frame relevant to your investigation.</p><p><strong>geocode: — Location-Based Searching</strong></p><p>This searches for tweets posted within a radius of specific coordinates.</p><pre>geocode:51.5074,-0.1278,10km</pre><p>This finds tweets posted within 10 kilometers of central London. The format is latitude, longitude, and radius with the unit (km or mi).</p><p>Combine this with other operators:</p><pre>from:Allen123 geocode:40.7128,-74.0060,5km since:2025-03-01 until:2025-03-15</pre><p>This finds any tweet posted by <strong>@Allen123</strong> within 5 kilometers of New York City during the first two weeks of March 2025. If the target claims they were in another country during that period, and this query returns results, you have a discrepancy.</p><p><strong>filter:media — Tweets Containing Images or Video</strong></p><pre>from:Allen123 filter:media</pre><p>This returns only tweets that include photos or videos. This is how you find geolocatable content without scrolling through text. Every image is a potential location clue.</p><p><strong>filter:links — Tweets Containing URLs</strong></p><pre>from:Allen123 filter:links</pre><p>This returns only tweets that include hyperlinks. Use this to map what articles, videos, or external content the target shares. It tells you what information sources they consume and what narratives they amplify.</p><p>Combining Operators for Surgical Precision</p><p>The real power is in combining these operators into a single query that returns exactly what you need.</p><pre>from:Allen123 to:SomeJournalist since:2025-04-01 until:2025-04-30 filter:media</pre><p>This returns every image <strong>@Allen123 </strong>sent as a reply to <strong>@SomeJournalist</strong> during<strong> April 2025</strong>. You are not scrolling through a timeline. You are pulling a specific slice of data tailored to your investigation question.</p><p><strong>Another example</strong>:</p><pre>from:Allen123 geocode:34.0522,-118.2437,15km since:2025-01-01 filter:links</pre><p>This returns every link <strong>@Allen123</strong> posted while physically in Los Angeles during 2025. If the target claims to have never visited LA, and this query returns geotagged tweets from within the city, you have evidence to the contrary.</p><p>Learn these operators. Practice combining them. The search bar is not for casual browsing. It is a query interface for a massive database. Write your queries with precision, and X will give you exactly what you ask for.</p><h4>Part 4: Reconstructing Deleted Tweets</h4><p>Tweets disappear for many reasons. The user deletes them. The account gets suspended. The content violates platform policy and is removed. But deletion is not erasure. The internet caches things. Your job is to find those caches.</p><h4>Method 1: Google Cache</h4><p>When Google indexes a tweet, it stores a snapshot. If the original tweet is deleted, the cached version may still exist.</p><p>Take the tweet URL. It looks like this:</p><pre>https://x.com/Allen123/status/123456789</pre><p>Now search that exact URL on Google. If Google cached the tweet before deletion, the search result will include a small green arrow next to the URL. Click that arrow. Select “<strong>Cached</strong>.” Google displays the stored version of the page, including the tweet text, timestamp, and sometimes the media preview.</p><h4>Method 2: Wayback Machine</h4><p>The Internet Archive at <strong>archive.org</strong> crawls and stores snapshots of web pages. Paste the tweet URL into the Wayback Machine search bar. If the tweet was archived, you will see a calendar of snapshots. Click any date to view the tweet as it existed at that moment.</p><p>The Wayback Machine does not capture every tweet. Popular accounts and high-engagement tweets are more likely to be archived. But when a snapshot exists, it is gold.</p><h4>Method 3: Third-Party Archives</h4><p>Several services aggregate and store X data at scale.</p><p><strong>tweetdeleter</strong> is primarily a tool for users to manage their own tweet history, but it also surfaces deleted content that was indexed before removal. Search the username or tweet text.</p><p>Academic datasets like <strong>DocNow</strong> and <strong>Social Feed Manager</strong> capture large volumes of X data for research purposes. These are not always user-friendly, but if your investigation involves a high-profile account or a significant event, academic archives may have preserved what the user tried to delete.</p><h4>Method 4: Screenshot Searches</h4><p>If the tweet was controversial enough to get deleted, someone probably screenshotted it before it went down. Search the tweet text in quotes on Google Images. Search the username plus keywords from the tweet. Search the tweet URL on Reddit and other forums where people share and discuss posts.</p><p>The text might be gone from X, but it lives on in screenshots posted to other platforms. Find those screenshots.</p><h4>Practical Workflow for Deleted Content Recovery</h4><ol><li>Start with the tweet URL. Check Google Cache.</li><li>Paste the URL into the Wayback Machine. Check for snapshots.</li><li>Search the tweet text in quotes on Google. Check cached results.</li><li>Search the username and keywords on third-party archives.</li><li>Search for screenshots of the tweet on Google Images and Reddit.</li></ol><p>If the tweet was public for any length of time, one of these methods will surface it. The internet does not forget. It just buries things. Your job is to dig.</p><h4>Part 5: Additional Tools for X Investigation</h4><p>Beyond the built-in search operators, several external tools enhance your collection capabilities.</p><p><strong>Nitter </strong>is a privacy-focused frontend for viewing X content without an account. It allows you to browse profiles, search tweets, and view media without logging in. Multiple Nitter instances exist. If one is down, find another. Use it for passive viewing when you do not want to interact with the platform directly.</p><p><strong>Twint </strong>was a Python-based scraping tool that pulled tweet data without API authentication. It is no longer actively maintained due to X’s API changes, but forks and alternatives exist. If you need bulk historical data, explore <strong>snscrape</strong>, which scrapes social networks including X and outputs structured data.</p><p>Social Bearing at <strong>socialbearing.com</strong> provides tweet analytics, sentiment analysis, and engagement metrics for specific search queries or user timelines. Use it to visualize posting frequency and interaction patterns.</p><p>Tweet Beaver at <strong>tweetbeaver.com</strong> offers several utilities including user ID lookup, follower analysis, and conversation threading. It is useful for quick lookups without touching the X interface.</p><h4>Part 6: Practical Investigation Workflow Summary</h4><p>Here is your step-by-step process for every X investigation.</p><ol><li>Navigate to the target profile. Extract the numeric user ID via page source or<strong> commentpicker.com</strong>. Document it.</li><li>Note the account creation date from the profile. Check the exact timestamp using inspect element if available.</li><li>Run a broad search using <strong>from:USERNAME</strong> to establish a baseline of the target&#39;s posting behavior.</li><li>Narrow the search with <strong>since</strong>: and <strong>until</strong>: operators to focus on the timeframe relevant to your investigation.</li><li>Use <strong>filter:media</strong> to pull all images and videos. Review each for geolocation clues.</li><li>Use <strong>filter:links</strong> to identify what external content the target shares.</li><li>Use <strong>geocode</strong>: combined with date operators to find location-specific activity.</li><li>Use <strong>to</strong>: to map who the target interacts with.</li><li>For any deleted tweets, run the recovery workflow: Google Cache, Wayback Machine, third-party archives, screenshot search.</li><li>Cross-reference findings with other platforms. The numeric ID, the writing style, the locations, the shared links, all of these bridge to Facebook, Instagram, Reddit, and LinkedIn.</li><li>Preserve everything. Screenshots, URLs, timestamps, extracted IDs. X content disappears. Your evidence file should not.</li></ol><p>This is X investigation at the professional level. Not scrolling endlessly. Not guessing. Systematic extraction of hard identifiers, surgical search queries that return exactly what you need, and recovery methods that bring back what someone tried to erase. Master this, and you control the signal.</p><h4>Lecture 4.6: GitHub Recon — The Developer’s Digital Shadow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*lF7RUr_DMfgkNytszmgIrA.jpeg" /></figure><p>GitHub is not social media in the traditional sense. But for an investigator, it is one of the richest intelligence sources available. Developers live on GitHub. They write code, document projects, collaborate with teams, and accidentally expose things they should not. Every repository is a window into how a person or organization operates. Every commit is a timestamped action tied to an email address. Every profile is a potential attribution bridge.</p><p>This lecture is a complete walkthrough of GitHub reconnaissance. By the end, you will know how to find users, map organizations, extract hidden emails, discover leaked credentials, determine exactly when an account was created, and automate large parts of the process. No theory without practice. Every technique comes with the exact command or query you need.</p><p><strong>Part 1: Understanding the GitHub API — Your Primary Data Source</strong></p><p>GitHub provides a rich, public API that returns structured JSON data for users, organizations, repositories, commits, and more. This API is your primary collection tool. You do not need authentication for public data. You just need to know the endpoints.</p><p>The base URL is <strong>https://api.github.com</strong>. Every query you run builds on this.</p><p>The tool you will use most often is <strong>curl</strong>, which fetches data from a URL directly from your terminal, paired with <strong>jq</strong>, which formats the JSON output so you can read it.</p><p>If you do not have <strong>curl </strong>installed, install it. If you do not have <strong>jq </strong>installed, install it. These are non-negotiable tools for GitHub OSINT.</p><pre>sudo apt install curl jq</pre><p>Now you are ready.</p><p><strong>Part 2: User Profile Reconnaissance</strong></p><p>Every GitHub user has a public profile accessible through the API. The endpoint is:</p><pre>https://api.github.com/users/[username]</pre><p>Replace [<strong>username</strong>] with the target&#39;s handle. Let me walk you through a real example. Suppose the target is <strong>techenthusiast167</strong>.</p><p><strong>Open your terminal and run the first or using your browser for the second:</strong></p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167&quot;<br><br>OR<br><br>https://api.github.com/users/techenthusiast167</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ly1BvfbzO8iHiRYOuy2oYA.png" /></figure><p>The <strong>-s</strong> flag keeps the output clean by suppressing progress bars. The command returns a <strong>JSON </strong>object. It is dense. You want to filter it to see only the fields that matter for your investigation.</p><p><strong>Run this instead</strong>:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167&quot; | jq &#39;{username: .login, name: .name, company: .company, location: .location, email: .email, blog: .blog, bio: .bio, public_repos: .public_repos, followers: .followers, following: .following, created_at: .created_at}&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0kS2tXqY_n8iMG6HJEGbw.png" /></figure><p><strong>This returns exactly what you need</strong>:</p><ul><li><strong>Username</strong>: The handle you searched.</li><li><strong>Name</strong>: The real name the user provided.</li><li><strong>Company</strong>: The organization they claim affiliation with.</li><li><strong>Location</strong>: Self-reported location.</li><li><strong>Email</strong>: Publicly listed email, if they added one.</li><li><strong>Blog</strong>: Personal website or social media link.</li><li><strong>Bio</strong>: Free-text description. Often contains contact details, interests, or other handles.</li><li><strong>Public Repos</strong>: Number of public repositories.</li><li><strong>Followers</strong>/<strong>Following</strong>: Network size indicators.</li><li><strong>Created At</strong>: The exact account creation timestamp.</li></ul><p><strong>Document every field</strong>. The email, blog, company, and location are direct attribution data. The bio often contains Twitter handles, personal websites, or other platform usernames.</p><p><strong>Part 3: GitHub User ID Extraction — The Numeric Anchor</strong></p><p>Every GitHub account has two identifiers. The username, which is the handle everyone sees like <strong>techenthusiast167</strong>, and the numeric user ID, which is GitHub&#39;s internal identifier.</p><p>The username can change. GitHub allows users to rename their accounts, and when they do, the old username becomes available for anyone else to claim. If you are tracking a target by username alone, a rename can break your investigation.</p><p>The numeric user ID never changes. It is assigned when the account is created and stays with that account permanently. If you capture the numeric ID, you can track that user through any number of username changes.</p><p><strong>Method 1: API Extraction via Curl</strong></p><p>The GitHub API returns the numeric ID in every user profile response. You have already pulled user data with curl. You just need to look at the <strong>id</strong> field.</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167&quot; | jq &#39;{username: .login, id: .id, created_at: .created_at}&#39;</pre><p><strong>The output looks like this</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ejLqsQLgdrnKZX7qy7XMuQ.png" /></figure><p>That <strong>id</strong> field, <strong>123456789</strong>, is the numeric user ID. It is globally unique. No other account on GitHub has that number. Copy it. Store it in your investigation file alongside the current username and the date of extraction.</p><p><strong>To pull just the ID on its own</strong>:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167&quot; | jq -r &#39;.id&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Y1Bb_YnD8FSOpYv597Y0Q.png" /></figure><p>This returns the raw number with no quotes, ready to use in your next query.</p><p><strong>Method 2: Browser Extraction</strong></p><p>If you prefer not to use the command line, you can get the numeric ID directly from your browser.</p><p><strong>Navigate to the API endpoint directly</strong>:</p><pre>https://api.github.com/users/techenthusiast167</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkQdg-incrW6x8tMnISUug.png" /></figure><p>This returns the full JSON profile in your browser. Press <strong>Ctrl + F</strong> and search for <strong>&quot;id&quot;</strong>. The first result will show the numeric ID. It is right there in plain text, no authentication required.</p><p>Use Firefox or install a JSON Formatter extension for Chrome to make the output collapsible and readable.</p><p><strong>Method 3: Avatar URL Analysis</strong></p><p>GitHub stores user avatars on a CDN, and the avatar URL often contains the numeric user ID. This is useful when you only have the avatar image and need to work backward to find the account.</p><p>Right-click on any GitHub user’s avatar and select “Open image in new tab.” The URL will look something like:</p><pre>https://avatars.githubusercontent.com/u/123456789?v=4</pre><p>The number after <strong>/u/</strong> is the numeric user ID. In this example, <strong>123456789 </strong>is the ID. The <strong>?v=4</strong> parameter is just a version counter and can be ignored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fwIQLXc360LSJRtopX-dUw.png" /></figure><p>If you have a GitHub avatar URL saved from a screenshot, a forum post, or a cached page, you can extract the numeric ID directly from the URL. Then construct the API call to pull the full profile:</p><pre>https://api.github.com/user/123456789</pre><p>This returns the complete user profile for whatever username currently holds that ID. If the user changed their username yesterday, this API call still finds them today.</p><p><strong>Customizing the URL to Return User Data via ID</strong></p><p>Once you have the numeric ID, you can query the GitHub API using that ID instead of the username. The endpoint is</p><pre>https://api.github.com/user/[ID]</pre><p>Replace <strong>[ID]</strong> with the numeric ID you extracted.</p><p><strong>Example</strong>:</p><pre>curl -s &quot;https://api.github.com/user/123456789&quot; | jq &#39;.&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SKjZ0MWrO72JBb4i2POodw.png" /></figure><p><strong>Note</strong>: you can as well do this via your browser without using the curl command:</p><p><strong>Example</strong>:</p><pre>https://api.github.com/user/123456789</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*STHToKtjw0bAQSZhMHrYiw.png" /></figure><p>This returns the full user profile for whatever account currently owns that ID. If the user renamed their account from <strong>oldhandle </strong>to <strong>newhandle</strong>, the API returns <strong>newhandle</strong>. You have tracked them through the name change.</p><p>To combine everything into one clean command that takes a username and returns the numeric ID plus the avatar URL:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167&quot; | jq &#39;{username: .login, id: .id, avatar: .avatar_url}&#39;</pre><p><strong>Output</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hY8wDfK4iyfrUdd0nTcRmg.png" /></figure><p><strong>Why This Matters for an Investigator</strong></p><p>The numeric user ID gives you persistence. Usernames change. People rebrand. They create new personas and abandon old ones. The numeric ID is the anchor that ties it all together.</p><p>Here is a practical scenario. You are investigating a developer who goes by <strong>@hackerx </strong>on GitHub. You extract the numeric ID: <strong>987654321</strong>. Six months later, <strong>@hackerx</strong> no longer exists. The account was renamed to <strong>@securityresearcher</strong>. Your old notes point to a dead profile. But if you stored the numeric ID, you run:</p><pre>curl -s &quot;https://api.github.com/user/987654321&quot; | jq &#39;.login&#39;</pre><p>And GitHub returns s<strong>ecurityresearcher</strong>. You found them.</p><p>The avatar URL is another breadcrumb. If a target uses the same avatar on GitHub, Twitter, and a forum, the numeric ID embedded in the GitHub avatar URL connects the GitHub account to that specific image. When you run perceptual hash matching across platforms, the GitHub avatar URL becomes one more confirmed node in your attribution map.</p><p>The numeric ID also helps with breach correlation. Some data breaches and leaked databases include GitHub numeric IDs alongside email addresses and usernames. Having the ID lets you search those datasets with higher precision than a username alone.</p><p><strong>Practical Workflow for ID Extraction</strong></p><ol><li>Pull the user profile: <strong>curl -s &quot;https://api.github.com/users/username&quot; | jq &#39;.&#39;</strong></li><li>Extract the numeric ID from the <strong>id </strong>field.</li><li>Extract the avatar URL from the <strong>avatar_url</strong> field.</li><li>Store both alongside the current username and the date of extraction.</li><li>Construct the ID-based API URL: <strong>https://api.github.com/user/[ID]</strong> for future lookups.</li><li>If the username ever goes dead, query the ID-based URL to find the new username.</li></ol><p><strong>Part 4: Account Creation Date Detection</strong></p><p>The <strong>created_at</strong> field from the API gives you the exact timestamp the account was registered. This is not an estimate. It is the precise second.</p><p><strong>To pull just the creation date</strong>:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167&quot; | jq -r &#39;.created_at&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X2EacEVsCnL0DPjWth3YVQ.png" /></figure><p>The <strong>Z </strong>at the end means UTC. This timestamp never changes. It is your temporal anchor for cross-referencing against other platforms.</p><p><strong>If you want to calculate how old the account is in days</strong>:</p><pre>creation_date=$(curl -s &quot;https://api.github.com/users/techenthusiast167&quot; | jq -r &#39;.created_at&#39;)<br>account_age=$(( ($(date +%s) - $(date -d &quot;$creation_date&quot; +%s)) / 86400 ))<br>echo &quot;Account age: $account_age days&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n7VAUrIFC6dEyEV5YK7dsA.png" /></figure><p>This tells you exactly how long this persona has existed. A new account with suspicious activity is a red flag. An old account with consistent activity is an established identity.</p><p><strong>Part 5: Repository Enumeration</strong></p><p>Repositories are where the intelligence lives. Every repo tells you what the user builds, what languages they know, and what problems they are working on.</p><p><strong>To list all public repositories for a user</strong>:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167/repos&quot; | jq &#39;.[].full_name&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRw1bG0yjRYhvJuBPLm9sg.png" /></figure><p>This returns the full name of each repository in <strong>owner/repo</strong> format. Pick one and drill deeper.</p><p><strong>To get detailed information about a specific repository</strong>:</p><pre>curl -s &quot;https://api.github.com/repos/techenthusiast167/repo-name&quot; | jq &#39;{description: .description, language: .language, stargazers_count: .stargazers_count, forks_count: .forks_count, open_issues_count: .open_issues_count, created_at: .created_at, updated_at: .updated_at}&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6AdOl8It2bAlla7uS0QSxQ.png" /></figure><p>This tells you what the project does, what language it is written in, how popular it is, and when it was created and last updated. An actively maintained repository indicates ongoing development. A repo created two years ago with no updates is abandoned.</p><p><strong>For broader lookup, simply use</strong>:</p><pre>https://api.github.com/repos/techenthusiast167/repo-name</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghiYh9zVjSTXwXj-oHAfJQ.png" /></figure><p><strong>Part 6: Commit Email Extraction</strong></p><p>This is one of the most valuable techniques in GitHub OSINT, and most investigators overlook it entirely.</p><p>Every time a developer makes a commit, Git records the author’s name and email address in the commit metadata. This is how Git tracks who wrote what. GitHub displays commits on the web interface, but it hides the raw email behind a privacy relay address that looks like <strong>username@users.noreply.github.com</strong>. That relay address is useless for investigation.</p><p>The raw commit data, however, still contains the original email if the developer did not configure Git to use the private relay. Many developers never change their default Git configuration, so their personal email is embedded in every commit they have ever made. Your job is to extract it.</p><p>Here are three methods, ordered from most efficient to most surgical.</p><p><strong>Method 1: Curl Extraction (Primary Method — Bulk Collection)</strong></p><p>This is the most reliable approach. It pulls structured <strong>JSON </strong>directly from the GitHub API, which you can filter and save for your evidence file. It works on every public repository.</p><p><strong>Run this command in your terminal:</strong></p><pre>curl -s &quot;https://api.github.com/repos/[owner]/[repo]/commits&quot; | jq &#39;.[].commit.author.email&#39;</pre><p>Replace [<strong>owner</strong>] with the username or organization name, and [<strong>repo</strong>] with the repository name.</p><p><strong>Example</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yo7VoKEwVgBM39y0ilKlag.png" /></figure><p>The output is a clean list of every email address associated with commits in that repository.</p><p>If the developer used multiple email addresses across different commits, you will see all of them. Each one is a pivot point for further investigation.</p><p><strong>To get more context with each email, pull the author name alongside it:</strong></p><pre>curl -s &quot;https://api.github.com/repos/techenthusiast167/my-project/commits&quot; | jq &#39;.[] | {name: .commit.author.name, email: .commit.author.email, date: .commit.author.date}&#39;</pre><p><strong>This returns</strong>:</p><pre>{<br>  &quot;name&quot;: &quot;John Doe&quot;,<br>  &quot;email&quot;: &quot;johndoe@gmail.com&quot;,<br>  &quot;date&quot;: &quot;2024-08-15T14:32:30Z&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ienQSc5eNvHNFOrgfgWZyA.png" /></figure><p>You now have the <strong>committer’s full name</strong>, their <strong>real email address</strong>, and the exact<strong> timestamp </strong>of each commit. This is attribution gold. Save this output directly into your investigation file.</p><p><strong>Method 2: Browser Shortcut (Quick Look — No Terminal Required)</strong></p><p>If you are not on a machine with curl installed, or you just want a fast glance without opening the command line, use your browser.</p><p><strong>Navigate to</strong>:</p><pre>https://api.github.com/repos/[owner]/[repo]/commits</pre><p>Replace [<strong>owner</strong>] with the username or organization name, and [<strong>repo</strong>] with the repository name.</p><p><strong>Example</strong>:</p><pre>https://api.github.com/repos/techenthusiast167/my-project/commits</pre><p>This opens a raw JSON page containing every commit on the default branch. The page is plain text, but all the data is there.</p><p>Now, press <strong>Ctrl + F</strong> and search for <strong>&quot;email&quot;</strong>. Every match is a commit author&#39;s email address embedded in the JSON. You will see lines like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04C9UV-dOnpHD4DS85WWPQ.png" /></figure><p>Scroll through the results. Each email is tied to a specific commit with a timestamp and a committer name. You can pull every email address ever used in that repository without cloning anything, without running a single command, just by reading the API output in your browser.</p><p>To make this even easier, use Firefox, which natively formats JSON with collapsible trees. If you are on Chrome, install a JSON Formatter extension. With formatted JSON, you can expand each commit object, navigate to <strong>commit </strong>→ <strong>author </strong>→ <strong>email</strong>, and the email is right there.</p><p>This method is fast, passive, and requires zero setup. Bookmark the API URL pattern. It will save you time on every GitHub investigation.</p><p><strong>Method 3: The .patch Method (Deep Dive on a Single Commit)</strong></p><p>If you need to preserve a single commit as evidence, or if the API is not returning the data you expect, the <strong>.patch</strong> method gives you the raw, unprocessed commit output.</p><p>First, get the <strong>SHA hash</strong> of the specific commit you want. Use Method 1 to list all commit SHAs:</p><pre>curl -s &quot;https://api.github.com/repos/techenthusiast167/my-project/commits&quot; | jq &#39;.[].sha&#39;</pre><p>This returns a list of commit hashes. Pick one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWMNsPgJyeCThNrwQ2oAng.png" /></figure><p>Now, append <strong>.patch</strong> to the commit URL and fetch it:</p><pre>curl -s &quot;https://github.com/techenthusiast167/my-project/commit/abc123def456.patch&quot;</pre><p>The output is a raw patch file. At the very top, you will see a line like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uR1N-Om55B0i7xj3qqrA3Q.png" /></figure><p>That is the committer’s real name and email address. Not the GitHub-provided <strong>noreply.github.com</strong> relay. The actual email they configured in Git.</p><p><strong>You can also open this URL directly in your browser. Navigate to</strong>:</p><pre>https://github.com/[owner]/[repo]/commit/[sha].patch</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dR1WVIJ489Qz4iivUZQkbQ.png" /></figure><p>The browser displays the raw patch as plain text. Press <strong>Ctrl + F</strong> and search for <strong>From</strong>:. The email is right there. Screenshot it. Save the page as evidence.</p><p><strong>What You Do With The Email</strong></p><p>Every <strong>email </strong>address you extract becomes a <strong>new investigation thread</strong>. Plug it into your email intelligence workflow from Module 3. Run it through Google dorks, Epieos, Intelbase, BehindTheEmail, etc. Search it across social media platforms. Check it against breach databases like HaveIBeenPwned, DeHashed, and IntelX.</p><p>A <strong>single commit email</strong> can unravel an <strong>entire digital footprint</strong>. I have found personal Facebook accounts, LinkedIn profiles, and personal websites starting from nothing but a GitHub commit email. The developer never thought anyone would look. That is exactly why you do.</p><p><strong>Part 7: Followers, Following, and Social Network Mapping</strong></p><p>GitHub profiles include follower and following lists. These reveal professional relationships, team structures, and collaboration networks.</p><p><strong>To see who a user follows</strong>:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167/following&quot; | jq &#39;.[].login&#39;<br><br>OR<br><br>curl -s &quot;https://api.github.com/users/techenthusiast167/following?per_page=100&quot; | jq &#39;.[].login&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eu8drLzDzi7ANH9YpgMagQ.png" /></figure><p><strong>To see who follows them</strong>:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167/followers&quot; | jq &#39;.[].login&#39;<br><br>OR<br><br>curl -s &quot;https://api.github.com/users/techenthusiast167/followers?per_page=100&quot; | jq &#39;.[].login&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aXXTtkwzIhTXzfp93ofxJg.png" /></figure><p>The <strong>?per_page=100</strong> parameter ensures you get up to 100 results per request instead of the default 30. If the user follows more than 100 accounts, you need to handle pagination. The API includes a <strong>Link </strong>header in the response with the URL for the next page. You can check it with:</p><pre>curl -s -I &quot;https://api.github.com/users/user/following?per_page=100&quot;</pre><p>Look for the <strong>Link </strong>header in the output. It contains the URL for the next page of results.</p><p><strong>If You Still Get an Empty Response</strong></p><p>Some users have zero followers or follow zero accounts. If the command returns nothing, that means exactly that. The user is not following anyone, or no one follows them.</p><p><strong>Map these connections</strong>. If a target follows several employees of the same company, they likely work there or have a professional relationship with them. If multiple accounts follow each other in a small cluster, you have identified a team or a collaboration group.</p><p><strong>Part 8: Organization Intelligence</strong></p><p>Organizations on GitHub have their own profile pages and member lists. If your target lists a company on their profile, check if that company has a GitHub organization.</p><p><strong>To pull organization profile data</strong>:</p><pre>curl -s &quot;https://api.github.com/orgs/companyname&quot; | jq &#39;{name: .name, description: .description, blog: .blog, email: .email, location: .location, public_repos: .public_repos}&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3e7zkSpxUDbRZqSNQOKyrw.png" /></figure><p><strong>To list all public members of an organization</strong>:</p><pre>curl -s &quot;https://api.github.com/orgs/companyname/members&quot; | jq &#39;.[].login&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MdER6tWOootathXL0cDPBw.png" /></figure><p><strong>Validation of results</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i9zYrC2sV8gw9F5u8cSRpQ.png" /></figure><p>This returns every GitHub user who publicly lists themselves as a member of that organization. You now have a list of potential employees. Cross-reference these handles against LinkedIn, Twitter, and other platforms to build a corporate directory from the outside.</p><p><strong>Rate Limiting</strong></p><p>GitHub allows 60 unauthenticated requests per hour. If you exceed that, the API returns a 403 error with a message about rate limiting. Check your current rate limit status:</p><pre>curl -s &quot;https://api.github.com/rate_limit&quot; | jq &#39;.rate&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bTBLDBK4go8XdP_9rp4DUg.png" /></figure><p>This shows your remaining requests and when the limit resets. If you are hitting the limit, wait, or use a personal access token to increase your quota to 5,000 requests per hour.</p><p><strong>Part 9: Advanced Curl: All-in-One Intelligence Extraction</strong></p><p>You can pull a target’s entire GitHub footprint with a single command. This returns profile details, organizations, repositories, and commit emails all at once.</p><p>Replace <strong>username </strong>with the target GitHub handle and run:</p><pre>echo &quot;=== PROFILE ===&quot; &amp;&amp; curl -s &quot;https://api.github.com/users/username&quot; | jq &#39;{username: .login, name: .name, company: .company, location: .location, email: .email, blog: .blog, bio: .bio, twitter: .twitter_username, hireable: .hireable, public_repos: .public_repos, followers: .followers, following: .following, created_at: .created_at}&#39; &amp;&amp; echo &quot;=== ORGANIZATIONS ===&quot; &amp;&amp; curl -s &quot;https://api.github.com/users/username/orgs&quot; | jq &#39;.[] | {org: .login, description: .description}&#39; &amp;&amp; echo &quot;=== REPOSITORIES ===&quot; &amp;&amp; curl -s &quot;https://api.github.com/users/username/repos?per_page=100&amp;sort=pushed&quot; | jq &#39;.[] | {repo: .full_name, language: .language, pushed_at: .pushed_at, description: .description}&#39; &amp;&amp; echo &quot;=== COMMIT EMAILS (Latest Repo) ===&quot; &amp;&amp; repo=$(curl -s &quot;https://api.github.com/users/username/repos?per_page=1&amp;sort=pushed&quot; | jq -r &#39;.[0].full_name&#39;) &amp;&amp; curl -s &quot;https://api.github.com/repos/$repo/commits?per_page=10&quot; | jq &#39;.[] | {author: .commit.author.name, email: .commit.author.email, date: .commit.author.date}&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sFSKsiDwhVOiKL0wvuyMNg.png" /></figure><p><strong>What This Returns in One Run</strong>:</p><ul><li>Full profile: username, real name, company, location, email, blog, bio, Twitter handle, hireable status</li><li>Account creation timestamp and last update timestamp</li><li>All public organizations the user belongs to</li><li>All public repositories with language and last push date</li><li>Commit author names and real email addresses from the most recently pushed repository</li></ul><p>Save this as a bash script. Run it on any username. The intelligence lands in your terminal in seconds. No clicking. No manual lookups. One command. Everything.</p><p><strong>Part 10: Advanced Code Search</strong></p><p>GitHub’s search is powerful, but you need to know the operators.</p><p>Go to <a href="https://github.com/search"><strong>https://github.com/search</strong></a> and type your query directly into the search bar. Use the operators you already know:</p><p><strong>Search by User or Organization</strong>:</p><pre>user:johndoe &quot;keyword&quot;<br>org:companyname &quot;keyword&quot;<br>repo:owner/repo &quot;keyword&quot;</pre><p><strong>Example</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndZsQLcN1L3GcAjCV01blA.png" /></figure><p><strong>Search by File Extension</strong>:</p><pre>extension:env &quot;DATABASE_URL&quot;<br>extension:json &quot;password&quot;<br>extension:yml &quot;secret&quot;<br>extension:pem &quot;PRIVATE KEY&quot;</pre><p><strong>Search by Filename</strong>:</p><pre>filename:.env<br>filename:config.json<br>filename:docker-compose.yml</pre><p><strong>Search by Path</strong>:</p><pre>path:.github/workflows<br>path:src/config<br>path:database</pre><p><strong>Search for Credentials and Secrets</strong>:</p><pre>&quot;api_key&quot; org:companyname<br>&quot;password&quot; user:techenthusiast167<br>&quot;AWS_ACCESS_KEY&quot; extension:env<br>&quot;ghp_&quot; org:companyname<br>&quot;xoxb-&quot; org:companyname</pre><p>These queries find API keys, tokens, passwords, and configuration files that developers accidentally committed to public repositories. The <strong>ghp_</strong> prefix is for GitHub personal access tokens. The <strong>xoxb-</strong> prefix is for Slack bot tokens. Finding either in a public repo is a critical security exposure.</p><p><strong>Combine operators for precision</strong>:</p><pre>org:companyname extension:env &quot;DATABASE_URL&quot;</pre><p>This finds every <strong>.env</strong> file in every repository belonging to the target organization that contains a database connection string. One query, and you have the keys to their database.</p><p><strong>Part 11: Automated Reconnaissance Tools</strong></p><p>Manual searching works, but automated tools scale your collection.</p><p>TruffleHog scans repositories for high-entropy strings, which are often API keys and passwords.</p><pre>trufflehog git https://github.com/user/repo --json --verify &gt; scan_results.json</pre><p>The <strong>--verify</strong> flag tests each found credential to confirm it is still active. Use this only on repositories you are authorized to investigate.</p><p><strong>Gitleaks uses pattern-based detection to find secrets</strong>.</p><pre>gitleaks detect --source=/path/to/repo -v</pre><p><strong>GitRob automates organization-wide scanning.</strong></p><pre>gitrob target-organization</pre><p>These tools find what manual searching misses, but they are not a replacement for understanding the search operators. Run the tools, then verify their findings manually. Automated scanners produce false positives. Your brain is the final filter.</p><p><strong>Part 12: Gists Investigation</strong></p><p>Gists are code snippets that users share publicly. They are separate from repositories and are often overlooked during investigations.</p><p><strong>To list all public gists for a user</strong>:</p><pre>curl -s &quot;https://api.github.com/users/johndoe/gists&quot; | jq &#39;.[].html_url&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CVkOOudRa6osPe0V9a9fVA.png" /></figure><p>Gists often contain configuration snippets, notes, API examples, and sometimes credentials. A developer who is careful with their repositories might be careless with their gists. Check them.</p><p><strong>Part 13: Activity Timeline and Pattern-of-Life Analysis</strong></p><p>The events endpoint shows a user’s recent public activity:</p><pre>curl -s &quot;https://api.github.com/users/techenthusiast167/events&quot; | jq &#39;.[].type&#39;<br><br>OR<br><br>https://api.github.com/users/techenthusiast167/events</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b05O1LPevKUJp5m1iy9P8Q.png" /></figure><p>This returns event types like <strong>PushEvent</strong>, <strong>CreateEvent</strong>, <strong>WatchEvent</strong>, and <strong>ForkEvent</strong>, each with a timestamp. Analyze this timeline to understand when the user is active.</p><p>A user who pushes code every weekday between 9 AM and 5 PM UTC has a consistent work schedule in that timezone. A user who commits at 3 AM on weekends has different patterns. This is pattern-of-life intelligence.</p><p><strong>Part 14: Practical Investigation Workflow Summary</strong></p><p>Here is the complete GitHub investigation sequence:</p><ol><li><strong>Profile Pull</strong>: curl -s &quot;https://api.github.com/users/username&quot; | jq &#39;.&#39; — Document name, ID, company, location, email, blog, bio, and creation date.</li><li><strong>Repository Enumeration</strong>: curl -s &quot;https://api.github.com/users/username/repos&quot; | jq &#39;.[].full_name&#39; — List all public repos.</li><li><strong>Repository Analysis</strong>: For each repo, pull description, language, stars, forks, and update history.</li><li><strong>Commit Email Extraction</strong>: For key repos, pull commits and append .patch to commit URLs to extract real email addresses.</li><li><strong>Social Network Mapping</strong>: Pull followers and following lists. Map professional connections.</li><li><strong>Organization Investigation</strong>: If the user lists a company, pull the org profile and member list.</li><li><strong>Code Search</strong>: Run targeted queries for file types, credentials, and sensitive configurations.</li><li><strong>Gists Check</strong>: List and review public gists.</li><li><strong>Activity Analysis</strong>: Pull events to establish active hours and pattern-of-life.</li><li><strong>Automated Scanning</strong>: Run TruffleHog or Gitleaks on high-value repositories for automated secret detection.</li><li><strong>Cross-Platform Correlation</strong>: Take the email, location, company, and social links found on GitHub and cross-reference them against LinkedIn, Twitter, Reddit, and Instagram.</li><li><strong>Document Everything</strong>: Save all API responses as JSON files with timestamps. Screenshot key findings. Build your evidence package.</li></ol><p><strong>Part 15: Quick Reference Commands</strong></p><p>Objective___________________Command</p><ul><li><strong>User profile</strong>:curl -s &quot;https://api.github.com/users/username&quot; | jq &#39;.&#39;</li><li><strong>Creation date only</strong>:curl -s &quot;https://api.github.com/users/username&quot; | jq -r &#39;.created_at&#39;</li><li><strong>List repos:</strong>curl -s &quot;https://api.github.com/users/username/repos&quot; | jq &#39;.[].full_name&#39;</li><li><strong>Repo details</strong>:curl -s &quot;https://api.github.com/repos/owner/repo&quot; | jq &#39;.&#39;</li><li><strong>Extract commit emails Append </strong>:.patch to commit URL</li><li><strong>Followers</strong>:curl -s &quot;https://api.github.com/users/username/followers&quot; | jq &#39;.[].login&#39;</li><li><strong>Following</strong>:curl -s &quot;https://api.github.com/users/username/following&quot; | jq &#39;.[].login&#39;</li><li><strong>Organization profile</strong>:curl -s &quot;https://api.github.com/orgs/orgname&quot; | jq &#39;.&#39;</li><li><strong>Org members</strong>:curl -s &quot;https://api.github.com/orgs/orgname/members&quot; | jq &#39;.[].login&#39;</li><li><strong>List gists</strong>:curl -s &quot;https://api.github.com/users/username/gists&quot; | jq &#39;.[].html_url&#39;</li><li><strong>User events</strong>:curl -s &quot;https://api.github.com/users/username/events&quot; | jq &#39;.[].type&#39;</li><li><strong>Gitleaks scan</strong>:gitleaks detect --source=/path/to/repo -v</li></ul><p><strong>Part 16: Legal and Ethical Boundaries</strong></p><p>Everything covered in this lecture uses publicly available data. The GitHub API returns information that users and organizations chose to make public. You are not bypassing authentication. You are not exploiting vulnerabilities.</p><p><strong>That said, there are lines you do not cross.</strong></p><ul><li><strong>Respect rate limits: </strong>GitHub allows 60 unauthenticated requests per hour. Use authenticated requests with a personal access token for 5,000 requests per hour if you have a legitimate developer account.</li><li><strong>Do not use found credentials</strong>: If you discover an API key or password, document it and report it through responsible disclosure. Using it is illegal.</li><li><strong>Do not harass or dox individuals based on GitHub data</strong>: The fact that someone’s email is public in a commit does not give you the right to target them.</li><li><strong>Store collected data securely</strong>: GitHub profiles change. Save what you need, but protect it.</li></ul><p>Professional investigators operate within the law. Your reputation depends on it.</p><p>This is GitHub reconnaissance at the professional level. Not browsing. Not guessing. Systematic API-driven collection, targeted code search, and automated scanning where appropriate. Master this, and you add a powerful new dimension to every investigation you run.</p><p><strong>Lecture 4.7: YouTube OSINT — The Video Investigator’s Toolkit</strong></p><p>YouTube is the second largest search engine on the planet. People upload their lives, their opinions, their locations, and their skills to this platform every second of every day. For an investigator, YouTube is not just a video library. It is a behavioral archive, a geolocation goldmine, and an attribution tool all rolled into one.</p><p>Most people watch videos. You are going to dissect them. This lecture covers every practical technique you need to extract intelligence from YouTube channels, videos, and the metadata that surrounds them.</p><p><strong>Lecture 4.7: YouTube OSINT — The Video Investigator’s Toolkit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fs8CPsdbwESMSrQU8n1O-g.png" /></figure><p>YouTube<strong> </strong>is the second largest search engine on the planet. People upload their lives, their opinions, their locations, and their skills to this platform every second of every day. For an investigator, YouTube is not just a video library. It is a behavioral archive, a geolocation goldmine, and an attribution tool all rolled into one.</p><p>Most people watch videos. You are going to dissect them. This lecture covers every practical technique you need to extract intelligence from YouTube channels, videos, and the metadata that surrounds them.</p><p><strong>Part 1: Channel Reconnaissance — The Initial Pass</strong></p><p>Every YouTube channel has a public face. Before you touch any tool, open the channel page and document what is visible.</p><p>Look at the channel name. This may be a real name, a pseudonym, or a brand. Note it exactly as displayed.</p><p>Look at the handle. YouTube assigns every channel a unique @handle like <strong>@JohnDoe</strong>. This handle is often reused across platforms. Document it.</p><p>Look at the channel description. Users frequently list <strong>contact emails</strong>, <strong>social media links</strong>, <strong>website URLs</strong>, and business inquiries here. Copy every link and email address. These are direct attribution bridges.</p><p>Look at the channel creation date. This is displayed under the “<strong>About</strong>” tab. An older channel with consistent uploads is an established identity. A new channel with a handful of videos is a burner or a fresh persona. Note it.</p><p>Look at the total video count, subscriber count, and view count. These numbers tell you the channel’s reach and activity level. A channel with thousands of subscribers and regular uploads is a significant online presence. A channel with three videos and ten subscribers is not.</p><p>Scroll through the video list. Note the upload frequency. Note the content themes. Note the locations visible in thumbnails. Thumbnails are often pulled directly from the video and can contain geolocatable imagery before you even click play.</p><p><strong>Part 2: User ID Extraction — The Unchangeable Identifier</strong></p><p>Every YouTube channel has a unique, unchangeable numeric <strong>Channel ID</strong>. The <strong>@handle</strong> can change. The channel name can change. The Channel ID stays the same forever. Extract it.</p><p><strong>Method 1: Page Source (Manual Extraction)</strong></p><p>Open any YouTube channel page. Right-click anywhere on the page background and select <strong>“View Page Source</strong>.” Press <strong>Ctrl + F</strong> and search for <strong>channel_id</strong> or <strong>externalId</strong>. You are looking for a line like:</p><pre>&quot;channel_id&quot;:&quot;UCxxxxxxxxxxxxxxxx&quot;</pre><p><strong>OR</strong>:</p><pre>&quot;externalId&quot;:&quot;UCxxxxxxxxxxxxxxxx&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nR_uXJsYCcS-i_XethbUEA.png" /></figure><p>The value starting with <strong>UC </strong>is the Channel ID. It is globally unique. Copy it. Store it. This ID lets you track the channel through any rebranding.</p><p><strong>Method 2: Browser URL Trick</strong></p><p>If the channel has a custom URL like <strong>youtube.com/@JohnDoe</strong>, the Channel ID is hidden behind the handle. To reveal it, click on any video on the channel. Scroll down to the comments section. Right-click on the channel name in a comment left by the channel owner and select &quot;<strong>Inspect Element</strong>.&quot; Look for an attribute like <strong>data-channelid</strong> or a link containing <strong>/channel/UCxxxxxxxxxxxxxxxx</strong>. That is the ID.</p><p><strong>Method 3: The Share Channel Option (Fastest Method — No Tools Required)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m93UJiCE8zzQ_-e4-kH1jA.png" /></figure><p>If you want the Channel ID without touching the page source, without opening developer tools, and without making a single API call, this is the method you use. It takes less than five seconds and works on every YouTube channel.</p><p>Open the target YouTube channel. Look at the channel banner area. On the right side, you will see a button labeled “<strong>More info</strong>” or a small arrow pointing downward next to the channel name. Click it.</p><p>A dropdown menu appears with several options. Scroll down until you see “Share channel.” It has a curved arrow icon pointing to the right. Click on it.</p><p><strong>A small popup window appears with two options</strong>:</p><ul><li><strong>Share channel</strong> — This copies a link to the channel.</li><li><strong>Copy channel ID</strong> — This copies the Channel ID directly to your clipboard.</li></ul><p>Click “<strong>Copy channel ID</strong>.” A small confirmation message appears at the bottom of the screen: “<strong>Channel ID copied to clipboard</strong>.”</p><p>That is it. You now have the target’s unchangeable Channel ID. Open a notepad, paste it, and store it in your investigation file.</p><p><strong>Method 4: Using the API</strong></p><p>YouTube’s Data API returns the Channel ID directly. The endpoint is:</p><pre>https://www.googleapis.com/youtube/v3/channels?part=id&amp;forUsername=USERNAME&amp;key=YOUR_API_KEY</pre><p>You need an API key from Google Cloud Console, but the free tier allows thousands of queries per day. This method is fast and reliable for bulk lookups.</p><p><strong>Part 2 (Addendum): Validating the YouTube Channel ID</strong></p><p>You pulled a string from the page source that looks like a Channel ID. It starts with <strong>UC </strong>followed by a string of characters. But how do you know it is real? You validate it. Never trust a single extraction without confirmation.</p><p>YouTube Channel IDs follow a predictable URL structure. Every valid Channel ID resolves to a working channel page. Here is how to test it.</p><p>Take the Channel ID you extracted. Let us say it is <strong>UCxxxxxxxxxxxxxxxx</strong>. Construct this URL:</p><pre>https://www.youtube.com/channel/UCxxxxxxxxxxxxxxxx</pre><p>Paste it into your browser. If the ID is valid, the page loads and displays the channel. You will see the channel name, the banner, the video grid, everything. The ID is confirmed.</p><p>If the ID is invalid, YouTube returns a 404 page with the message “This page isn’t available.” That means the string you extracted is not a real Channel ID, or the channel has been terminated. Either way, document it. A terminated channel is still intelligence. It tells you the account existed and was removed.</p><p><strong>Part 3: Channel Metadata Deep Dive</strong></p><p>YouTube stores extensive metadata about every channel. Most of it is visible on the About tab, but some of it is buried in the page source or accessible through third-party tools that aggregate the data for you.</p><p><strong>The About Tab — Manual Collection</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UrRCiDJ8W0vo_1FW4T67BQ.png" /></figure><p>Click the “<strong>About</strong>” tab on any channel. Document the following:</p><ul><li><strong>Description</strong>: Copy the full text. Look for emails, URLs, other social media handles.</li><li><strong>Details</strong>: This section sometimes includes a business inquiry email and a location. Copy both.</li><li><strong>Links</strong>: Custom links to websites, social media, and merchandise stores. Click every one.</li><li><strong>Join Date</strong>: The exact month and year the channel was created.</li><li><strong>Total Views</strong>: Lifetime view count for the entire channel.</li><li><strong>Featured Channels</strong>: Other channels the user endorses or is connected to.</li></ul><p><strong>Page Source Metadata Extraction</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjCDsGWSK7RN0dSjoDOVow.png" /></figure><p>Right-click on the channel page background. Select “<strong>View Page Source</strong>.” Search for these keywords to find hidden data:</p><ul><li><strong>keywords </strong>— YouTube stores channel-level keywords in the metadata. These reveal what topics the channel owner thinks their content is about.</li><li><strong>description</strong> — The full description text, sometimes including older versions that were edited out of the current About tab.</li><li><strong>og:title</strong> and <strong>og:description</strong> — Open Graph meta tags used for social sharing. These often contain clean, structured text.</li><li><strong>canonical</strong> — The canonical URL of the channel, which includes the Channel ID.</li><li><strong>image_src </strong>— The channel’s high-resolution profile image URL</li></ul><p>Document everything you find.</p><p><strong>Part 4: Video Metadata Analysis</strong></p><p>Every video on YouTube carries its own metadata. This includes the upload timestamp, the title, the description, the tags, the category, and sometimes the location where the video was recorded.</p><p><strong>Method 1: The Video Page Source</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iAK5sTPJuHIhPq7WrO48kg.png" /></figure><p>Open any video. Right-click on the page background and select “<strong>View Page Source</strong>.” Search for these fields:</p><ul><li><strong>publishDate</strong> or <strong>datePublished </strong>— The exact upload timestamp in ISO format.</li><li><strong>keywords </strong>— The tags the uploader assigned to the video. These reveal the topics and communities the content targets.</li><li><strong>description </strong>— The full video description, including links and text that may have been edited after upload.</li><li><strong>location </strong>— Rare, but some videos contain geolocation data embedded in the metadata if the uploader enabled it.</li></ul><p><strong>Method 2: The YouTube Metadata Tool</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gWgr2aZ4ssmUA249_ABQvQ.png" /></figure><p>A faster, cleaner way to pull all this data is to use the free web tool at: <a href="https://mattw.io/youtube-metadata/"><strong>https://mattw.io/youtube-metadata</strong></a></p><p>Paste any YouTube video URL into the search bar and click Submit. The tool returns a structured page with:</p><ul><li>Video title, description, and tags.</li><li>Exact upload timestamp.</li><li>Channel ID and channel title.</li><li>Video duration, category, and privacy status.</li><li>Thumbnail URLs at multiple resolutions.</li><li>Whether the video is unlisted, private, or public.</li><li>Caption availability and language.</li></ul><p>This tool aggregates data from YouTube’s public APIs and page source into one readable screen. It saves you from manually digging through HTML. Use it for every video you investigate.</p><p><strong>Part 5: Video and Image Download via Source Code, Inspect Element, Browser Extensions</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u4BO33VFkhXLdM94fez9SQ.png" /></figure><p>You may need to preserve a video or thumbnail as evidence. Downloading is straightforward, but there are multiple methods depending on what you need.</p><p><strong>Downloading Thumbnails</strong></p><p>YouTube generates thumbnails at multiple resolutions. Every video has a default thumbnail URL pattern:</p><pre>https://img.youtube.com/vi/[VIDEO_ID]/0.jpg<br>https://img.youtube.com/vi/[VIDEO_ID]/1.jpg<br>https://img.youtube.com/vi/[VIDEO_ID]/2.jpg<br>https://img.youtube.com/vi/[VIDEO_ID]/3.jpg<br>https://img.youtube.com/vi/[VIDEO_ID]/maxresdefault.jpg</pre><p>Replace <strong>[VIDEO_ID]</strong> with the video ID from the URL. For example, if the video URL is <strong>youtube.com/watch?v=abc123def45</strong>, the video ID is <strong>abc123def45</strong>.</p><ul><li><strong>0.jpg</strong> is the auto-generated thumbnail, usually showing a frame from the video.</li><li><strong>1.jpg</strong>, <strong>2.jpg</strong>, <strong>3.jpg </strong>are alternate auto-generated frames.</li><li><strong>maxresdefault.jpg</strong> is the highest resolution custom thumbnail the uploader provided.</li></ul><p>Open any of these URLs in your browser. Right-click and save the image. These URLs are public and require no authentication.</p><p><strong>Downloading Videos via Inspect Element</strong></p><p>YouTube does not provide a direct download link on the video page, but the video file URL is embedded in the page source.</p><p>Open the video page. Right-click and select “<strong>Inspect Element</strong>.” Go to the Network tab in the developer tools panel. Refresh the page. In the filter bar, type <strong>videoplayback</strong>. Look for requests to URLs containing <strong>videoplayback </strong>in the domain. These are the direct video stream URLs.</p><p>Click on one of these requests. In the Headers tab, copy the full Request URL. Open that URL in a new tab. The video file plays directly. Right-click and select “<strong>Save video as</strong>” to download it.</p><p><strong>Alternatively, use command-line tools like </strong>yt-dlp:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dz8ptABzLkaKUoG2q5wcYw.png" /></figure><pre>sudo apt install yt-dlp<br><br>yt-dlp -h<br><br>Proceed:<br><br>yt-dlp https://www.youtube.com/watch?v=abc123def45</pre><p>This downloads the highest quality version available. <strong>yt-dlp</strong> is the successor to <strong>youtube-dl</strong> and is actively maintained. Install it and keep it updated.</p><p><strong>Downloading Subtitles and Closed Captions</strong></p><p>Subtitles are a goldmine for text analysis. YouTube auto-generates captions for most videos, and uploaders sometimes provide their own.</p><p><strong>To download subtitles using </strong>yt-dlp:</p><pre>yt-dlp --write-subs --sub-langs all https://www.youtube.com/watch?v=abc123def45</pre><p>This saves all available subtitle tracks. The resulting text files contain every word spoken in the video, which you can search, analyze, and cross-reference against other platforms.</p><p><strong>Downloading Videos via Browser Extensions (Quick Alternative)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zfQGVE1QVDgKNCBOFTn7AA.png" /></figure><p>If you prefer a graphical interface, browser extensions handle the download process for you. Install one of these:</p><ul><li><strong>Video DownloadHelper </strong>— Available for Firefox and Chrome. Detects video streams on the page and offers one-click download.</li><li><a href="https://savefrom.net/"><strong>SaveFrom.net</strong></a> Helper — Adds a download button directly below the YouTube video player.</li></ul><p>These extensions work by intercepting the video streams as the page loads. They are simpler than command-line tools, but they can break when YouTube updates its delivery system. Use them for quick downloads, but keep <strong>yt-dlp</strong> as your fallback.</p><p>If you cannot install software and cannot use browser extensions, web-based services work as a last resort. Use these with caution. They are third-party sites, and you should never enter any personal credentials.</p><ul><li><a href="http://y2mate.com/"><strong>y2mate.com</strong></a> — Paste the video URL, select format, download.</li><li><a href="http://savefrom.net/"><strong>savefrom.net</strong></a> — Paste the URL, click download.</li><li><a href="http://9xbuddy.com/"><strong>9xbuddy.com</strong></a> — Similar functionality.</li></ul><p>These sites are functional but often filled with ads and pop-ups. Use an ad blocker. Do not click anything that asks you to install software. The download link is usually a small text button after processing.</p><p><strong>Part 6: Email Extraction from Channels</strong></p><p>YouTube channels often list a business inquiry email in the About section. This email is public and intended for contact, but for an investigator, it is a direct attribution link.</p><p>To find it, go to the channel’s About tab. Look for a section labeled “<strong>For business inquiries</strong>” or “<strong>Details</strong>.” The email is displayed there if the channel owner added one.</p><p>Once you have the email, run it through your Module 3 email intelligence workflow. Search it on breach databases. Check social media platforms. Cross-reference it against LinkedIn, GitHub, and forums. A YouTube channel email is often the same email used to register accounts across the web.</p><p><strong>Part 7: Geolocation from YouTube Content</strong></p><p>YouTube videos can reveal location through intentional tags and unintentional background details.</p><p><strong>Geotags</strong></p><p>Some videos include a location tag set by the uploader. This is visible on the video page below the title, next to the view count. It might say something like “Recorded at Central Park, New York.” This is self-reported and may be inaccurate, but document it anyway.</p><p><strong>Background Analysis</strong></p><p>Apply the image geolocation techniques from Module 2. Watch the video frame by frame using the comma (<strong>,</strong>) and period (<strong>.</strong>) keys to move backward and forward one frame at a time. Look for:</p><ul><li>Storefronts and business names.</li><li>Street signs and road markings.</li><li>License plates.</li><li>Distinctive architecture or landmarks.</li><li>Language on signs and posters.</li><li>Vegetation and climate indicators.</li></ul><p>Screenshot key frames. Run them through reverse image search. Plot confirmed locations on a map. One video can reveal where a person lives, works, and spends their free time.</p><p><strong>Part 8: Cross-Platform Attribution</strong></p><p>The YouTube <strong>@handle</strong> is often reused on other platforms. Search the handle on <strong>Twitter</strong>, <strong>Instagram</strong>, <strong>Reddit</strong>, <strong>GitHub</strong>, and <strong>TikTok</strong>. Search the channel name as a plain text string in Google with quotes.</p><p>The channel description links are direct bridges. If the channel links to a Twitter profile, an Instagram account, or a personal website, each of those is a new investigation path.</p><p>The email you extracted from the About tab is a pivot point. Search it everywhere.</p><p>The visual content of the videos themselves can bridge platforms. If a YouTube video shows the same room, same face, or same event as an Instagram post, you have a connection. Screenshot both. Document the correlation.</p><h4><strong>Part 9: Practical Investigation Workflow Summary</strong></h4><ol><li>Open the channel. Document the name, handle, description, creation date, and subscriber count.</li><li>Extract the Channel ID from the page source or using the API.</li><li>Click the About tab. Copy the description, business email, location, and external links.</li><li>Run the channel through <strong>https://mattw.io/youtube-metadata/</strong> for structured data.</li><li>Open individual videos. Extract the video ID, upload timestamp, tags, and description.</li><li>Download thumbnails using the <strong>img.youtube.com/vi/[VIDEO_ID]/</strong> pattern.</li><li>Download subtitles using <strong>yt-dlp --write-subs</strong> for text analysis.</li><li>Analyze video frames for geolocation clues.</li><li>Extract emails from the About tab and page source.</li><li>Cross-reference the handle, email, and external links across all other platforms.</li><li>Preserve everything. Screenshots, downloaded videos, metadata exports, and your investigation notes.</li></ol><h4><strong>Part 10: Quick Reference</strong></h4><p><strong>Objective________________Method</strong></p><ul><li>Channel ID extraction: View Page Source → search for <strong>externalId</strong> or <strong>channelId</strong></li><li>Structured metadata:<strong>https://mattw.io/youtube-metadata/</strong></li><li>Thumbnail download: <a href="https://img.youtube.com/vi/[VIDEO_ID]/maxresdefault.jpg"><strong>https://img.youtube.com/vi/[VIDEO_ID]/maxresdefault.jpg</strong></a></li><li>Video download:<strong>yt-dlp [URL]</strong></li><li>Subtitle download:<strong>yt-dlp --write-subs --sub-langs all [URL]</strong></li><li>Email extraction: About tab → Details section → or search page source for <strong>@gmail.com</strong></li><li>Geolocation analysis: Frame-by-frame review, reverse image search on screenshots</li><li>Cross-platform search: Search<strong> @handle </strong>and email on Twitter, Instagram, Reddit, GitHub</li></ul><p>This is YouTube investigation. Not just watching videos. Extracting hard data, mapping connections, and building attribution from the content people publish to the world. Master this, and every YouTube channel becomes an intelligence source.</p><p><strong>Lecture 4.8: Telegram OSINT — Investigating the Encrypted Messenger</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w00SBYHBZlZPCEQWTXnXRQ.png" /></figure><p>Telegram is not just a messaging app. It is a massive ecosystem of public channels, groups, and bots. People share files, discuss topics openly, run businesses, and build communities, all on a platform that most investigators ignore because they think it is too private.</p><p>Yes, Telegram offers end-to-end encryption for secret chats. But public channels and groups are not encrypted. They are open. They are indexed. They are searchable. And they contain a staggering amount of intelligence for anyone who knows how to look.</p><p>This lecture covers every practical technique you need to find channels, extract user data, map networks, recover deleted content, and use Telegram’s own infrastructure against itself for intelligence collection.</p><p><strong>Part 1: Understanding Telegram’s Structure</strong></p><p>Before you start any investigation, you need to understand how Telegram organizes its content. There are four types of entities you will encounter.</p><p><strong>Users are individual accounts</strong>. Each has a unique numeric ID, a username (optional), a display name, and a phone number (hidden unless shared). The username, if set, is public and searchable.</p><p><strong>Groups are private or public chat spaces</strong>. Public groups have a username and can be joined freely. Private groups require an invite link. Group members are visible to all members.</p><p><strong>Channels are one-way broadcast tools</strong>. The channel owner posts content. Subscribers read it. Channels can be public (searchable, joinable) or private (invite only). Public channels are indexed by Telegram’s search and external tools.</p><p><strong>Bots are automated accounts that perform functions</strong>. Investigative bots can pull user data, download channel content, generate invite links, and more.</p><p><strong>The key insight is this</strong>: public channels and groups are not private. They are broadcast platforms and open forums. Treat them as such.</p><p><strong>Part 2: Account and User Reconnaissance</strong></p><p>You encounter a Telegram username. It looks like <strong>@targetuser</strong>. Before you do anything else, document what is visible.</p><p>Open Telegram. In the search bar at the top, type the username. If the account is public, the profile appears. You will see:</p><ul><li><strong>Display Name</strong>: The name the user chose. This may be real or fake. Document it either way.</li><li><strong>Username</strong>: The <strong>@handle</strong>. This is your primary identifier.</li><li><strong>Bio</strong>: Free-text description. Users often list other social media handles, contact emails, or personal details here. Copy every word.</li><li><strong>Phone Number Visibility</strong>: If the user has chosen to make their number visible, it appears here. This is rare, but when it happens, it is gold.</li></ul><p>If the account does not appear in search, the user has either set their account to private, hidden their username from search, or blocked you. That is intelligence in itself.</p><p><strong>Part 3: User ID Extraction — The Permanent Anchor</strong></p><p>Every Telegram account is assigned a permanent <strong>numeric User ID </strong>at creation. This ID never changes. The username can change. The display name can change. The phone number can change. The User ID remains the same for the life of the account.</p><p>For an investigator, this is the anchor. If a target changes their @handle from <strong>@targetuser</strong> to <strong>@newhandle</strong>, you lose them if you are tracking by username alone. But if you extracted the numeric ID, you can verify the new handle belongs to the same account.</p><p>The User ID also appears in message metadata, forwarded messages, and bot responses. When you scrape a channel and see the same numeric ID appearing across different usernames over time, you know it is the same person operating under different aliases.</p><p>Here are the methods to extract it.</p><p><strong>Method 1: @userinfobot</strong></p><p>Search for <strong>@userinfobot</strong> in Telegram. Start a chat. Forward any message from the target user to the bot. It responds with:</p><pre>User ID: 123456789<br>First Name: John<br>Username: @targetuser</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wqLYDJjBobXXz8mbEnOxUg.png" /></figure><p>The numeric User ID is now yours. Copy it. Store it.</p><p><strong>Method 2: Get Chat_ID &amp; User_ID</strong></p><p>This bot returns the raw JSON data for any message, user, or channel you forward to it. Search for <strong>Get Chat_ID &amp; User_ID</strong>. Forward a message from the target. The bot replies with a JSON dump that includes the sender&#39;s full profile data.</p><p><strong>Look for</strong>:</p><pre>&quot;from&quot;: {<br>    &quot;id&quot;: 123456789,<br>    &quot;first_name&quot;: &quot;John&quot;,<br>    &quot;last_name&quot;: &quot;Doe&quot;,<br>    &quot;username&quot;: &quot;@targetuser&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fpZi2uX1MXMdvUFsVI_j5g.png" /></figure><p>The <strong>id </strong>field is the numeric User ID. This is the most complete user data you can pull from a single bot interaction.</p><p><strong>Method 3: @getidsbot</strong></p><p>Search for <strong>@getidsbot</strong>. Start a chat. Forward a message from the target. The bot returns the User ID, chat ID, and message ID in one clean response. It is fast and straightforward.</p><p><strong>Why the User ID Matters</strong></p><p>Here is exactly how the User ID adds value in real investigations.</p><ul><li><strong>Tracking Through Username Changes</strong>: A target uses <strong>@hackerx</strong>. You extract the User ID: <strong>987654321</strong>. Three months later, <strong>@hackerx</strong> disappears. The account now goes by <strong>@securityresearcher</strong>. You forward a message from the new handle to <strong>@userinfobot</strong>. The bot returns the same User ID: <strong>987654321</strong>. Confirmed. Same account. Same person. The name change did not fool you.</li><li><strong>Cross-Referencing Across Groups</strong>: A user appears in multiple public groups under different usernames. You extract the User ID from messages in each group. The IDs match. You now know these separate personas belong to one individual. The usernames were a distraction. The ID told the truth.</li><li><strong>Linking to Other Data Sources</strong>: Some data breaches and leaked databases include Telegram User IDs alongside email addresses and phone numbers. Having the numeric ID lets you search those datasets with precision. If a breach contains User ID <strong>123456789 </strong>tied to <strong>johndoe@gmail.com</strong>, you just linked an anonymous Telegram account to a real email address.</li><li><strong>Automated Monitoring</strong>: You can write scripts using Telethon that monitor a User ID for activity. Even if the username changes, the script tracks the ID. When the target joins a new group, posts in a channel, or changes their profile, you get an alert. The ID is the constant that makes long-term monitoring possible.</li></ul><p><strong>Workflow Rule</strong>: Every time you encounter a new Telegram account, extract the numeric User ID immediately. Store it alongside the current username and the date of extraction. The username is temporary. The ID is forever.</p><p><strong>Part 4: Phone Number Discovery</strong></p><p>Telegram accounts are tied to phone numbers. The number is private by default, but several techniques can reveal it or confirm it.</p><p><strong>Method 1: Contact Sync Exploitation</strong></p><p>This is the most well-known technique. Telegram allows users to sync their phone contacts with the app. If you add a phone number to your phone’s contacts and that number is registered on Telegram, the account appears in your Telegram contacts list.</p><p>Create a sock puppet Telegram account. Save the target phone number to your device contacts under a fake name. Open Telegram. Navigate to Contacts. If the number is registered on Telegram, the account appears with its display name, username, and profile picture. You just confirmed the phone number is tied to that account.</p><p>This does not notify the target. It is passive. But do this only from a properly maintained sock puppet, never from your personal device.</p><p><strong>Method 2: WHOIS Lookup on Linked Domains</strong></p><p>If the target lists a website in their Telegram bio, run a WHOIS lookup on that domain. The registrant’s phone number may be in the WHOIS record. Cross-reference it using Method 1.</p><p><strong>Method 3: Cross-Platform Leakage</strong></p><p>Many users link their Telegram account to other platforms. Check the target’s Twitter bio, Instagram bio, Facebook About section, and personal website for a Telegram link. If they publicly connect their Telegram to a named account elsewhere, they have just bridged the anonymity gap.</p><p><strong>Part 5: Channel and Group Intelligence</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aK_AA66H-hlmZR70-EUlXA.png" /></figure><p>Public channels and groups are searchable. You can find them through Telegram’s internal search, Google dorks, and specialized indexing services.</p><p><strong>Telegram Internal Search</strong></p><p>Open Telegram. Tap the search bar. Type a keyword. Telegram returns matching users, groups, and channels. This is the most direct method. It is limited to what Telegram chooses to show you, but it is fast.</p><p><strong>Google Dorks for Telegram</strong></p><p>Telegram channels have public web previews. Google indexes these pages.</p><p><strong>Use these dorks to find channels and groups by keyword</strong>:</p><pre>site:t.me &quot;keyword&quot;<br>site:t.me &quot;gmail.com&quot;<br>site:t.me &quot;location&quot;<br>site:t.me &quot;phone&quot;</pre><p><strong>To find channels related to a specific topic</strong>:</p><pre>site:t.me &quot;osint&quot; channel<br>site:t.me &quot;cybersecurity&quot; channel</pre><p><strong>To find invite links shared publicly</strong>:</p><pre>site:t.me &quot;joinchat&quot;<br>site:t.me &quot;+&quot;</pre><p>The <strong>t.me/+</strong> prefix is used for private group invite links. If someone shared a private invite link publicly on a website, forum, or social media, Google indexes it. This is how you find supposedly private groups.</p><p><strong>Specialized Telegram Search Engines</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mU6UKEVMzx7k0FYUCfTuBg.png" /></figure><p>Several third-party services index Telegram channels and make them searchable outside the app.</p><ul><li>Telegago: <a href="https://cse.google.com/cse?cx=006368593537057042503:efxu7xprihg"><strong>https://cse.google.com/cse?cx=006368593537057042503:efxu7xprihg</strong></a><strong> </strong>— A Google Custom Search Engine specifically for Telegram.</li><li><a href="https://telemetr.io/">Telemetr.io</a>: <a href="https://telemetr.io/"><strong>https://telemetr.io</strong></a> — Channel analytics, search, and statistics. Find channels by keyword, see subscriber growth, and view top posts.</li><li>TGStat: <a href="https://tgstat.com/"><strong>https://tgstat.com</strong></a><strong> </strong>— Another channel analytics platform with search, rankings, and post discovery.</li><li>TelegramDB: <a href="https://telegramdb.org/"><strong>https://telegramdb.org</strong></a> — A searchable database of public Telegram channels and groups.</li></ul><p>Use these tools when Telegram’s internal search is insufficient or when you need to discover channels by topic rather than exact username.</p><p><strong>Part 6: Message and Content Scraping</strong></p><p>Once you find a channel or group, you need to collect its content. Manual scrolling is slow. Automated tools are faster.</p><p><strong>Method 1: Telethon (Python Library)</strong></p><p>Telethon is a Python library that interacts with Telegram’s API. It requires a Telegram account and an API key from<strong> </strong><strong>my.telegram.org</strong>. Set up a sock puppet account, get your API credentials, and install Telethon:</p><pre>pip install telethon</pre><p><strong>Then use a simple script to download messages from a channel</strong>:</p><pre>from telethon import TelegramClient<br><br>api_id = YOUR_API_ID<br>api_hash = &#39;YOUR_API_HASH&#39;<br><br>client = TelegramClient(&#39;session_name&#39;, api_id, api_hash)<br><br>async def main():<br>    channel = await client.get_entity(&#39;@channelname&#39;)<br>    messages = await client.get_messages(channel, limit=1000)<br>    for message in messages:<br>        print(message.sender_id, message.date, message.text)<br><br>with client:<br>    client.loop.run_until_complete(main())</pre><p>This downloads the last 1,000 messages from the channel, including sender IDs, timestamps, and message text. Adjust the limit as needed. The <strong>sender_id </strong>is the numeric User ID discussed in Part 3, which means you can track users across username changes directly from your scraped data.</p><p>If you are new to Telethon and want a full walkthrough from setup to execution, <strong>John Hammond</strong> has a practical video guide that covers everything step by step:</p><p><strong>Quick Help</strong>: How to Scrape Telegram with Python — <a href="https://www.youtube.com/watch?v=kCDUbJU99F8"><strong>https://www.youtube.com/watch?v=kCDUbJU99F8</strong></a></p><p>Watch it. Follow along. You will have a working scraper in under thirty minutes.</p><p><strong>Method 2: Export Chat via Telegram Desktop</strong></p><p>If you have access to a group or channel, Telegram Desktop allows you to export the entire chat history. Open Telegram Desktop. Go to the channel or group. Click the three-dot menu. Select “<strong>Export chat history</strong>.” Choose the data you want to export (messages, photos, videos). Telegram generates a JSON or HTML file with the complete history.</p><p>This is useful for preserving evidence from a group you have already infiltrated.</p><p><strong>Part 7: Bot-Assisted Investigation</strong></p><p>Telegram bots are automated tools built into the platform. Many are designed for investigation.</p><p><strong>User Information Bots</strong></p><ul><li><strong>@userinfobot</strong>: Returns user ID, first name, last name, and username.</li><li><strong>@Get Chat_ID &amp; User_ID</strong>: Returns full JSON profile data for any forwarded message.</li><li><strong>@getidsbot</strong>: Returns user ID, chat ID, and message ID.</li><li><strong>@tgscan_bot</strong>: Takes a username and returns related accounts, shared groups, and profile history.</li></ul><p><strong>Channel and Group Analysis Bots</strong></p><ul><li><strong>@ChannelActivityBot</strong>: Analyzes channel engagement and subscriber activity.</li><li><strong>@telebrezebot</strong>: Checks if a specific username appears in any public channel or group.</li><li><strong>@TgStatBot</strong>: Provides channel statistics, growth trends, and post analytics.</li></ul><p><strong>Search and Discovery Bots</strong></p><ul><li><strong>@telescoper_bot</strong>: Searches for users across Telegram by username, name, or phone number (if public).</li><li><strong>@SangMataInfo_bot</strong>: Tracks username changes. Enter a username, and the bot shows previous usernames associated with that account. This is how you discover a target’s old handles.</li></ul><p><strong>Email and Data Leak Bots</strong></p><ul><li><strong>@mailsearcher_bot</strong>: Searches for an email address across Telegram’s public channels and groups. If the email appears in any message, the bot finds it.</li><li><strong>@UniversalSearchBot</strong>: General keyword search across Telegram’s public content.</li></ul><p>Use these bots from your sock puppet account. Never from your personal account.</p><p><strong>Part 8: Browser Extensions for Telegram Investigation</strong></p><p><strong>Telegago Custom Search Engine</strong></p><p>Telegago is a Google CSE that indexes Telegram content. Add it to your browser as a custom search engine, or visit the link directly. Use it to search Telegram without opening the app.</p><p>URL: <a href="https://cse.google.com/cse?cx=006368593537057042503:efxu7xprihg"><strong>https://cse.google.com/cse?cx=006368593537057042503:efxu7xprihg</strong></a></p><p><strong>Save Telegram (Extension)</strong></p><p>The Save Telegram browser extension adds a download button to Telegram Web for photos, videos, and documents. Install it, open Telegram Web, and download channel media with one click.</p><p>Chrome: <a href="https://chromewebstore.google.com/detail/save-telegram"><strong>https://chromewebstore.google.com/detail/save-telegram</strong></a></p><p>Firefox: <a href="https://addons.mozilla.org/en-US/firefox/addon/save-telegram/"><strong>https://addons.mozilla.org/en-US/firefox/addon/save-telegram/</strong></a></p><p><strong>TG Content Downloader — Telegram Downloader</strong></p><p>This browser extension is specifically designed for bulk downloading content from Telegram channels and groups. Unlike Save Telegram which handles individual files, TG Content Downloader allows you to select multiple messages and download all attached media at once.</p><p>Install the extension from your browser’s extension store. Open Telegram Web. Navigate to the target channel or group. The extension adds download buttons next to each message containing media. Click to download individual files, or use the bulk selection feature to queue multiple downloads. Photos, videos, documents, voice messages. All saved to your local machine with original filenames and timestamps.</p><p>Chrome: <a href="https://chromewebstore.google.com/detail/tg-content-downloader"><strong>https://chromewebstore.google.com/detail/tg-content-downloader</strong></a></p><p><strong>Important Note on Operational Security</strong></p><p>All browser extensions for Telegram Web require you to be logged into a Telegram account. Use your sock puppet account for this. Never log into Telegram Web with your personal account while running investigative extensions. Keep your investigation environment separate, just as you would for any other platform.</p><p><strong>Part 9: Geolocation from Telegram Content</strong></p><p>Telegram allows users to share their live location or static location pins. In public groups and channels, these are visible to all members.</p><p>When you encounter a location pin, click it. Telegram opens a map view. The coordinates are visible in the URL when opened in Telegram Web or by inspecting the element.</p><p>Users also post geolocatable images. Apply the techniques from Module 2. Look for background landmarks, street signs, and business names in photos shared on channels. Screenshot them. Run reverse image search. Cross-reference with satellite imagery.</p><p><strong>Part 10: Practical Investigation Workflow Summary</strong></p><ol><li>Search the target username in Telegram. Document the display name, bio, and any linked accounts.</li><li>Forward a message from the target to <strong>@userinfobot</strong> or @<strong>GetChatID&amp;UserIDBot</strong> to extract the numeric User ID.</li><li>Run the username through <strong>@SangMataInfo_bot</strong> to discover previous usernames.</li><li>Search the username on Google with <strong>site:t.me &quot;username&quot;</strong> to find public mentions.</li><li>Use<strong> </strong><a href="https://telemetr.io/"><strong>Telemetr.io</strong></a> and TGStat to find channels the target owns or participates in.</li><li>Use Telegago to search for the target’s username, email, or phone number across indexed Telegram content.</li><li>If the target lists a website, run a WHOIS lookup for contact details.</li><li>Scrape relevant channels using Telethon or snscrape to collect message history.</li><li>Download shared media. Analyze images for geolocation clues.</li><li>Cross-reference the username, email, and phone number against other platforms.</li><li>Document everything. Save screenshots, exported chat histories, and bot responses.</li></ol><p><strong>Part 11: Quick Reference</strong></p><p><strong>Objective_______________Method/Tool</strong></p><ul><li>Extract User ID:<strong>@userinfobot</strong>, <strong>@GetChatID&amp;UserIDBot</strong>, <strong>@getidsbot</strong></li><li>Find previous usernames:<strong>@SangMataInfo_bot</strong></li><li>Search Telegram via Google@:<strong>site:t.me &quot;keyword&quot;</strong></li><li>Custom search engine: <strong>Telegago CSE</strong></li><li>Channel analytics:<strong>telemetr.io</strong>, <strong>tgstat.com</strong></li><li>Message scraping: <strong>Telethon</strong> (Python)</li><li>Email search in channels:<strong>@mailsearcher_bot</strong></li><li>Phone number confirmation: <strong>Contact sync technique via sock puppet</strong></li><li>Channel export: <strong>Telegram Desktop</strong> → <strong>Export chat history</strong></li><li>Username cross-reference:<strong>@tgscan_bot</strong>,<strong> </strong><strong>@telebrezebot</strong></li></ul><h4>Lecture 4.9: TikTok OSINT — Investigating Short-Form Content</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9D8WNQodbN2AjMfykqp9Hw.png" /></figure><p>TikTok has over a billion active users. It is not just dance videos. People post their locations, their homes, their workplaces, their opinions, and their relationships. They do it in short, digestible clips that most investigators scroll past without a second thought.</p><p>That is a mistake.</p><p>TikTok videos contain geolocatable backgrounds, exposed personal details, and links to other platforms. TikTok profiles carry usernames that are often reused across Instagram, Twitter, and YouTube. TikTok bios include email addresses and external links. Ignoring TikTok means leaving a massive source of behavioral data untouched.</p><p>This lecture walks you through every practical technique for investigating TikTok profiles and content. No theory. Just what works.</p><h4>Part 1: TikTok Profile Structure — What Is Publicly Visible</h4><p>Before you touch any tool, understand what TikTok gives you for free on any public profile.</p><p>Open a TikTok profile in your browser. No login required for public accounts. You will see:</p><ul><li><strong>Username</strong>: The @handle. Often reused across platforms. Your first pivot point.</li><li><strong>Display Name</strong>: Can be different from the username. May contain a real name or alias.</li><li><strong>Bio</strong>: Up to 80 characters. Users frequently list other social media handles, contact emails, or personal details here. Copy every word.</li><li><strong>Profile Picture</strong>: The circular avatar. You can open it in a new tab and save the full-resolution version for reverse image search.</li><li><strong>Following Count</strong>: Number of accounts this profile follows.</li><li><strong>Follower Count</strong>: Number of accounts following this profile.</li><li><strong>Like Count</strong>: Total likes across all videos. This is public even if individual liked videos are private.</li><li><strong>Video Count</strong>: Total number of videos posted.</li><li><strong>Pinned Video</strong>: The video the user chose to feature at the top of their profile. This is what they want you to see first.</li><li><strong>External Links</strong>: Any URL in the bio. This may lead to a Linktree, personal website, YouTube channel, or Instagram profile. Each is a new investigation path.</li></ul><p>Document all of this before you go deeper. Screenshot the profile. Save the profile picture. Copy the bio. This is your baseline.</p><h4>Part 2: Extracting the Numeric TikTok User ID using <strong>View Page Source</strong></h4><p>Every TikTok account has a unique, unchangeable numeric User ID. The username can change. The display name can change. The User ID stays the same forever.</p><p>Open the target TikTok profile. Right-click on the page background and select “<strong>View Page Source</strong>.” Press <strong>Ctrl + F</strong> and search for<strong> “userInfo”:</strong> . You are looking for a line that looks like:</p><pre>&quot;userInfo&quot;:{&quot;user&quot;:{&quot;id&quot;:&quot;6345820253489857518&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpUwiXSRCA1JEkxTVJkKjA.png" /></figure><p>That number is the numeric User ID. It is globally unique. Copy it. Store it.</p><h4>Part 2 (Addendum): Finding a TikTok User-ID with Comment Picker — No Source Code Required</h4><p>If you want the User ID without touching the page source, use Comment Picker’s TikTok ID tool.</p><p>Go to: <a href="https://commentpicker.com/tiktok-id.php"><strong>https://commentpicker.com/tiktok-id.php</strong></a></p><p>Enter the target TikTok @username. Click the button. The tool returns the numeric User ID instantly.</p><p>This is the fastest method. No page source. No inspect element. No console. Just type the username and get the ID. Use this when you need quick results across multiple profiles without the technical overhead.</p><h4>Part 3 (Addendum): Resolving the Numeric User ID to a Username — <strong>The URL Pivot</strong></h4><p>You extracted a numeric User ID. Now you need to know what username it currently belongs to. TikTok does not let you search by ID in the app, but the platform resolves IDs internally. Here is how to use that.</p><p>TikTok structures its sharing URLs to accept either the username or the numeric ID. Paste this directly into your browser:</p><pre>https://www.tiktok.com/share/user/target_user_id</pre><p>Replace the <strong>target_user_id</strong> with the<strong> User-ID</strong> you extracted.</p><p>If the account is active and public, TikTok’s web server automatically redirects this URL to the target’s current handle. Your address bar will change to:</p><pre>https://www.tiktok.com/@username</pre><p>You now have the current username. If the account has changed handles multiple times, this URL still resolves to the latest one. The numeric ID is the anchor. This URL proves it.</p><h4>Why This Matters</h4><p>If you stored a numeric User ID from an investigation months ago and the target has changed their username, these methods still find them. The handle changes. The ID does not. This is how you track a TikTok account through rebranding.</p><h4>Part 3: Finding the Account Creation Date</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*viK4siMO3JpCTefjlaAxcw.png" /></figure><p>TikTok does not display the account creation date publicly. But you can find it.</p><p><strong>Method 1: First Video Upload Date</strong></p><p>Scroll to the very bottom of the profile’s video list. The oldest video gives you an approximate creation date. If the first video was posted in March 2020, the account was created around that time. This is not exact but it is a solid estimate.</p><h4>Method 2: Comment Picker — Instant Creation Timestamp</h4><p>Comment Picker, the same tool used for User ID extraction, also returns the exact account creation timestamp. No source code required.</p><p>Go to: <a href="https://commentpicker.com/tiktok-id.php"><strong>https://commentpicker.com/tiktok-id.php</strong></a></p><p>Enter the target TikTok @username. Click the button. Alongside the numeric User ID, the tool displays the account creation date in a readable format.</p><p>This is the fastest method. You get the User ID and the creation date in one step. Document both. The creation timestamp is a temporal anchor. You can cross-reference it against account creation dates on other platforms to build correlation. An account created on TikTok in March 2020 and an Instagram account with the same handle created in February 2020 is a strong link.</p><h4>Part 4: Downloading Videos Without Watermarks</h4><p>TikTok stamps every video with a watermark showing the username. For investigation, you want the clean version. Several methods work.</p><p><strong>Method 1: yt-dlp (Recommended)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgC-841G-lV5rjzwzU6Zbw.png" /></figure><p><strong>yt-dlp</strong> downloads TikTok videos without watermarks in the highest available quality.</p><p><strong>Install</strong>:</p><pre>pip install yt-dlp</pre><p><strong>Download a single video</strong>:</p><pre>yt-dlp https://www.tiktok.com/@username/video/123456789</pre><p><strong>Download all videos from a profile</strong>:</p><pre>yt-dlp https://www.tiktok.com/@username</pre><p><strong>Download with metadata</strong>:</p><pre>yt-dlp --write-info-json https://www.tiktok.com/@username</pre><p>Each video saves alongside a JSON file containing the caption, hashtags, upload timestamp, and music used.</p><p><strong>Method 2: Online Downloaders</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MXvwdJHOYyS8P-MgMu9YKg.png" /></figure><p>If you cannot install yt-dlp, use a web-based tool:</p><ul><li><a href="http://snaptik.app/"><strong>snaptik.app</strong></a> — Paste the video URL. Downloads without watermark.</li><li><a href="http://ttdownloader.com/"><strong>ttdownloader.com</strong></a> — Similar functionality.</li><li><a href="https://tikinsights.com/tools/parse"><strong>https://tikinsights.com/tools/parse</strong></a><strong> </strong>— Similar functionality.</li></ul><p>These work for individual videos. For bulk collection, yt-dlp is the only practical option.</p><h4>Part 5: Extracting Video Thumbnails via Inspect Element</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tVqLoQM-vLN2jaiW_7WvJA.png" /></figure><p>Every TikTok video has a thumbnail image. You can extract it without any third-party tools.</p><p><strong>Step 1: Open the Target Profile</strong></p><p>Navigate to the TikTok profile you are investigating. Scroll until you find the video whose thumbnail you want.</p><p><strong>Step 2: Open Inspect Element</strong></p><p>Right-click on the page background, away from any video or button. Select “<strong>Inspect</strong>” or “<strong>Inspect Element</strong>” from the menu. The browser’s Developer Tools panel opens.</p><p><strong>Step 3: Activate the Element Selector</strong></p><p>Look at the top left corner of the Developer Tools panel. You will see a small icon that looks like a<strong> dotted square</strong> with a <strong>cursor arrow</strong>. This is the element selector tool. Click it once. Your cursor is now in inspection mode.</p><p><strong>Step 4: Click on the Target Video</strong></p><p>Move your cursor over the video whose thumbnail you want. Click on the video. The Developer Tools panel jumps to the specific line of HTML that renders that video element.</p><p><strong>Step 5: Locate the Thumbnail URL</strong></p><p>Look for an <strong>img </strong>tag or a <strong>div </strong>element with a <strong>style </strong>attribute containing a <strong>background-image</strong> property. The thumbnail URL will be embedded there. It will look something like:</p><pre>&lt;img src=&quot;https://p16-sign.tiktokcdn-us.com/...&quot; alt=&quot;...&quot;&gt;</pre><p><strong>Or</strong>:</p><pre>&lt;div style=&quot;background-image: url(https://medium.com/&#39;https://p16-sign.tiktokcdn-us.com/...&#39;)&quot;&gt;&lt;/div&gt;</pre><p><strong>Step 6: Copy and Open the URL</strong></p><p>Click on the URL inside the HTML to select it fully. Copy it. Open a new browser tab. Paste the URL into the address bar. Press Enter.</p><p>The thumbnail image loads in full resolution. Right-click on the image and select “<strong>Save image as</strong>” to save it to your investigation folder.</p><h4>Why Thumbnails Matter</h4><p>The thumbnail is the frame the uploader chose to represent their video. It often shows the most important visual element. A face. A location. A document. A product. You can run the thumbnail through reverse image search without downloading the entire video. This saves time and bandwidth while still producing intelligence.</p><h4>Part 6: Extracting Video Metadata</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OaRXq6wLxDf7rWYkdHdNyA.png" /></figure><p>Every TikTok video carries metadata. Extracting it gives you timestamps, hashtags, and music data.</p><p><strong>Method 1: Page Source Extraction</strong></p><p>Open the video page. Right-click on the page background and select “View Page Source.” Press <strong>Ctrl + F</strong> and search for <strong>createTime </strong>or <strong>create_time</strong>. You will find a Unix timestamp:</p><pre>&quot;createTime&quot;:&quot;1692123456&quot;</pre><p>Copy that number. Go to <a href="http://epochconverter.com/"><strong>epochconverter.com</strong></a>. Paste the number into the input field. The tool converts it to a human-readable date and time in UTC. This is the exact moment the video was uploaded.</p><p><strong>Method 2: Bellingcat TikTok Timestamp Tool (Works Even If the Video Is Deleted or Private)</strong></p><p>If the page source method does not return a timestamp, or if the video has been deleted, set to private, or you are blocked by TikTok’s web firewall, use the Bellingcat tool.</p><p>TikTok embeds the Unix generation time directly into the binary bits of every Video ID using a Snowflake structure. This means the timestamp is mathematically encoded in the video URL itself. You do not need to access TikTok’s servers to extract it.</p><p>Tool: <strong>Bellingcat TikTok Date Extractor</strong></p><p>Link: <a href="https://bellingcat.github.io/tiktok-timestamp"><strong>https://bellingcat.github.io/tiktok-timestamp</strong></a></p><h4>How to use:</h4><ol><li>Copy the full TikTok video URL from your browser. Example:</li></ol><pre>https://www.tiktok.com/@username/video/7234567890123456789</pre><p>2. Paste the URL into the input field on the Bellingcat tool.</p><p>3. Click “<strong>Get uploaded date</strong>.”</p><p>The tool mathematically decodes the bits embedded in the Video ID and returns the exact upload timestamp down to the second in UTC. No API calls. No authentication. No connection to TikTok’s servers. It works entirely in your browser.</p><p><strong>Method 3: Manual Mathematical Breakdown — Understanding the Snowflake ID</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xXA4-ieyhd2QHDt_pSZ9w.png" /></figure><p>If you want to understand what the Bellingcat tool is doing under the hood, or if you want to decode a timestamp manually without any tools, here is the step-by-step mathematical process.</p><p>Every TikTok Video ID is a 64-bit Snowflake integer. The first 31 bits of that integer encode the timestamp. The remaining 33 bits encode sequence data. By isolating the first 31 bits and converting them back to decimal, you get the Unix timestamp in seconds.</p><p><strong>Step 1: Convert the Video ID to Binary</strong></p><p>Take the numeric Video ID from the URL. For example:</p><pre>7248147125599859971</pre><p>Convert this <strong>decimal </strong>number to its 64-bit <strong>binary </strong>representation using a conversion tool.</p><p>Go to: <a href="https://www.rapidtables.com/convert/number/decimal-to-binary.html"><strong>https://www.rapidtables.com/convert/number/decimal-to-binary.html</strong></a></p><p>Paste the Video ID into the input field. Click “<strong>Convert</strong>.” The tool returns the binary equivalent:</p><pre>0110010010010111110111000101010001101101...</pre><p><strong>Step 2: Isolate the First 31 Bits</strong></p><p>The Snowflake structure dictates that the oldest bits, the ones on the far left, hold the time data. Slice out the first 31 characters of that binary string:</p><pre>Full 64-bit string: 0110010010010111110111000101010001101101...<br><br>First 31 bits extracted: 0110010010010111110111000101010</pre><p><strong>Step 3: Convert the 31-bit Binary Back to Decimal</strong></p><p>Take that isolated 31-bit string and convert it back into a standard base-10 integer:</p><pre>Binary: 0110010010010111110111000101010<br><br>Decimal Result: 1687698986</pre><p><strong>Step 4: Translate the Unix Timestamp</strong></p><p>The resulting integer <strong>1687698986 </strong>is a standard Unix timestamp, the number of seconds that have elapsed since January 1, 1970.</p><p>When you parse <strong>1687698986 </strong>through a standard calendar converter like <a href="http://epochconverter.com/"><strong>epochconverter.com</strong></a>, it outputs exactly:</p><pre>Greenwich Mean Time (GMT): Sunday, June 25, 2023, 13:16:26 UTC</pre><h4>Why These Methods Matter</h4><ul><li>The timestamp is extracted from the Video ID itself, not from TikTok’s servers.</li><li>It works even if the video has been deleted.</li><li>It works even if the account is private.</li><li>It works even if TikTok’s web firewall has blocked you.</li><li>You get an exact UTC timestamp you can use in timelines and reports.</li></ul><h4>From yt-dlp JSON Output</h4><p>When you use <strong>yt-dlp --write-info-json</strong>, the resulting JSON file contains additional metadata:</p><ul><li><strong>upload_date</strong> — Exact date in YYYYMMDD format.</li><li><strong>timestamp </strong>— Unix timestamp.</li><li><strong>description </strong>— Full video caption.</li><li><strong>hashtags </strong>— Every hashtag used.</li><li><strong>track </strong>— Music or sound used.</li><li><strong>duration </strong>— Video length in seconds.</li></ul><p>Read the JSON file directly or parse it with a script. Every field is intelligence.</p><h4>Part 7: Geolocation from TikTok Videos</h4><p>TikTok does not have built-in location tags like Instagram. But videos reveal location through content.</p><p><strong>Background Analysis</strong></p><p>Apply the same geolocation techniques from Module 2. Look at:</p><ul><li>Storefronts and business names visible in the background.</li><li>Street signs, license plates, and road markings.</li><li>Distinctive architecture, landmarks, and skylines.</li><li>Language on signs, posters, and product labels.</li><li>Vegetation and climate indicators.</li></ul><p>Pause the video. Use the comma (<strong>,</strong>) and period (<strong>.</strong>) keys to move frame by frame in a browser or media player. Screenshot key frames. Run them through Google Lens and Yandex Images.</p><h4>Stitching and Duet Locations</h4><p>TikTok’s Stitch and Duet features let users respond to other videos. The original video may have been filmed in one location. The response may show a different one. Compare backgrounds. You may find two locations connected through a single interaction.</p><h4>Location Clues in Captions and Hashtags</h4><p>Users tag locations in captions even without a formal geotag. Search captions for city names, neighborhood names, and venue names. Hashtags like <strong>#LondonLife</strong> or <strong>#NYC</strong> are self-reported but still useful as leads.</p><h4>Part 8: Finding Linked Accounts from TikTok Bios</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CA-oQSsladOeoWCp0NHOyg.png" /></figure><p>TikTok bios often contain links to other platforms. These are direct attribution bridges.</p><h4>Direct Links</h4><p>Click any link in the bio. It may go to:</p><ul><li>A Linktree or Beacons page listing multiple social media accounts.</li><li>A YouTube channel.</li><li>An Instagram profile.</li><li>A personal website.</li><li>A business page.</li></ul><p>Each destination is a new platform to investigate. Document every link.</p><h4>Username Cross-Reference</h4><p>If the TikTok bio says “IG: <strong>@sameusername</strong>,” go to Instagram and check that handle. If it exists and the content matches, you have a cross-platform connection. Do the same for <strong>Twitter</strong>, <strong>YouTube</strong>, and <strong>Snapchat</strong>. TikTok users frequently reuse handles.</p><h4>Profile Picture Reverse Search</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8rwA0fo1fugodUZvu0fHHw.png" /></figure><p>Download the TikTok profile picture. Run it through Google Lens and Yandex Images. If the same image appears on LinkedIn, Twitter, or a forum, you have another cross-platform link. This is how you connect an anonymous TikTok account to a named profile elsewhere.</p><h4>Part 9: Analyzing Hashtag Participation for Network Mapping</h4><p>Hashtags group content by topic. They also group people.</p><h4>Finding Related Accounts</h4><p>Click on a hashtag the target uses. TikTok shows all public videos with that tag. Browse the videos. Look for other accounts posting similar content. These are potential associates, collaborators, or members of the same community.</p><h4>Tracking Hashtag Campaigns</h4><p>If a target participates in a hashtag campaign, search that hashtag across platforms. A <strong>hashtag </strong>used on <strong>TikTok </strong>may also appear on <strong>Instagram</strong>, <strong>Twitter</strong>, and <strong>YouTube</strong>. This reveals cross-platform activity and a wider network of participants.</p><h4>Part 10: TikTok-Specific Search Operators and Dorks</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N0xxHRkYkyD130_ZQbfLTw.png" /></figure><p>TikTok has an internal search bar, but Google indexes TikTok content too.</p><p><strong>Google Dorks for TikTok</strong></p><pre>site:tiktok.com &quot;username&quot;<br><br>site:tiktok.com &quot;@username&quot;<br><br>site:tiktok.com &quot;username&quot; &quot;gmail.com&quot;<br><br>site:tiktok.com &quot;username&quot; &quot;instagram&quot;</pre><p>These find TikTok profiles, mentions in video descriptions, and any email addresses or social media handles publicly listed.</p><h4>TikTok Internal Search</h4><p>Use TikTok’s search bar. Type a username, a hashtag, or a keyword. TikTok returns accounts, videos, sounds, and hashtags. This is the most direct way to find content by topic.</p><h4>Searching by Sound</h4><p>Every TikTok video uses a sound. Click on the sound from any video. TikTok shows every other video using that same audio. This is how you find all content within a trend or audio meme. If a target uses a specific sound, browse the other videos using it. You may find associates or discover additional accounts operated by the same person.</p><h4>Part 11: Practical Investigation Workflow Summary</h4><ol><li>Open the TikTok profile. Document the username, display name, bio, follower count, following count, like count, and video count.</li><li>Extract the numeric User ID from the page source or console.</li><li>Estimate the account creation date from the oldest video or cross-reference with other platforms.</li><li>Download the profile picture. Save it. Run it through reverse image search.</li><li>Click every link in the bio. Document all external platforms.</li><li>Download key videos using <strong>yt-dlp</strong>. Save metadata with <strong>--write-info-json</strong>.</li><li>For bulk collection, run <strong>yt-dlp </strong><a href="https://www.tiktok.com/@username."><strong>https://www.tiktok.com/@username.</strong></a></li><li>Extract video metadata: upload timestamps, captions, hashtags, and music.</li><li>Analyze video frames for geolocation clues. Screenshot and reverse search key frames.</li><li>Search the username on Google with <strong>site:tiktok.com &quot;username&quot;</strong>.</li><li>Cross-reference the username, profile picture, and linked accounts across Instagram, Twitter, YouTube, and other platforms.</li><li>Document everything. Screenshots, downloaded videos, metadata files, and your analysis.</li></ol><h4>Part 12: Quick Reference</h4><p><strong>Objective______________Method</strong></p><ul><li><strong>Extract User ID</strong>: View Page Source → search for <strong>id</strong> or use <a href="http://commentpicker.com/tiktok-id.php"><strong>commentpicker.com/tiktok-id.php</strong></a></li><li>Resolve User ID to username:<strong>https://www.tiktok.com/share/user/[ID]</strong></li><li>Find account creation date<a href="http://Download single video	yt-dlp [video URL]"><strong>commentpicker.com/tiktok-id.php</strong></a> or oldest video estimate</li><li>Download single video:<strong>yt-dlp [video URL]</strong></li><li>Download all videos from profile:<strong>yt-dlp</strong> <a href="https://www.tiktok.com/@username"><strong>https://www.tiktok.com/@username</strong></a></li><li>Extract video metadata:<strong>yt-dlp --write-info-json</strong></li><li>Extract upload timestamp from Video IDPage source (<strong>createTime</strong>), <a href="http://Download video thumbnail	Inspect Element → element selector → click video → copy image URL"><strong>bellingcat.github.io/tiktok-timestamp</strong></a>, or Python script using <strong>&gt;&gt; 33</strong></li><li>Download video thumbnail: <strong>Inspect Element</strong> → <strong>element selector</strong> → <strong>click video</strong> → <strong>copy image URL</strong></li><li>Profile picture extraction: <strong>Right-click</strong> → <strong>Open image in new tab</strong> → <strong>Save</strong></li><li>Frame-by-frame video analysis: <strong>Period </strong>(.) forward, <strong>Comma </strong>(,) backward in browser or E key in VLC</li><li>Reverse image search: Google Lens, Yandex Images, TinEye, Bing Images</li><li>Find linked accounts: Bio links, username cross-reference across platforms</li><li>Hashtag network mapping: Click hashtag → browse videos using same hashtag</li><li>Google dork for TikTok:<strong>site:tiktok.com &quot;username&quot;</strong></li></ul><p>This is TikTok OSINT. Not scrolling endlessly. Systematic extraction of identifiers, timestamps, thumbnails, video frames, and connections from the platform everyone underestimates. Master this, and you add a billion-user intelligence source to your toolkit.</p><h4>Lecture 4.10: Bluesky OSINT — Investigating the Decentralized Network</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yX8QAW8elTKMBwbEEmok2Q.png" /></figure><p>Bluesky is the new player in the social media landscape. Built on the AT Protocol, it looks like Twitter but works differently under the hood. It is decentralized. It is open. And because it is built by developers who value transparency, it exposes far more data through public APIs and page source than most platforms ever have.</p><p>For an investigator, Bluesky is a gift. User IDs are permanent and publicly accessible. Account creation dates are embedded in the page source. Posts are indexed and searchable. Images are easy to extract. The platform was designed for openness. Your job is to use that openness for intelligence gathering.</p><p>This lecture covers everything from basic profile reconnaissance to advanced image extraction. Every technique is practical. Every method works today.</p><h4>Part 1: Understanding Bluesky’s Structure</h4><p>Bluesky uses the AT Protocol, which is fundamentally different from Twitter’s architecture.</p><h4>Key concepts:</h4><ul><li><strong>DID (Decentralized Identifier)</strong>: Every user has a unique DID that looks like <strong>did:plc:abcdef123456</strong>. This is the permanent identifier. The handle can change. The DID never does.</li><li><strong>Handle</strong>: The username people see, like <strong>@username.bsky.social</strong>. Users can also set custom domain handles like <strong>@username.com</strong>. Handles can change. DIDs cannot.</li><li><strong>PDS (Personal Data Server)</strong>: Where user data is stored. The platform is decentralized, so data lives on different servers.</li><li><strong>Public API</strong>: Bluesky’s API is open. No authentication required for public data. This makes automated collection straightforward.</li></ul><h4>Part 2: Profile Reconnaissance — The Surface Level</h4><p>Start with what is visible on the profile page.</p><p><strong>Open the target’s Bluesky profile in your browser</strong>:</p><pre>https://bsky.app/profile/username.bsky.social</pre><h4><strong>Document everything</strong>:</h4><ul><li><strong>Display Name</strong>: May contain a real name or alias.</li><li><strong>Handle</strong>: The @username. Often reused across platforms.</li><li><strong>Bio</strong>: Free-text description. Users list other social media handles, contact emails, locations, and affiliations here. Copy every word.</li><li><strong>Banner Image</strong>: The header image at the top of the profile.</li><li><strong>Profile Picture</strong>: The avatar.</li><li><strong>Follower Count</strong>: Number of accounts following the target.</li><li><strong>Following Count</strong>: Number of accounts the target follows.</li><li><strong>Post Count</strong>: Total number of posts.</li><li><strong>Pinned Post</strong>: The post the user chose to feature. This is what they want you to see first.</li><li><strong>Joined Date</strong>: Sometimes displayed on the profile. If not visible, you will extract it from the page source.</li></ul><p>Screenshot everything. This is your baseline.</p><h4>Part 3: User ID Extraction — The DID</h4><p>Every Bluesky account has a DID. It looks like <strong>did:plc:abcdef123456</strong>. This never changes. The handle can change. The DID is permanent. Extract it.</p><p><strong>Method 1: Page Source</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g_tOcWpq4KQzcy7amo3Ujw.png" /></figure><p>Open the target profile. Right-click on the page background. Select “<strong>View Page Source</strong>.” Press <strong>Ctrl + F</strong> and search for <strong>did:plc:</strong>. You will find a line like:</p><pre>content=&quot;did:plc:abcdef123456&quot;</pre><p>That is the <strong>DID</strong>. Copy it. Store it.</p><p><strong>Method 2: The DID Resolver</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOh9yzIJ603bTjJrzefOrw.png" /></figure><p>Every Bluesky DID resolves to a DID document that contains the account’s public metadata. Open your browser and navigate to:</p><pre>https://plc.directory/did:plc:abcdef123456</pre><p>Replace the <strong>DID </strong>with the one you extracted. The page returns a JSON object containing the handle, the public signing key, and the PDS endpoint. This is the technical backbone of the account. Document everything.</p><p><strong>Method 3: Third-Party Tools</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEFjlmpmfwsuKDie5qHLMQ.png" /></figure><p>PDSls at <a href="https://pdsls.dev/"><strong>https://pdsls.dev</strong></a> is a Bluesky directory and search tool. Enter a handle or DID. It returns the account&#39;s DID document, associated records, and metadata. Use it when you need a clean, structured view of the account&#39;s technical profile without digging through raw JSON.</p><p><strong>Method 4: Validating the DID via Direct Profile URL</strong></p><p>Once you have extracted the DID, you can validate it and navigate directly to the account’s profile by pasting the DID into Bluesky’s profile URL structure:</p><pre>https://bsky.app/profile/did:plc:yf6hctt2ug3qyfty4in64yob</pre><p>Replace the <strong>DID </strong>with the one you extracted. Open the URL in your browser.</p><p>If the DID is valid, Bluesky loads the profile page directly. You will see the display name, handle, bio, follower count, and all posts. This confirms the DID is real and resolves to an active account.</p><p>If the account has changed its handle multiple times, this URL still resolves to the current profile. The handle may change. The DID never does. This is how you track a Bluesky account through rebranding. Store the DID-based URL alongside the current handle in your investigation file.</p><h4>Part 4: Account Creation Date Extraction</h4><p>Bluesky embeds the account creation timestamp in the page source and in the DID document.</p><p><strong>Method 1: Page Source</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*bH8KNUGnYd3hchVSmbWDZw.png" /></figure><p>Open the target profile. View Page Source. Search for dateCreated”:. You will find:</p><pre>&quot;dateCreated&quot;:&quot;2023-05-15T10:30:00.000Z&quot;</pre><p>This is the exact ISO 8601 timestamp of account creation. Convert it to your local time if needed. This is precise, not an estimate.</p><p><strong>Method 2: Analyzing the DID Audit Log</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3UvJ2eD4AACG5mUWmqGPg.png" /></figure><p>Every Bluesky account is tied to a unique Decentralized Identifier (DID). For accounts using the standard <strong>did:plc</strong> format, you can uncover a permanent, tamper-proof history of the account, including its exact creation time by querying the public PLC Directory.</p><p><strong>Step 1:</strong> <strong>Locate the DID:</strong> Extract the target account’s unique <strong>did:plc:...</strong> identifier.</p><p><strong>Step 2</strong>: <strong>Access the Audit Log:</strong> Insert the target’s DID into the following URL format:</p><pre>https://plc.directory/[TARGET_DID]/log/audit</pre><p>Replace [<strong>TARGET_DID</strong>] with the actual DID you extracted from the target.</p><p><strong>Step 3:</strong> <strong>Review the JSON Payload:</strong> Opening this URL returns a public audit log. The very first entry in the JSON array represents the account’s creation (the genesis operation), which includes a server-verified <strong>createdAt</strong> ISO timestamp:</p><pre>[<br>  {<br>    &quot;type&quot;: &quot;plc_operation&quot;,<br>    &quot;createdAt&quot;: &quot;2023-05-15T10:30:00.000Z&quot;,<br>    &quot;alsoKnownAs&quot;: [<br>      &quot;at://username.bsky.social&quot;<br>    ],<br>    &quot;services&quot;: {<br>      &quot;atproto_pds&quot;: {<br>        &quot;type&quot;: &quot;AtprotoPersonalDataServer&quot;,<br>        &quot;endpoint&quot;: &quot;https://bsky.social&quot;<br>      }<br>    }<br>  }<br>]</pre><p>This is the same timestamp. It is permanent. It never changes. Document it.</p><h4>Why This Matters</h4><p>The creation timestamp is a temporal anchor. Cross-reference it against account creation dates on Twitter, Instagram, GitHub, and other platforms. An account created on Bluesky in May 2023 and a Twitter account created in April 2023 with the same handle is a correlation point. The timestamp builds your attribution case.</p><p><strong>OSINT Tip<em>:</em></strong><em> </em>Because the PLC Directory operates as a public transparency log, this timestamp is cryptographically validated on the server side. It provides an indisputable timeline for when the account was initialized, making it impossible for a user to spoof or hide their true creation date.</p><h4>Part 5: Bio Analysis and Cross-Platform Attribution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMKHV3kGPuq_IF3UMMwxCw.png" /></figure><p>The Bluesky bio is a text field. Users often list other social media handles, contact emails, and personal details here.</p><h4>What to Look For:</h4><ul><li><strong>Other platform handles</strong>: “IG: @username”, “Twitter: @username”, “GitHub: username”</li><li><strong>Email addresses</strong>: Rare but sometimes included for business inquiries</li><li><strong>Locations</strong>: “London”, “NYC”, “Berlin”</li><li><strong>Occupations</strong>: “Security Researcher”, “Journalist”, “Developer”</li><li>Pronouns and personal details</li></ul><h4>Cross-Referencing the Handle</h4><p>Take the Bluesky handle. Search it on Twitter, Instagram, TikTok, GitHub, and Reddit. Users who migrate to Bluesky often bring their existing handles with them. A match is a direct platform bridge.</p><h4>Cross-Referencing the Display Name</h4><p>Some users use their real name as their display name. Search it on LinkedIn, Facebook, and Google. Cross-reference with other platforms.</p><h4>Part 6: Banner and Profile Image Extraction</h4><p>Bluesky stores the banner image and profile picture as publicly accessible URLs embedded in the page source.</p><p><strong>Method 1: Page Source</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X2slXD8OjQKTQUk6-yWafA.png" /></figure><p>Open the target profile. View Page Source. Search for <strong>og:image</strong>. You will find:</p><pre>&lt;meta property=&quot;og:image&quot; content=&quot;https://cdn.bsky.app/img/avatar/plain/did:plc:abcdef123456/avatar@jpeg&quot;&gt;</pre><p>The <strong>content </strong>attribute contains the direct URL to the profile banner. Open the URL in a new tab. The full-resolution image loads. Right-click and save.</p><p><strong>Method 2: Inspect Element</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_fYZhpzgGQOG1Cg8vDhtQ.png" /></figure><p>Right-click on the profile picture or banner image on the profile page. Select “<strong>Inspect</strong>” or “<strong>Inspect Element</strong>.” The Developer Tools panel opens, highlighting the HTML that renders that image.</p><p>Look for the <strong>src </strong>attribute within the <strong>img </strong>tag. It will look like:</p><pre>&lt;img src=&quot;https://cdn.bsky.app/img/avatar/plain/did:plc:abcdef123456/avatar@jpeg&quot;&gt;</pre><p>Copy the full URL. Open it in a new tab. Save the image at full resolution.</p><p>Alternatively, use the element selector tool. Click the dotted square icon at the top left of the Developer Tools panel (<strong>Ctrl + Shift + C</strong>). Move your cursor over the profile picture or banner. Click on it. The HTML jumps to the correct line. Copy the URL.</p><p><strong>Method 3: PDSls</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Qt5hENhaRhAQxzFPDCFpA.png" /></figure><p>Search the handle on <a href="https://pdsls.dev/"><strong>https://pdsls.dev</strong></a>. The tool displays the avatar and banner URLs directly in the profile view. Copy them from there without touching the page source.</p><h4>What You Do With the Images</h4><p>Run the profile picture and banner through Google Lens, Yandex Images, and TinEye. If the same image appears on Twitter, Instagram, or LinkedIn, you have a cross-platform attribution bridge. The banner image often contains additional intelligence. A banner showing a city skyline is a location clue. A banner with text may contain contact details or affiliations.</p><h4>Part 7: Post Analysis — Extracting Timestamps</h4><p>Every Bluesky post has an exact timestamp. The interface shows relative time (“<strong>7mo</strong>” for <strong>seven months </strong>ago). You need the exact timestamp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o2XAtTT5M_Zij16qeERL-g.png" /></figure><p>Navigate to the target’s profile. Scroll to the post you want to analyze. Click on the relative timestamp, such as “<strong>7mo</strong>” or “<strong>2d</strong>.” The page expands to show the exact date and time in a tooltip or by navigating to the post’s detail view. The URL changes to something like:</p><pre>22:02 · 30 Dec 2025</pre><p>The full timestamp is displayed on this page. Document it.</p><h4>Part 8: Extracting Posted Images via Network Tab and Chrome Extension</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SYhDnwAoKcFZfbby8mXOmQ.png" /></figure><p>This technique extracts every image posted by the user in bulk using the browser’s Network tab.</p><p><strong>Step 1</strong>: Navigate to the target’s Bluesky profile page.</p><p><strong>Step 2</strong>: Open Developer Tools (<strong>F12 </strong>or <strong>Ctrl + Shift + I</strong>). Click the Network tab.</p><p><strong>Step 3</strong>: In the filter bar, type <strong>img </strong>to show only image-related network requests.</p><p><strong>Step 4</strong>: Refresh the page (<strong>F5</strong>). The Network tab populates with requests.</p><p><strong>Step 5</strong>: Look for requests to URLs containing <strong>cdn.bsky.app/img. </strong>These are the user&#39;s posted images. Each image the user has posted that loads on the page appears as a separate request.</p><p><strong>Step 6</strong>: Scroll down the profile to load more posts. As new posts load, new image requests appear in the Network tab. The more you scroll, the more images populate.</p><p><strong>Step 7</strong>: To download an image, you can double click on the image request line and it will pop up the image in a new tab. Or simply click on the request line, navigate to “<strong>preview</strong>” and right-click on the image to save it.</p><h4>Extracting All Loaded Images at Once</h4><p>To extract every image currently loaded in the Network tab without downloading them one by one:</p><p><strong>Method 1: HAR Export</strong></p><p><strong>Step 1</strong>: After scrolling to load the desired posts, right-click anywhere inside the Network tab.</p><p><strong>Step 2</strong>: Select “<strong>Save all as HAR with content</strong>.” This saves a HAR (HTTP Archive) file containing every request, including all loaded images, as base64-encoded data.</p><p><strong>Step 3</strong>: Use a <strong>HAR viewer </strong>or a Python script to extract the images from the HAR file. Save the HAR file and process it offline. Every image that loaded during your session is recoverable.</p><p><strong>Method 2: Chrome Extensions for One-Click Downloads</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*8-fLgYMhMynWY7rNEMG2ZQ.png" /></figure><p>If you prefer a graphical approach without touching the Network tab or console, use a dedicated Bluesky scraper extension.</p><p><strong>Bluesky Media Downloader</strong></p><p>Install from the Chrome Web Store:</p><pre>https://chromewebstore.google.com/detail/bluesky-media-downloader/odebdafkpnmipmdangfpfbhdamhdocdb</pre><p>Navigate to the target profile, click the extension icon, customize your settings, switch to bulk mode, set your max posts per run, and click “Start Bulk Download” — every image saves directly to your machine with no Network tab, no console, and no command line.</p><p>Install, click, download. Use this when speed and simplicity are the priority.</p><h4>Part 9: Using PDSls for Deeper Intelligence</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnp9JcA3FkAaobJDejJ38A.png" /></figure><p>PDSls at <a href="https://pdsls.dev/"><strong>https://pdsls.dev</strong></a> is a directory and inspection tool for the AT Protocol. It gives you structured access to account data without touching the page source.</p><h4>Search by Handle or DID</h4><p>Enter a Bluesky handle or DID. The tool returns:</p><ul><li>The full DID document</li><li>Avatar and banner URLs</li><li>Associated PDS endpoint</li><li>Public records and collections</li></ul><h4>Browse Account Records</h4><p>PDSls lets you browse the account’s public records, including posts, likes, and follows. This is API-level access through a clean web interface. No coding required.</p><h4>Find Related Accounts</h4><p>Some accounts link to other DIDs through their records. PDSls surfaces these connections. If the target has linked a website domain to their Bluesky account, PDSls shows the verification record. This is a direct bridge to the domain’s WHOIS data and ownership information.</p><h4>Part 10: Google Dorking for Bluesky</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-yG0zTzw9fO13TSSRUYYg.png" /></figure><p>Bluesky profiles and posts are indexed by Google. You can use dorks to find profiles, posts, and public mentions without touching the Bluesky app.</p><p><strong>Find Bluesky Profiles by Username or Display Name</strong></p><pre>site:bsky.app &quot;username&quot;<br>site:bsky.app &quot;display name&quot;</pre><p><strong>Find Bluesky Profiles with Specific Keywords in Bio</strong></p><pre>site:bsky.app &quot;security researcher&quot;<br>site:bsky.app &quot;osint&quot;<br>site:bsky.app &quot;investigator&quot;</pre><p><strong>Find Posts Containing Specific Keywords</strong></p><pre>site:bsky.app &quot;keyword&quot;<br>site:bsky.app &quot;email&quot;<br>site:bsky.app &quot;@gmail.com&quot;</pre><p><strong>Find Posts from a Specific User</strong></p><pre>site:bsky.app &quot;username&quot; &quot;keyword&quot;</pre><p><strong>Find Bluesky Handles Mentioned on Other Websites</strong></p><pre>&quot;bsky.app&quot; &quot;username&quot;<br>&quot;@username.bsky.social&quot;<br>&quot;did:plc:&quot;</pre><p>This last dork finds pages outside Bluesky where a DID or handle is referenced. It surfaces forum posts, blog comments, and social media bios where the target listed their Bluesky account.</p><h4>Cross-Engine Search</h4><p>Run the same dorks on Yandex and Bing. Google indexes Bluesky well, but different engines catch different results. A post invisible to Google may appear on Bing.</p><h4>Part 11: Practical Investigation Workflow Summary</h4><ol><li><strong>Open the target Bluesky profile.</strong> Document the display name, handle, bio, follower and following counts, and post count.</li><li>Google dork the handle and display name. Run <strong>site:bsky.app &quot;username&quot;</strong> and <strong>&quot;@username.bsky.social&quot;</strong> across Google, Yandex, and Bing. Find external mentions and indexed posts.</li><li><strong>Extract the DID from the page source or PDSls.</strong> This is the permanent identifier.</li><li><strong>Pull the account creation timestamp </strong>from the page source or DID document.</li><li><strong>Save the profile picture and banner image.</strong> Run them through reverse image search.</li><li>Analyze the bio for other platform handles, locations, and contact details.</li><li>Cross-reference the handle and display name across Twitter, Instagram, TikTok, GitHub, and LinkedIn.</li><li>Click on relative post timestamps to reveal exact dates. Or extract timestamps from the page source.</li><li>Use the Network tab to extract all posted images in bulk. Save as HAR for offline processing.</li><li>Use Inspect Element to extract individual images with precision.</li><li>Run PDSls searches for structured account data and related records.</li><li>Document everything. Screenshots, extracted IDs, timestamps, and your analysis.</li></ol><h4>Part 11: Quick Reference</h4><p><strong>Objective__________Method</strong></p><ul><li>Extract DID (User ID): Page Source → search for <strong>did:plc:</strong></li><li>Resolve DID to metadata:<strong>https://plc.directory/did:plc:...</strong></li><li>Account creation timestamp: Page Source → <strong>createdAt </strong>or DID document</li><li>Banner image extraction: Page Source → <strong>og:image</strong> or Inspect Element</li><li>Post timestamp extraction: Click relative time or Inspect Element → <strong>datetime</strong></li><li>Bulk image extraction: Network tab → filter <strong>img </strong>→ Save as HAR</li><li>Structured account data:<a href="https://pdsls.dev/"><strong>https://pdsls.dev</strong></a></li><li>Google dork for Bluesky:<strong>site:bsky.app &quot;username&quot;</strong></li><li>Find external mentions:<strong>&quot;@username.bsky.social&quot;</strong> or <strong>&quot;did:plc:&quot;</strong></li><li>Cross-platform handle search: Search handle on <strong>Twitter</strong>, <strong>Instagram</strong>, <strong>TikTok</strong>, <strong>GitHub</strong></li><li>Reverse image search: <strong>Google Lens</strong>, <strong>Yandex</strong>, <strong>TinEye</strong></li></ul><p>This is Bluesky OSINT. The platform was built for transparency. It gives you permanent identifiers, public APIs, and page source metadata that other platforms hide. Use that openness. Extract the DID. Pull the timestamps. Download the images. Cross-reference everything.</p><p><strong>A quick note</strong>: nearly every piece of intelligence you gather via View Page Source can also be gathered via Inspect Element. The same data is there. The same URLs. The same timestamps. The same DIDs. If you prefer the visual element selector over searching raw HTML, use Inspect Element. If you prefer scanning the full source at once, use View Page Source. Both paths lead to the same intelligence. Choose whichever works faster for you.</p><p>This is what investigation looks like when the platform does not fight back.</p><h4>Lecture 4.11: Discord OSINT — Investigating the Chat Platform</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NOzs-RAviCtPWGYIxhKVxQ.png" /></figure><p>Discord is not just a chat app for gamers. It is where communities form, where developers collaborate, where activists organize, and where threat actors operate. Servers dedicated to everything from cryptocurrency trading to open source intelligence exist alongside private invite-only groups. People share files, link their other social accounts, and post messages they assume are semi-private.</p><p>Most investigators ignore Discord because it feels closed. It is not. Public servers are accessible. User IDs are permanent. Connected accounts are visible. Invite links are indexed. There is intelligence on Discord for anyone willing to look.</p><p>This lecture covers every practical technique for investigating Discord users and servers. No theory. Just what works.</p><h4>Part 1: Understanding Discord’s Structure</h4><p>Discord is organized differently from other platforms. You need to understand the architecture before you investigate.</p><ul><li><strong>Users</strong>: Individual accounts. Each has a username, a display name, a numeric User ID, a profile picture, and optional connected accounts.</li><li><strong>Servers</strong>: Communities that contain channels. Servers can be public (anyone can join via invite link) or private (invite only).</li><li><strong>Channels</strong>: Text or voice spaces within a server. Messages in public channels are visible to all server members.</li><li><strong>Messages</strong>: Text, images, files, and links posted in channels. Messages in public servers can be viewed by anyone who joins.</li><li><strong>Direct Messages (DMs)</strong>: Private conversations between users. You cannot access these without compromising an account. Do not try.</li></ul><p><strong>The key insight is this</strong>: public servers and the users within them leave traces that are visible without authentication.</p><h4>Part 2: Extracting the Permanent Discord User ID</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFOHdNLE_3YNSN7hJiCVjg.png" /></figure><p>Every Discord user has a permanent numeric User ID. The username can change. The display name can change. The User ID never does. This is your anchor.</p><p><strong>Step 1: Enable Developer Mode</strong></p><p>Open Discord. Go to User Settings (the gear icon next to your username). Scroll down to Advanced in the left sidebar. Toggle Developer Mode to ON. This unlocks the ability to copy IDs.</p><p><strong>Step 2: Copy the User ID</strong></p><p>Navigate to the target user’s profile. You can do this by clicking their name in a server, in a direct message list, or in a friend list. Once on their profile, click the three-dot menu in the top right. Select Copy User ID.</p><p><strong>The ID is now on your clipboard. It looks like</strong>:</p><pre>123456789012345678</pre><p>This is the permanent identifier. Store it.</p><h4>Step 3: Validate the User ID</h4><p>Discord has a native URL format that targets a specific User ID. Construct a direct link to the user profile using the web URL format:</p><pre>https://discord.com/users/USER_ID_HERE</pre><p>Replace the <strong>USER_ID_HERE</strong> with the User ID you extracted. Open this URL in your browser.</p><p>If the ID is valid, Discord loads a profile card showing the user’s public information: current username, display name, avatar, and badges. You have confirmed the ID is real and resolves to an active account.</p><p>If the ID is invalid or the account has been deleted, Discord shows an error or a blank profile.</p><h4><strong>Alternative: Deep-Link for the Discord App</strong></h4><p>Using Discord-id-lookup</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPP5jhQkmx_bVm2bvBbP8w.png" /></figure><p>To open the profile directly in the Discord desktop app instead of a browser:</p><pre>discord://-/users/USER_ID_HERE</pre><p>This forces the Discord app to open and display the target’s profile card.</p><h4>Alternative: Third-Party Lookup</h4><p>If you want to fetch publicly available profile data outside of Discord entirely, use:</p><ul><li><a href="https://discord.id/"><strong>https://discord.id</strong></a><strong> </strong>— Set your bot token, paste the User ID. Returns avatar URL, banner URL, creation date, and public flags without opening Discord.</li><li><a href="https://www.nicheprowler.com/tools/discord/discord-id-lookup"><strong>https://www.nicheprowler.com/tools/discord/discord-id-lookup</strong></a><strong> </strong>— paste the User ID. Returns avatar URL, banner URL, creation date, and public flags without opening Discord.</li></ul><h4>Part 3: Finding the Account Creation Date via Snowflake ID</h4><p>Discord uses the same Snowflake ID structure as TikTok. The User ID encodes the account creation timestamp in its first bits.</p><p><strong>Method 1: Discord Lookup Websites</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJWVUL4zveEE5wxhEJopbA.png" /></figure><p>Several websites decode Discord Snowflakes automatically.</p><p>Go to <a href="https://www.nicheprowler.com/tools/discord/discord-id-lookup"><strong>https://www.nicheprowler.com/tools/discord/discord-id-lookup</strong></a><strong> </strong>— Paste the User ID. The site returns:</p><ul><li>Account creation date and time in UTC.</li><li>The exact timestamp down to the second.</li></ul><p>This is the fastest method. No math required.</p><p><strong>Method 2: Manual Snowflake Decoding</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVYoEK7OWpb3Ou9EHWs_jw.png" /></figure><p>Discord Snowflakes do store the time elapsed since Discord’s epoch (January 1, 2015), shifted by 22 bits. To get the exact Unix timestamp in seconds, the mathematically correct formula is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*LQOOSgKgqiq62UltNdww3g.png" /></figure><h4>Step-by-Step How to Do It Properly:</h4><ol><li><strong>Bit-shift the ID:</strong> Right-shift the Discord User ID by 22 bits (or divide it by <strong>4194304 </strong>and discard the remainder/decimal). This extracts the milliseconds since Discord’s epoch.</li><li><strong>Add the Epoch:</strong> Add <strong>1420070400000</strong> (Discord&#39;s epoch in milliseconds) to that number. This gives you the Unix timestamp in <em>milliseconds</em>.</li><li><strong>Convert to Seconds:</strong> Divide the total by <strong>1000 </strong>to get the timestamp in seconds, which you can then paste into EpochConverter.</li></ol><h4>Let us do this with an actual Discord User-ID:</h4><p>The Math Breakdown:</p><ul><li><strong>Discord Snowflake ID:</strong> <strong>357121971798016000</strong></li><li><strong>Bitwise Right-Shift ( &gt;&gt; 22):</strong> Shifting the binary bits to the right by 22 is mathematically equivalent to dividing the number by <strong>2 </strong>raise to power <strong>22 </strong>(which is<strong> 4,194,304</strong>) and discarding any remainder.</li><li><strong>357121971798016000</strong> / <strong>4194304 </strong>= <strong>85144512061</strong></li><li><strong>Add Discord’s Epoch:</strong> Now we add Discord’s custom epoch offset (<strong>1420070400000</strong> milliseconds).</li><li><strong>85144512061 </strong>+ <strong>1420070400000 </strong>= <strong>1505214912061</strong></li><li><strong>Convert to Seconds:</strong> Divide the resulting Unix millisecond timestamp by <strong>1,000</strong>.</li><li><strong>1505214912061 </strong>/ <strong>1000 </strong>= <strong>1505214912.061</strong> seconds</li></ul><h4><strong>The Result:</strong></h4><p>If you take the integer part — <strong>1505214912</strong>—and paste it into <a href="http://epochconverter.com/"><strong>epochconverter.com</strong></a>, it will output the exact second the account was created:</p><ul><li><strong>GMT:</strong> Tuesday, September 12, 2017 11:15:12 AM</li><li><strong>Relative Time:</strong> September 12, 2017</li></ul><p><strong>Method 3: Python Script</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPBx9i39_2QV_Aj1ezeLMw.png" /></figure><p>You can automate the Snowflake decoding with a simple Python script. No dependencies required.</p><pre>from datetime import datetime, timezone<br><br>snowflake = 123456789012345678<br>timestamp_ms = (snowflake &gt;&gt; 22) + 1420070400000<br>timestamp_s = timestamp_ms / 1000<br>utc_date = datetime.fromtimestamp(timestamp_s, tz=timezone.utc)<br>print(f&quot;Account created: {utc_date.strftime(&#39;%Y-%m-%d %H:%M:%S UTC&#39;)}&quot;)</pre><p>Replace “<strong>123456789012345678” </strong>with the real Discord User ID. The script prints the exact account creation timestamp. This is the permanent temporal anchor for your investigation.</p><h4>Part 4: Finding Connected Accounts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNhrfmdd0Dejq0txehdk1w.png" /></figure><p>Discord allows users to link external accounts to their profile. These are visible to anyone who shares a server with the user, and sometimes to anyone who can view the profile.</p><p><strong>What Can Be Connected</strong>:</p><ul><li>Spotify (shows what the user is listening to)</li><li>Xbox</li><li>Steam</li><li>GitHub</li><li>Twitter (X)</li><li>Reddit</li><li>YouTube</li><li>Twitch</li><li>Battle.net</li><li>League of Legends</li><li>Epic Games</li><li>PayPal (rare)</li></ul><p><strong>How to View Connected Accounts</strong></p><p>Click on the target’s profile in Discord. Look for linked accounts displayed as icons near their username. Click each icon. Discord opens the connected profile.</p><p>A linked Steam account shows their Steam profile URL. A linked GitHub shows their GitHub username. A linked Twitter shows their Twitter handle. Each of these is a direct cross-platform attribution bridge.</p><p>Document every connected account. Cross-reference the handles against other platforms.</p><h4>Part 5: Finding Public Server Invite Links</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Rm1xIsmSGvlhOUH_kKksA.png" /></figure><p>Public Discord servers are accessible via invite links. These links are shared on social media, forums, Reddit, and websites. Google indexes them.</p><p><strong>Google Dorks for Discord Servers</strong></p><pre>site:discord.gg &quot;keyword&quot;<br>site:discord.gg &quot;osint&quot;<br>site:discord.gg &quot;cybersecurity&quot;<br>site:discord.gg &quot;ukraine&quot;<br>site:discord.gg &quot;crypto&quot;</pre><p>Replace <strong>keyword </strong>with the topic or community you are investigating. Each result is an invite link to a public server.</p><p><strong>Find Servers by Username Mentions</strong></p><pre>&quot;username&quot; site:discord.com<br>&quot;username#0000&quot; site:discord.com<br>&quot;@username&quot; site:discord.gg</pre><p>These find forum posts, blog comments, and social media bios where the target listed their Discord username or a server invite link.</p><p><strong>Discord Server Listing Sites</strong></p><p>Several websites index public Discord servers:</p><ul><li><a href="https://disboard.org/"><strong>https://disboard.org</strong></a> — Search by keyword or category. Largest public server directory.</li><li><a href="https://discordservers.com/"><strong>https://discordservers.com</strong></a> — Curated server listings.</li><li><a href="https://top.gg/"><strong>https://top.gg</strong></a> — Server discovery with search.</li></ul><p>Search for keywords, topics, or community names. Each listing includes an invite link.</p><h4>Part 6: Server Reconnaissance — What You Can See</h4><p>Once you join a public server with your sock puppet account, document what is visible.</p><p><strong>Server Information</strong></p><p>Click the server name at the top. You see:</p><ul><li>Server name and description.</li><li>Server rules.</li><li>Member count (online and total).</li><li>Server boost level.</li><li>Creation date (visible in the server settings for some servers).</li></ul><p><strong>Channel Listing</strong></p><p>The left sidebar shows every channel in the server. Channels are organized into categories. Read the channel names and descriptions. They tell you what the community discusses and where sensitive conversations might happen.</p><p><strong>Member List</strong></p><p>The right sidebar shows all members currently online, organized by role. Roles tell you the server hierarchy. Look for:</p><ul><li><strong>Administrators and Moderators</strong>: These users control the server.</li><li><strong>Custom Roles</strong>: Roles with names like “<strong>VIP</strong>,” “<strong>Verified</strong>,” “<strong>Staff</strong>,” or “<strong>Contributor</strong>” reveal the server’s structure.</li><li><strong>Bots</strong>: Servers use bots for moderation, music, and automation. Note the bots present. Some bots log messages or provide lookup functionality you can use.</li></ul><p><strong>Messages</strong></p><p>Scroll through public text channels. Read what people post. Look for:</p><ul><li>Personal details shared casually (<strong>locations, occupations, relationships</strong>).</li><li>Links to external profiles (<strong>Twitter, GitHub, Instagram</strong>).</li><li>Files and images that can be downloaded and analyzed.</li><li>Pinned messages (important announcements or resources).</li></ul><h4>Part 7: Extracting Profile Pictures and Banners</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gYdJUnSNAGZW82TtNBIX7A.png" /></figure><p>Discord profile pictures and server icons are accessible, but right-clicking and copying the image URL no longer works reliably. Discord now loads images dynamically. You need to extract them through the browser’s Developer Tools.</p><p><strong>Extracting a User’s Profile Picture</strong></p><p><strong>Step 1</strong>: Open Discord in your browser at <a href="https://discord.com/"><strong>https://discord.com</strong></a>. Log into your sock puppet account. Navigate to the target user&#39;s profile by clicking their name in a server or friend list.</p><p><strong>Step 2</strong>: Open Developer Tools (<strong>F12 </strong>or <strong>Ctrl + Shift + I</strong>). Click the Network tab.</p><p><strong>Step 3</strong>: In the filter bar, type <strong>avatar </strong>to show only avatar-related requests.</p><p><strong>Step 4</strong>: Refresh the page (<strong>F5</strong>). The Network tab populates with requests.</p><p><strong>Step 5</strong>: Look for requests to URLs containing <strong>cdn.discordapp.com/avatars/</strong>. These are the user&#39;s profile pictures. Discord loads multiple sizes. Find the one ending in <strong>.png</strong> or <strong>.webp</strong> with the largest file size. That is the full-resolution version.</p><p><strong>Step 6</strong>: Click on the request. In the Headers tab, copy the full Request URL. Open it in a new browser tab. Right-click and save the image.</p><p><strong>Alternative: Filter by Image Type</strong></p><p>If filtering by <strong>avatar </strong>returns too many results, switch to the <strong>Img </strong>filter instead. This shows only image files. Scroll through the loaded images. Find the ones from <strong>cdn.discordapp.com/avatars/</strong>. Click and save.</p><p><strong>Extracting a Server Icon</strong></p><p>The process is identical for server icons.</p><p><strong>Step 1</strong>: Navigate to the target server in Discord.</p><p><strong>Step 2</strong>: Open Developer Tools. Go to the Network tab.</p><p><strong>Step 3</strong>: In the filter bar, type <strong>icon </strong>or <strong>cdn.discordapp.com/icons/</strong>.</p><p><strong>Step 4</strong>: Refresh the page. Discord loads the server icon.</p><p>Step 5: Look for requests to URLs containing <strong>cdn.discordapp.com/icons/.</strong> Click the request. Copy the full URL. Open in a new tab. Save the image.</p><p><strong>Alternative: Img Filter</strong></p><p>Switch to the <strong>Img </strong>filter in the Network tab. Every image Discord loaded for that page appears. Find the server icon from the list. Download it.</p><p><strong>What You Do With the Images</strong></p><p>Once saved, run the profile picture or server icon through:</p><ul><li>Google Lens: <a href="https://lens.google.com/"><strong>https://lens.google.com</strong></a></li><li>Yandex Images: <a href="https://yandex.com/images"><strong>https://yandex.com/images</strong></a></li><li>TinEye: <a href="https://tineye.com/"><strong>https://tineye.com</strong></a></li></ul><p>If the same image appears on Twitter, Instagram, GitHub, or a forum, you have a cross-platform attribution bridge. A server icon that matches a website’s logo links the Discord server to that domain.</p><h4>Part 8: Google Dorks for Discord Users and Servers</h4><pre>site:discord.com &quot;username&quot;<br>site:discord.gg &quot;servername&quot;<br>site:disboard.org &quot;keyword&quot;<br>&quot;username#0000&quot;<br>&quot;discord.gg&quot; &quot;keyword&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l-9u7ms2Jg9vObsQdugrrw.png" /></figure><p>Run these across Google, Yandex, and Bing. Find forum posts, social media bios, and public server listings where the target’s Discord presence is mentioned.</p><h4>Part 9: Ethical Boundaries</h4><p>Discord is a semi-private platform. Many servers are invite-only. Some content is behind authentication walls.</p><p><strong>What Is Acceptable</strong>:</p><ul><li>Viewing public server listings and joining public servers.</li><li>Extracting User IDs and profile pictures from public profiles.</li><li>Decoding Snowflake IDs for creation timestamps.</li><li>Viewing linked accounts that the user chose to display publicly.</li><li>Documenting messages in public channels you legitimately joined.</li></ul><p><strong>What Is Not Acceptable</strong>:</p><ul><li>Using compromised accounts to access private servers.</li><li>Attempting to view direct messages.</li><li>Scraping messages at scale from servers without permission.</li><li>Impersonating another user to gain access.</li><li>Using bots to automate data collection in violation of Discord’s Terms of Service.</li></ul><p>If a server requires an invite you were not given, you stop. If a user has set their profile to private, you respect that boundary. Discord’s platform rules prohibit unauthorized scraping. Operate within the terms.</p><h4>Part 10: Practical Investigation Workflow Summary</h4><ol><li>Enable Developer Mode in Discord.</li><li>Copy the target’s User ID from their profile.</li><li>Decode the creation timestamp using <strong>discord.id</strong> or the Snowflake formula.</li><li>Document all connected accounts visible on the profile. Cross-reference each to other platforms.</li><li>Save the profile picture. Run reverse image search.</li><li>Google dork the username and any known server names.</li><li>Search <strong>disboard.org</strong> and <strong>discordservers.com</strong> for servers related to the target&#39;s interests.</li><li>Join relevant public servers with a sock puppet account.</li><li>Document server information, member roles, and visible messages.</li><li>Extract server icons and reverse image search them.</li><li>Cross-reference every username, handle, and connected account across platforms.</li><li>Document everything. Screenshots, User IDs, timestamps, and your analysis.</li></ol><h4>Part 11: Quick Reference</h4><p><strong>Objective______________Method</strong></p><ul><li>Enable Developer Mode: User Settings → Advanced → Developer Mode</li><li>Extract User ID: Profile → three-dot menu → Copy User ID</li><li>Decode creation timestamp:<strong>discord.id</strong> or Snowflake formula</li><li>Find connected accounts: View target profile → linked icons</li><li>Find public servers:<strong>site:discord.gg &quot;keyword&quot;</strong>, <strong>disboard.org</strong></li><li>Extract profile picture: Right-click → Copy Image URL</li><li>Reverse image search: Google Lens, Yandex, TinEye</li><li>Server reconnaissance: Join public server → document channels, roles, messages</li><li>Google dork for Discord:<strong>site:discord.com &quot;username&quot;</strong>, <strong>site:discord.gg &quot;keyword&quot;</strong></li></ul><p>This is Discord OSINT. The platform wants you to think everything is private. It is not. User IDs are permanent. Connected accounts bridge to other platforms. Public servers are open. Invite links are indexed. Extract what is visible, cross-reference everything, and build your attribution from the fragments people leave behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vA8xD9R5yGci0mzAtusGEA.png" /></figure><p>This module shifts your focus from platforms to pivot points. A phone number. A business record. A historical snapshot of a website. A person’s name. These are the raw materials of investigation. You do not always start with a social media handle. Sometimes all you have is a phone number on a leaked receipt, a company name on a job posting, or a person’s name mentioned in a report. This module teaches you how to turn those fragments into full intelligence profiles.</p><h4><strong>Lecture 5.1: Phone Number OSINT</strong></h4><p>A phone number is one of the most valuable starting points in any investigation. It is tied to a physical device. It is linked to messaging apps. It appears in data breaches, public records, and social media databases. If you know how to work a phone number properly, you can extract a name, a location, a profile picture, and a list of connected accounts without ever making a call.</p><p>This lecture walks you through the complete phone number investigation workflow. No theory without practice. Every technique is something you can do right now.</p><p><strong>Part 1: The Number’s Address — Understanding the Numbering Plan</strong></p><p>Before you plug a phone number into any tool, stop. Look at the number itself. A phone number is structured. It contains a country code, an area code or mobile prefix, and a subscriber number. Reading this structure tells you where in the world the number lives before you run a single search.</p><p>Every phone number on the planet follows the <strong>E.164</strong> international numbering plan. The format is:</p><pre>+[Country Code] [National Destination Code] [Subscriber Number]</pre><p>Take this number as an example: <strong>+234 802 345 67**</strong></p><p><strong>Break it down.</strong></p><p>The <strong>+234</strong> is the country code. That is Nigeria. You now know the country. That is your geographic anchor. Everything else you find about this number should be consistent with Nigeria. If a tool tells you the carrier is in Germany, something is wrong.</p><p>The <strong>802</strong> is the mobile prefix. In Nigeria, prefixes like <strong>802</strong>, <strong>803</strong>, <strong>809</strong>, and others are assigned to specific mobile networks. <strong>802 </strong>typically belongs to Airtel Nigeria. You now know the carrier without looking it up.</p><p>The remaining digits are the subscriber number. These are unique to the individual line.</p><p>Now take another example: <strong>+1 212 555 0199</strong></p><p>The <strong>+1</strong> is the country code for the United States, Canada, and several Caribbean nations. That narrows you to North America.</p><p>The <strong>212 </strong>is the area code. That is Manhattan, New York City. You now have a city-level location.</p><p>The <strong>555 </strong>prefix is reserved for fictional numbers in US media. This specific number is a fake. You just identified a dummy number by reading its structure.</p><p>This is the skill. Before tools, use your eyes. The number itself tells a story. Learn the major country codes. Learn the mobile prefixes for the regions you investigate most often. The more you can determine without touching a keyboard, the faster and more accurate your investigation becomes.</p><p><strong>Part 2: Carrier and Line Type Lookup</strong></p><p>Once you have identified the country and general region from the number structure, your next step is to confirm the carrier and determine the line type. Is this a mobile number, a landline, or a VoIP number? The answer changes how you investigate.</p><p><strong>Tool</strong>: <a href="https://freecarrierlookup.com/">FreeCarrierLookup.com</a></p><p>Go to <a href="http://freecarrierlookup.com/"><strong>freecarrierlookup.com</strong></a>. Enter the full phone number with country code. The tool returns:</p><ul><li>The carrier name.</li><li>The line type (mobile, landline, VoIP).</li><li>The original carrier, even if the number has been ported.</li></ul><p>A mobile number is tied to a physical SIM card and a device. This is what you want. A <strong>VoIP number</strong> from a service like<strong> Google Voice</strong> or <strong>TextNow </strong>is essentially <strong>disposable</strong>. It can be created in minutes and abandoned just as fast. Knowing this upfront saves you from spending hours investigating a burner.</p><p><strong>Tool</strong>: <a href="https://phonevalidator.com/">PhoneValidator.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atvJR5Xvok0oq7CGgk4exw.png" /></figure><p><a href="http://phonevalidator.com/"><strong>phonevalidator.com</strong></a> is another free lookup tool. It provides similar carrier and line type data, plus it sometimes returns the city and state associated with the area code. Use it as a second source to confirm what FreeCarrierLookup told you. Never trust a single tool. Always validate.</p><p><strong>Part 3: True People Search and Spydialer — Name Discovery</strong></p><p>Now you want to put a name to the number. In the United States, two free tools dominate this space.</p><p><strong>True People Search</strong></p><p>Go to<a href="http://truepeoplesearch.com/"> <strong>truepeoplesearch.com</strong></a>. Enter the phone number. If the number is in their database, the tool returns:</p><ul><li>First and last name.</li><li>Current and previous addresses.</li><li>Email addresses associated with the number.</li><li>Possible relatives or associates.</li></ul><p>This is aggregated from public records, marketing databases, and consumer data. It is not guaranteed to be accurate, but it is a strong starting point. If you get a name, cross-reference it immediately against social media platforms to confirm the association.</p><p><strong>Spydialer</strong></p><p>Go to <a href="http://spydialer.com/"><strong>spydialer.com</strong></a>. Enter the phone number. Spydialer works differently. It does not pull from consumer databases. It checks the number&#39;s voicemail greeting without actually ringing the phone.</p><p>Here is how it works. Spydialer calls the number, waits for the voicemail system to pick up, and records the greeting. If the voicemail message says “<strong>You have reached John Smith</strong>. <strong>Please leave a message</strong>,” Spydialer captures that audio and transcribes the name. You never spoke to the target. The target’s phone never rang. You just extracted their name from their own voicemail greeting.</p><p>This is passive. It is legal. It works because people voluntarily record their name on their voicemail. Spydialer simply listens to what they chose to make public.</p><p>Use <strong>Spydialer </strong>for US numbers. For international numbers, the tool is less effective because voicemail systems vary by country. But for US targets, it is one of the most reliable name discovery tools available.</p><p><strong>Part 4: Messenger App Querying — The Most Powerful Technique</strong></p><p>This is the technique I told you about at the start. It is simple. It is passive. It works across WhatsApp, Signal, and Telegram. And it produces results faster than any database lookup.</p><p>The concept is straightforward. Messaging apps allow you to see certain information about a user if you have their phone number saved in your contacts. You do not need to message them. You do not need to call them. You just add them and look.</p><p><strong>WhatsApp</strong></p><p>Open WhatsApp on your sock puppet device. Save the target phone number to your device contacts with the full international format (including the <strong>+ </strong>and country code). Give the contact a fake name in your address book. Open WhatsApp. Wait a few seconds for the app to sync. If the number is registered on WhatsApp, the contact appears in your WhatsApp contact list.</p><p><strong>Now, tap on the contact. You will see</strong>:</p><ul><li><strong>Profile Picture</strong>: The image the user set as their WhatsApp avatar. This is often the same photo they use on Instagram, Facebook, or LinkedIn. Save it. Run it through perceptual hash matching.</li><li><strong>Status</strong>: A short text status that may contain location, mood, or activity hints.</li><li><strong>Last Seen</strong>: A timestamp showing when the user last opened WhatsApp. This reveals their active hours.</li><li><strong>About</strong>: A longer bio section. Users often list their job title, location, or other social media handles here.</li></ul><p>You have just extracted a profile picture, an activity timestamp, and biographical information from nothing but a phone number. No message was sent. No notification was triggered. The target has no idea you are looking at them.</p><p><strong>Signal</strong></p><p>The process is identical. Save the number. Open Signal. If the number is registered, the contact appears. Signal shows the profile picture and display name. Signal does not show a “<strong>last seen</strong>” status by default unless the user has enabled it, but the profile picture alone is worth the effort.</p><p><strong>Telegram</strong></p><p>You already know this from the Telegram lecture. Save the number. Open Telegram. If the number is registered, the account appears in your contacts with the display name, username, and profile picture. Now you have the Telegram <strong>@handle</strong>, which you can use for all the Telegram OSINT techniques covered in Lecture 4.8.</p><p><strong>Why This Technique Is So Powerful</strong></p><p>A phone number is private, right? People guard their phone numbers. But they voluntarily link them to messaging apps. And those apps display profile pictures, bios, and activity timestamps to anyone who has the number saved. The target thinks their number is hidden. They do not realize their WhatsApp profile picture is visible to every contact who adds them, including the investigator who just saved their number to a sock puppet device.</p><p>This is not a hack. It is not a bypass. It is the intended functionality of these apps. You are simply using the features as designed. The ethical boundary is clear. You look. You document. You do not message. You do not call. You do not interact.</p><p><strong>Part 5: Phone Number to Social Media Discovery</strong></p><p>A phone number is often used to register accounts on Facebook, Instagram, Twitter, and other platforms. Most platforms allow you to search for contacts by syncing your phone’s address book. This is the reverse of the messenger technique. Instead of checking individual apps, you use the platform’s contact sync feature to find every account linked to that number at once.</p><p><strong>Facebook Contact Sync</strong></p><p>On your sock puppet <strong>Facebook </strong>account, go to <strong>Settings</strong>. Find the “<strong>Find Friends</strong>” or “<strong>Upload Contacts</strong>” option. Upload a contact file containing only the target phone number. Facebook processes the file and returns any account associated with that number. If a match is found, you see the profile name, profile picture, and a link to the account.</p><p>This is more aggressive than the WhatsApp technique because you are uploading data to Facebook. Understand the risk. Use a properly maintained sock puppet. Never use your real account.</p><p><strong>Instagram Contact Sync</strong></p><p>Instagram offers a similar feature. Go to your sock puppet Instagram profile. Navigate to “<strong>Discover People</strong>” or “<strong>Connect Contacts</strong>.” Sync your device contacts, which includes the target number. Instagram shows you any account linked to that number.</p><p><strong>The Workflow</strong></p><ol><li>Save the target number to your sock puppet device.</li><li>Check WhatsApp, Signal, and Telegram for profile pictures and bios.</li><li>Sync contacts on Facebook and Instagram to find linked accounts.</li><li>Document every account found. Cross-reference usernames and profile pictures across platforms.</li><li>Never message. Never call. Never interact.</li></ol><p><strong>Part 6: Phone Number to Email Discovery</strong></p><p><strong>Phone numbers </strong>and <strong>email addresses </strong>are often linked in data breaches, consumer databases, and public records. Several tools allow you to search a phone number and find associated email addresses.</p><p><strong>That’s Them</strong></p><p>Go to <a href="http://thatsthem.com/"><strong>thatsthem.com</strong></a>. Enter the phone number. The tool returns associated names, email addresses, and physical addresses from public records and marketing databases. Free to use with a daily limit.</p><p><strong>FastPeopleSearch</strong></p><p>Go to <a href="http://fastpeoplesearch.com/"><strong>fastpeoplesearch.com</strong></a>. Enter the phone number. The tool returns name, address history, and sometimes associated email addresses. This is another consumer data aggregator. Use it as a second source.</p><p><strong>Sync.me / Truecaller.com</strong></p><p><a href="http://sync.me/"><strong>sync.me</strong></a> / <a href="https://www.truecaller.com/"><strong>truecaller.com</strong></a><strong> </strong>is a caller ID and spam blocking app that also works as a reverse phone lookup. Search the number on their website or through the app. It returns the name and sometimes the profile picture associated with the number from their user-contributed database.</p><p><strong>Email Extraction Workflow</strong></p><ol><li>Run the phone number through <strong>That’s Them</strong>, <strong>FastPeopleSearch</strong>, and <a href="https://sync.me/"><strong>Sync.me</strong></a>, <a href="https://www.truecaller.com/"><strong>truecaller.com</strong></a><strong>.</strong></li><li>Collect any email addresses returned.</li><li>Plug those emails into your Module 3 email intelligence workflow.</li><li>Search the emails on breach databases like HaveIBeenPwned, DeHashed, and IntelX.</li><li>Cross-reference the emails against social media platforms.</li></ol><p>A single phone number can lead to an email address, which leads to a Facebook profile, which leads to a LinkedIn account, which gives you their full employment history. This is the chain. Pull one link, and the rest follows.</p><p><strong>Part 7: International Phone Number Resources</strong></p><p>Not all phone numbers are US-based. Different countries have different lookup tools. Here is a quick reference for major regions.</p><p><strong>Europe</strong></p><ul><li><a href="http://118712.fr/"><strong>118712.fr</strong></a> — France.</li><li><a href="http://dasoertliche.de/"><strong>dasoertliche.de</strong> </a>— Germany.</li><li><a href="http://paginebianche.it/"><strong>paginebianche.it</strong></a> — Italy.</li><li><a href="http://bt.com/"><strong>bt.com</strong></a> — United Kingdom.</li></ul><p><strong>Asia</strong></p><ul><li><a href="http://jpnumber.com/"><strong>jpnumber.com</strong></a> — Japan.</li><li><a href="http://truecaller.com/"><strong>truecaller.com</strong></a> — India (and global, but strongest in India).</li></ul><p><strong>Global</strong></p><ul><li><a href="http://numlookup.com/"><strong>numlookup.com</strong></a> — Free reverse lookup for many countries.</li><li><a href="http://truecaller.com/"><strong>truecaller.com</strong></a> — Global caller ID and spam detection. Requires an account.</li><li><a href="http://sync.me/"><strong>sync.me</strong></a> — Global, user-contributed database.</li></ul><p><strong>Part 8: Practical Investigation Workflow Summary</strong></p><ol><li>Read the number. Identify the country code and area code without any tools.</li><li>Run a carrier and line type lookup using FreeCarrierLookup and PhoneValidator.</li><li>If the number is US-based, search True People Search and Spydialer for a name.</li><li>Save the number to your sock puppet device.</li><li>Check WhatsApp, Signal, and Telegram for profile pictures, bios, and activity timestamps.</li><li>Sync contacts on Facebook and Instagram to find linked accounts.</li><li>Run the number through That’s Them, FastPeopleSearch, and <a href="https://sync.me/">Sync.me</a>, Truecaller for email addresses.</li><li>Plug any discovered emails into your email intelligence workflow.</li><li>Cross-reference every name, username, email, and profile picture across all platforms.</li><li>Document everything. Screenshots, timestamps, tool outputs, and your analysis.</li></ol><p><strong>Part 9: Quick Reference</strong></p><p><strong>Objective______________Tool/Method</strong></p><ul><li>Country and area identification: Manual<strong> E.164 analysis</strong></li><li>Carrier and line<strong>: </strong>type<a href="http://freecarrierlookup.com/"><strong>freecarrierlookup.com</strong></a><strong>, </strong><a href="http://phonevalidator.com/"><strong>phonevalidator.com</strong></a></li><li>Name discovery (US):<a href="http://truepeoplesearch.com/"><strong>truepeoplesearch.com</strong></a>, <a href="http://spydialer.com/"><strong>spydialer.com</strong></a></li><li>Voicemail name extraction:<a href="http://spydialer.com/"><strong>spydialer.com</strong></a></li><li>WhatsApp profile: <strong>Save number</strong> → <strong>check WhatsApp</strong></li><li>Signal profile:<strong> Save number</strong> → <strong>check Signal</strong></li><li>Telegram profile: <strong>Save number</strong> → <strong>check Telegram</strong></li><li>Social media account discovery: <strong>Facebook </strong>and <strong>Instagram </strong>contact sync</li><li>Email discovery:<a href="http://thatsthem.com/"><strong>thatsthem.com</strong></a>, <a href="http://fastpeoplesearch.com/"><strong>fastpeoplesearch.com</strong></a>, <a href="http://sync.me/"><strong>sync.me</strong></a></li><li>International lookups:<a href="http://numlookup.com/"><strong>numlookup.com</strong></a>, <a href="http://truecaller.com/"><strong>truecaller.com</strong></a>, country-specific directories</li></ul><p>This is phone number OSINT. Not just searching a database. Reading the number. Confirming the carrier. Extracting the name from the voicemail they recorded themselves. Pulling their profile picture from the messaging apps they voluntarily linked. Building the chain from a single ten-digit string to a full identity profile.</p><p>Master this, and a phone number stops being a dead end. It becomes one of your most productive starting points.</p><h4><strong>Lecture 5.2: Wayback Machine &amp; The Internet Archive</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T4CQT7WN89u0rWXmrMYs2Q.png" /></figure><p>The internet forgets nothing. It just buries things. Websites change. Pages get deleted. Social media profiles get wiped. Companies remove controversial statements. Executives scrub their bios. Products with embarrassing specifications disappear from official pages. But before any of that happened, the Internet Archive was watching.</p><p>The Wayback Machine at <a href="http://archive.org/"><strong>archive.org</strong></a> has been taking snapshots of the web since 1996. It has captured over 800 billion pages. For an investigator, this is not a history tool. It is a time machine. It lets you visit a website as it existed on any date a snapshot was taken. You can read deleted blog posts. You can find old employee directories. You can recover social media profiles that were deleted years ago. You can compare a page from 2018 to the same page in 2022 and see exactly what changed, what was removed, and what someone tried to hide.</p><p>This lecture is about using the Wayback Machine like a professional. Not just pasting a URL and hoping for the best. Systematic collection, wildcard discovery, change detection, and evidence preservation.</p><p><strong>Part 1: The Basics — Viewing a Single Page</strong></p><p>You have a URL. You want to see what it looked like in the past. The most direct method is the Wayback Machine’s main interface.</p><p>Go to <a href="http://archive.org/web/"><strong>archive.org/web/</strong></a>. Paste the URL into the search bar and press Enter. The Wayback Machine displays a calendar with colored circles. Blue circles mean a successful snapshot exists. Green circles mean a redirect was captured. The darker the circle, the more snapshots exist on that date.</p><p><strong>Click a date</strong>. The page loads exactly as it appeared at that moment. The images, the text, the links. Everything is preserved.</p><p>But this is the surface. You are not here for surface-level browsing.</p><p><strong>Part 2: The Wildcard Operator — Downloading Entire Directories</strong></p><p>This is the technique that separates amateurs from professionals. The Wayback Machine allows you to use the <strong>* </strong>wildcard to download every file in a directory, every snapshot of every file, across all time.</p><p><strong>The format is</strong>:</p><pre>https://web.archive.org/web/*/example.com/staff/*</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YwZ8I_ogAzp1vpCSFkNrQ.png" /></figure><p><strong>Let me break this down.</strong></p><ul><li><strong>https://web.archive.org/web/</strong> is the base URL for the Wayback Machine.</li><li>The first <strong>* </strong>means &quot;every date.&quot; It tells the Wayback Machine to return snapshots from all available dates, not just one.</li><li><strong>example.com/staff/</strong> is the directory you are targeting.</li><li>The second <strong>* </strong>means &quot;every file in that directory.&quot;</li></ul><p>When you open this URL, the Wayback Machine returns a list of every file it ever captured in that directory, sorted by filename. You will see old staff profile pages, deleted bios, removed documents, and anything else that was once publicly accessible in that folder.</p><p>Here is a practical example. Say you are investigating a company called Acme Corp. You want to find old employee profiles. You navigate to:</p><pre>https://web.archive.org/web/*/acmecorp.com/about/team/*</pre><p>The Wayback Machine returns every snapshot of every file in the <strong>/about/team/ </strong>directory. You see entries like:</p><pre>acmecorp.com/about/team/john-doe.html 2018-03-15<br>acmecorp.com/about/team/jane-smith.html 2019-11-02<br>acmecorp.com/about/team/former-executive.html 2017-06-20</pre><p>Click on any of these. The page loads as it existed on that date. You are now reading the bio of an executive who left the company three years ago and whose profile was deleted from the live site. The Wayback Machine kept it.</p><p><strong>Part 3: Targeting Specific File Types</strong></p><p>The wildcard technique becomes surgical when you target specific file extensions. Companies accidentally leave PDFs, Excel spreadsheets, Word documents, and other files in publicly accessible directories. The Wayback Machine captures them.</p><p><strong>To find every PDF ever hosted on a domain</strong>:</p><pre>https://web.archive.org/web/*/example.com/*.pdf</pre><p><strong>To find every Excel spreadsheet in a specific directory</strong>:</p><pre>https://web.archive.org/web/*/example.com/internal/*.xlsx</pre><p><strong>To find every Word document</strong>:</p><pre>https://web.archive.org/web/*/example.com/*.doc</pre><p><strong>To find every CSV file</strong>:</p><pre>https://web.archive.org/web/*/example.com/*.csv</pre><p>I have used this technique to find internal strategy documents, financial spreadsheets, employee directories, and training manuals. Files that were never meant to be public but were placed in directories with no access control. The company removed them years ago. The Wayback Machine did not.</p><p><strong>Part 4: Investigating Social Media Profiles</strong></p><p>Social media profiles change constantly. Bios get updated. Profile pictures get swapped. Posts get deleted. The Wayback Machine captures public social media pages just like any other website. This is how you recover what someone tried to erase.</p><p><strong>Twitter/X Profiles</strong></p><p><strong>Paste the profile URL into the Wayback Machine</strong>:</p><pre>https://web.archive.org/web/*/x.com/username</pre><p><strong>Or the old Twitter domain</strong>:</p><pre>https://web.archive.org/web/*/twitter.com/username</pre><p>The calendar shows every date a snapshot was taken. Click through different dates. You will see old display names, old bios, old profile pictures, and the tweets that were visible on that date. If the target deleted controversial tweets, they may still be visible in older snapshots.</p><p><strong>LinkedIn Profiles</strong></p><p>LinkedIn blocks some Wayback Machine snapshots, but public profiles are often captured:</p><pre>https://web.archive.org/web/*/linkedin.com/in/username</pre><p>If a target removed a previous job from their profile, the old version may still list it. If they changed their headline or summary, the old version shows what they used to claim.</p><p><strong>Instagram Profiles</strong></p><p>Instagram is harder to archive due to its dynamic loading, but public profile pages are sometimes captured:</p><pre>https://web.archive.org/web/*/instagram.com/username</pre><p>Focus on older snapshots. The bio, profile picture, and follower count may be different. These changes tell a story.</p><p><strong>Facebook Profiles</strong></p><p>Facebook actively blocks archival of logged-in pages, but public pages and public profiles occasionally get captured:</p><pre>https://web.archive.org/web/*/facebook.com/username</pre><p>Do not expect full timelines. But bios, profile pictures, and public posts sometimes survive.</p><p><strong>YouTube Channels</strong></p><p><strong>YouTube channel pages are archived regularly</strong>:</p><pre>https://web.archive.org/web/*/youtube.com/@handle</pre><p><strong>Or</strong></p><pre>https://web.archive.org/web/*/youtube.com/channel/UCxxxxxxxxxxxxxxxx</pre><p>Old snapshots show previous channel names, old banner images, and video titles that have since been changed or deleted.</p><p><strong>Part 5: Change Detection — Comparing Pages Side by Side</strong></p><p>This is the technique that turns the Wayback Machine from a history viewer into an investigative tool. You do not just look at one snapshot. You compare two snapshots from different dates and document exactly what changed.</p><h4><strong>Here is the practical workflow</strong></h4><p><strong>Step 1: Identify the Target Page</strong></p><p>Pick a page that is likely to change over time. An executive team page. A product description page. A company’s “<strong>About Us</strong>” page. A privacy policy. A terms of service.</p><p><strong>Step 2: Pick Two Dates</strong></p><p>Choose a date from the past and a more recent date. For example, compare the page as it existed in 2018 to the page as it existed in 2022. The wider the gap, the more changes you are likely to find.</p><p><strong>Step 3: Open Both Snapshots Side by Side</strong></p><p>Open two browser windows. Load the 2018 snapshot in one. Load the 2022 snapshot in the other. Place them next to each other on your screen.</p><p><strong>Step 4: Go Line by Line</strong></p><p><strong>Read both pages. Compare the text. Look for</strong>:</p><ul><li><strong>Removed personnel</strong>. An executive bio that existed in 2018 but is gone in 2022. That person left the company. When did they leave? Why?</li><li><strong>Changed job titles</strong>. A person listed as “<strong>VP of Engineering</strong>” in 2018 is now “<strong>Advisor</strong>” in 2022. They were demoted or moved to a non-operational role. That is intelligence.</li><li><strong>Removed product descriptions</strong>. A product page in 2020 listed specific technical specifications. The 2023 version removed those specs. The company is hiding something about the product’s capabilities.</li><li><strong>Changed contact information</strong>. The 2019 page lists a phone number and email address. The 2022 page lists different ones. Both are now pivot points.</li><li><strong>Deleted statements</strong>. A company’s “Our Values” page in 2021 mentioned a commitment to a specific cause. The 2024 version removed all references. The company quietly changed its public stance.</li></ul><p><strong>Step 5: Document Every Change</strong></p><p>Screenshot both versions. Highlight the differences. Write a brief note explaining what changed and what it implies. This is your evidence package.</p><p><strong>Part 6: The Save Page Now Feature — Preserving Evidence in Real Time</strong></p><p>The Wayback Machine is not just for looking at the past. You can force it to capture a page right now. This is critical for evidence preservation.</p><p>Go to <strong>archive.org/web/</strong>. Look for the &quot;<strong>Save Page Now</strong>&quot; section. Paste the URL you want to capture. Click &quot;Save Page.&quot; The Wayback Machine takes an immediate snapshot and gives you a permanent link to that snapshot.</p><p><strong>Use this when</strong>:</p><ul><li>You find a page that might be deleted soon.</li><li>A target posts something controversial that they are likely to remove.</li><li>You need a timestamped record of a page as it exists at this exact moment.</li><li>You are building an evidence file and need a permanent, verifiable copy of the source.</li></ul><p>The snapshot link is permanent. Even if the original page is deleted, your snapshot remains.</p><p><strong>Part 7: Using the Wayback Machine CDX API for Bulk Discovery</strong></p><p>The browser interface is fine for single pages. For large-scale discovery, you use the CDX API. This is a machine-readable interface that returns a list of all snapshots matching your query.</p><p><strong>The base URL is</strong>:</p><pre>https://web.archive.org/cdx/search/cdx?url=example.com&amp;output=text</pre><p>This returns a plain text list of every snapshot of every page on <strong>example.com</strong>. Each line contains the timestamp, the URL, and the HTTP status code.</p><p><strong>To filter by file type</strong>:</p><pre>https://web.archive.org/cdx/search/cdx?url=example.com&amp;matchType=prefix&amp;filter=mimetype:application/pdf&amp;output=text</pre><p>This returns only PDF files.</p><p><strong>To filter by year:</strong></p><pre>https://web.archive.org/cdx/search/cdx?url=example.com&amp;from=2020&amp;to=2021&amp;output=text</pre><p>This returns only snapshots taken in 2020 and 2021.</p><p><strong>To download the results for analysis</strong>:</p><pre>curl &quot;https://web.archive.org/cdx/search/cdx?url=example.com&amp;output=text&quot; &gt; wayback_results.txt</pre><p>You now have a complete inventory of every page the Wayback Machine ever captured from that domain. Use this to discover directories, files, and pages you would never find through the browser interface.</p><p><strong>Part 8: Investigating Deleted Websites</strong></p><p>Sometimes the entire website is gone. The domain expired. The company shut down. The content was removed. The Wayback Machine may still have it.</p><p>Paste the domain into the Wayback Machine search bar. If snapshots exist, the calendar appears. Browse the site as it existed when it was live.</p><p><strong>To find every page ever captured from a defunct domain, use the wildcard</strong>:</p><pre>https://web.archive.org/web/*/defunctsite.com/*</pre><p>This returns a list of every page, every image, every file the Wayback Machine captured before the site disappeared. You can reconstruct the entire website from these snapshots.</p><p><strong>Part 9: Browser Extensions for Faster Access</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4tZ_-dOIJYU_56A0Sfz6Q.png" /></figure><p><strong>Wayback Machine (Official Extension)</strong></p><p>The Internet Archive provides an official browser extension for Chrome and Firefox. Install it. When you encounter a page that is down or you want to check its history, click the extension icon. It shows you if snapshots exist and lets you load them with one click.</p><p>Chrome: <a href="https://chromewebstore.google.com/detail/wayback-machine/fpnmgdkabkmnadcjpehmlllkndpkmiak"><strong>https://chromewebstore.google.com/detail/wayback-machine/fpnmgdkabkmnadcjpehmlllkndpkmiak</strong></a></p><p>Firefox: <a href="https://addons.mozilla.org/en-US/firefox/addon/wayback-machine_new/"><strong>https://addons.mozilla.org/en-US/firefox/addon/wayback-machine_new/</strong></a></p><p><strong>Go Full Page (Screenshot Capture)</strong></p><p>When preserving evidence from a Wayback Machine snapshot, you need a full-page screenshot. The Go Full Page extension captures the entire scrollable page as a single image.</p><p>Chrome: <a href="https://chromewebstore.google.com/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl"><strong>https://chromewebstore.google.com/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl</strong></a></p><p><strong>Part 10: Practical Investigation Workflow Summary</strong></p><ol><li>Start with a URL. Paste it into <strong>archive.org/web/</strong>.</li><li>Browse the calendar. Identify key dates when significant changes likely occurred.</li><li>Use the wildcard operator to discover hidden directories and files: <strong>*/example.com/staff/*</strong>.</li><li>Target specific file types: <strong>*.pdf, </strong><strong>*.xlsx, </strong><strong>*.doc, </strong><strong>*.csv</strong>.</li><li>For social media profiles, check snapshots across multiple dates to find deleted bios, old profile pictures, and removed posts.</li><li>Perform change detection. Compare two snapshots side by side. Document what was added, removed, or altered.</li><li>Use the CDX API for bulk discovery across entire domains.</li><li>Use “<strong>Save Page Now</strong>” to preserve any page that might disappear.</li><li>Screenshot everything. Save the snapshot URLs. Build your evidence file.</li></ol><p><strong>Part 11: Quick Reference</strong></p><p><strong>Objective_____________Method</strong></p><ul><li>View a single page:<strong>archive.org/web/</strong> → paste URL</li><li>Discover all files in a directory:<strong>*/example.com/directory/*</strong></li><li>Find specific file types:<strong>*/example.com/*.pdf</strong></li><li>Compare pages over time: <strong>Open two snapshots side by side</strong></li><li>Preserve a page now:<strong>archive.org/web/</strong> → Save Page Now</li><li>Bulk snapshot discoveryCDX API: <strong>web.archive.org/cdx/search/cdx?url=...</strong></li><li>Twitter/X profile history:<strong>*/x.com/username</strong></li><li>LinkedIn profile history:<strong>*/linkedin.com/in/username</strong></li><li>YouTube channel history:<strong>*/youtube.com/@handle</strong></li><li>Reconstruct defunct websites:<strong>*/defunctsite.com/*</strong></li><li>Quick access browser extension: <strong>Wayback Machine official extension</strong></li></ul><p>This is the Wayback Machine. Not a history book. An investigative tool. Use the wildcard to discover what was hidden. Compare snapshots to document what was changed. Preserve what is about to disappear. Master this, and you can investigate any website, any social media profile, any online presence across time. The internet remembers. Now you do too.</p><h4><strong>Lecture 5.3: Business Intelligence for the Investigator</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-z7hpbPM6Mh9K0m8w_xBA.png" /></figure><p>Companies hide things. Not always illegally. Sometimes they just structure themselves in ways that make it hard to see who really owns what, who supplies whom, and where the money flows. Your job as an investigator is to cut through that structure and find the truth.</p><p>Business intelligence is not about reading annual reports and nodding along. It is about pulling the right records from the right registries, tracing ownership chains through multiple jurisdictions, and mapping supply networks from raw trade data. When you finish this lecture, you will be able to look at any company and tell a story about who really controls it, who it does business with, and what it might be trying to hide.</p><p><strong>Part 1: Corporate Registries — The Foundation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OOuDccm3aNL0NAn_g19uw.png" /></figure><p>Every legitimate company is registered somewhere. That registration creates a public record. The record contains names, addresses, dates, and ownership structures. Your first task is always the same: find the company’s official registration and pull everything you can.</p><p><strong>UK Companies House</strong></p><p>Companies House is the UK’s corporate registry, and it is one of the most transparent in the world. It is free to use. No account required. The data is deep.</p><p>Go to <a href="http://find-and-update.company-information.service.gov.uk/"><strong>find-and-update.company-information.service.gov.uk</strong></a>. Search for the company by name or registration number. The company profile page gives you:</p><ul><li>Registered office address.</li><li>Company status (active, dissolved, in liquidation).</li><li>Incorporation date.</li><li>Last accounts filed.</li><li>Next accounts due.</li><li>Nature of business (SIC code).</li><li>List of officers (directors and company secretary).</li><li>Persons with Significant Control (PSCs).</li></ul><p>The PSC register is the goldmine. A Person with Significant Control is anyone who owns more than 25% of the company’s shares or voting rights, or who otherwise exercises significant influence. This is UK law. Companies must declare their real owners.</p><p><strong>Click on each PSC. You will see</strong>:</p><ul><li>Full name.</li><li>Date of birth (month and year).</li><li>Nationality.</li><li>Correspondence address.</li><li>Nature of control (ownership of shares, voting rights, etc.).</li></ul><p>This is the real owner. Not a nominee director. Not a shell. The person who ultimately benefits from the company’s existence.</p><p>Now, click on each director. You will see their full name, date of birth (month and year), role, and sometimes a service address. Cross-reference these names against other companies. A director who appears in five different companies, some of which are dissolved, is building a pattern.</p><p>Click the “<strong>Filing History</strong>” tab. This contains every document the company has filed since incorporation. Annual returns. Changes of address. Appointment and resignation of directors. Share allotments. Mortgage charges. These documents tell the story of the company’s evolution. Read them chronologically. You are building a timeline.</p><p><strong>US SEC EDGAR</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VO6rLYukekZ337w-C4DxcA.png" /></figure><p>In the United States, publicly traded companies file with the Securities and Exchange Commission. EDGAR is the database.</p><p>Go to <a href="http://sec.gov/edgar/search"><strong>sec.gov/edgar/search</strong></a>. Search by company name or ticker symbol. The results include:</p><ul><li>10-K (annual report) — Comprehensive overview of the business, risks, and financials.</li><li>10-Q (quarterly report) — Quarterly financial updates.</li><li>8-K (current report) — Material events like acquisitions, bankruptcies, or leadership changes.</li><li>Proxy statements — Executive compensation, board member details, and shareholder voting.</li><li>Insider trading filings (Forms 3, 4, 5) — When executives buy or sell company stock.</li></ul><p>The 10-K is your starting point. It contains a detailed description of the business, its revenue streams, its risk factors, its legal proceedings, its properties, and its subsidiaries. The “Risk Factors” section is particularly valuable. The company is legally required to disclose what could go wrong. Read it. They are telling you their vulnerabilities.</p><p>The<strong> proxy statement</strong> lists the <strong>board of directors</strong>, their <strong>backgrounds</strong>, their <strong>compensation</strong>, and their <strong>relationships </strong>with the company. This is how you map the power structure.</p><p><strong>Insider trading filings</strong> tell you whether executives are buying or selling. A CEO selling a large block of shares before bad news becomes public is a signal. The filings are public. Connect the dates.</p><p><strong>OpenCorporates</strong></p><p>OpenCorporates at <a href="http://opencorporates.com/"><strong>opencorporates.com</strong></a> is a global aggregator. It pulls data from over 140 jurisdictions into one searchable database.</p><p><strong>Search by company name, officer name, or address. The results show</strong>:</p><ul><li>Company name and registration number.</li><li>Jurisdiction.</li><li>Current status.</li><li>Directors and officers.</li><li>Sometimes the ultimate beneficial owners.</li></ul><p>The real power of OpenCorporates is the address search. Enter an address, and it returns every company registered at that location. If you find fifty companies registered at the same small office in Delaware, you have found a corporate service provider that creates shell companies. That is a lead.</p><p>The <strong>officer search</strong> is equally powerful. <strong>Enter a name</strong>, and OpenCorporates returns <strong>every company </strong>that <strong>person </strong>is <strong>associated </strong>with <strong>across all jurisdictions</strong>. A single director search can reveal a hidden network of connected entities.</p><p><strong>Part 2: Tracing Beneficial Ownership Through Layers</strong></p><p>Companies hide ownership by layering. <strong>Company A </strong>is <strong>owned </strong>by <strong>Company B</strong>, which is <strong>owned </strong>by <strong>Company C</strong>, which is owned by a<strong> trust in a jurisdiction</strong> that does not require <strong>public disclosure</strong>. Your job is to follow the chain as far as it goes and identify where it goes dark.</p><p>Start with the company you are investigating. Pull its registration. Identify the declared owners. If the owner is another company, pull that company’s registration. Repeat. Each layer takes you deeper.</p><p><strong>Here is the practical workflow.</strong></p><ol><li>Pull the target company’s registration from its home jurisdiction.</li><li>Identify the shareholders or PSCs.</li><li>If a shareholder is another company, search that company in its home jurisdiction.</li><li>Repeat until you reach either a natural person or a jurisdiction that does not disclose ownership (like Panama, British Virgin Islands, or Cayman Islands).</li><li>When the chain goes dark, document the last known entity and the jurisdiction where the trail ends. This is your transparency boundary. The fact that ownership disappears into a secrecy jurisdiction is intelligence in itself.</li></ol><p><strong>Tools that help with this</strong>:</p><ul><li><strong>OpenCorporates</strong> — Cross-jurisdictional officer and company search.</li><li>ICIJ Offshore Leaks Database — <a href="http://offshoreleaks.icij.org/"><strong>offshoreleaks.icij.org</strong></a> — Data from the Panama Papers, Paradise Papers, and other leaks. Search by name, company, or address.</li><li>OCCRP Aleph — <a href="http://aleph.occrp.org/"><strong>aleph.occrp.org</strong></a> — A search engine for investigative data, including corporate registries, sanctions lists, and leaked records.</li></ul><p><strong>Part 3: Supply Chain Mapping — Who Really Does Business With Whom</strong></p><p>Companies claim to have ethical supply chains. They claim to source from approved vendors. They claim to have no business with sanctioned entities. Import and export records tell you the truth.</p><p>When goods cross international borders, customs agencies record the shipment. The bill of lading contains the shipper, the consignee, the product description, the quantity, the weight, and the date. These records are aggregated by commercial services, and many offer free access to partial data.</p><p><strong>ImportYeti</strong></p><p>Go to <a href="http://importyeti.com/"><strong>importyeti.com</strong></a>. Search for a company name. ImportYeti returns US import records associated with that company, including:</p><ul><li>Supplier names and locations.</li><li>Product descriptions.</li><li>Shipment quantities and weights.</li><li>Port of entry.</li><li>Date of shipment.</li></ul><p>This is how you find a company’s real suppliers. Not the ones they list on their website. The ones they actually buy from. Search a company you are investigating. Look at the supplier list. Cross-reference those suppliers against sanctions lists, blacklists, and adverse media.</p><p><strong>Panjiva (Free Tier)</strong></p><p>Panjiva at <a href="http://panjiva.com/"><strong>panjiva.com</strong></a> is a more detailed trade data platform owned by S&amp;P Global. The free tier allows limited searches. Enter a company name. Panjiva returns shipment records with buyer and seller names, product descriptions, and shipping routes.</p><p><strong>Sayari (Commercial, Free Trial Available)</strong></p><p>Sayari at <a href="http://sayari.com/"><strong>sayari.com</strong></a> is a commercial supply chain intelligence platform. It maps corporate ownership and trade relationships globally. If you have access through your organization, use it. If not, the free trial may be sufficient for a single investigation.</p><p><strong>The Supply Chain Workflow</strong></p><ol><li>Search the target company on ImportYeti.</li><li>Document every supplier and customer listed in the shipment records.</li><li>Search each supplier on OpenCorporates to identify their ownership.</li><li>Cross-reference supplier names against sanctions lists using <a href="http://sanctionssearch.ofac.treas.gov/"><strong>sanctionssearch.ofac.treas.gov</strong></a> (US OFAC) and <a href="http://sanctionsmap.eu/"><strong>sanctionsmap.eu</strong></a> (EU).</li><li>Look for discrepancies. A company that claims to source from ethical suppliers but imports from a blacklisted factory is exposed by the trade data</li></ol><p><strong>Part 4: Beyond Registries — Finding What They Did Not Declare</strong></p><p>Corporate registries show what the company chose to file. Investigations show what they did not. Use the techniques from previous modules to build a fuller picture.</p><p><strong>Wayback Machine</strong></p><p>Paste the company’s website into the Wayback Machine. Look at old versions of the “<strong>About Us</strong>” page, the “<strong>Team</strong>” page, and the “<strong>Products</strong>” page. Find executives who were listed in 2018 but disappeared in 2022. Find products that were once advertised but are now removed. Find contact details that were changed. Every edit is a decision. Every removal is something they did not want you to see.</p><p><strong>Social Media Cross-Referencing</strong></p><p>Take the names of <strong>directors </strong>and <strong>PSCs</strong>. Search them on <strong>LinkedIn</strong>, <strong>Twitter</strong>, <strong>Facebook</strong>, and <strong>Instagram</strong>. A <strong>director </strong>who lists “<strong>CEO at XYZ Corp</strong>” on <strong>LinkedIn </strong>but is not listed as a <strong>director </strong>on <strong>Companies House</strong> is a<strong> red flag</strong>. A <strong>PSC </strong>who posts about a<strong> luxury lifestyle </strong>on Instagram while their <strong>company </strong>files for <strong>bankruptcy </strong>is a signal.</p><p><strong>Phone Number and Email OSINT</strong></p><p>Take the phone numbers and email addresses listed on the corporate registry filings. Run them through the techniques from Lecture 5.1. Find the personal accounts linked to those numbers. A corporate phone number that traces back to a personal WhatsApp profile picture tells you more than any filing.</p><p><strong>News and Adverse Media</strong></p><p>Search the company name and director names on Google News. Use the <strong>site:news.google.com</strong> dork. Search for lawsuits, regulatory actions, protests, and scandals. One negative article does not damn a company. Five articles from different sources over three years about the same type of problem is a pattern.</p><p><strong>Part 5: Practical Investigation Workflow Summary</strong></p><ol><li>Search the company on its home jurisdiction’s corporate registry. Pull all filings.</li><li>Identify the directors and Persons with Significant Control.</li><li>Search every director and PSC on OpenCorporates to find all associated companies.</li><li>Trace the ownership chain through multiple jurisdictions until you reach a natural person or a secrecy wall.</li><li>Check the ICIJ Offshore Leaks database and OCCRP Aleph for connections to leaked records.</li><li>Search the company on ImportYeti to map its real suppliers and customers.</li><li>Cross-reference suppliers against OFAC and EU sanctions lists.</li><li>Run the company’s website through the Wayback Machine. Compare old and new versions.</li><li>Search director and PSC names on LinkedIn, Twitter, Facebook, and Instagram.</li><li>Run phone numbers and emails from filings through Phone OSINT and Email OSINT workflows.</li><li>Search for adverse media on Google News.</li><li>Compile a report with a risk rating based on your findings.</li></ol><p><strong>Part 6: Quick Reference</strong></p><p><strong>Objective_____________Tool/Resource</strong></p><ul><li>UK company search:<a href="http://find-and-update.company-information.service.gov.uk/"><strong>find-and-update.company-information.service.gov.uk</strong></a></li><li>US public company filings:<a href="http://sec.gov/edgar/search"><strong>sec.gov/edgar/search</strong></a></li><li>Global company search:<a href="http://opencorporates.com/"><strong>opencorporates.com</strong></a></li><li>Offshore leaks database:<a href="http://offshoreleaks.icij.org/"><strong>offshoreleaks.icij.org</strong></a></li><li>Investigative data search:<a href="http://aleph.occrp.org/"><strong>aleph.occrp.org</strong></a></li><li>US import/export records:<a href="http://importyeti.com/"><strong>importyeti.com</strong></a></li><li>Trade data platform:<a href="http://panjiva.com/"><strong>panjiva.com</strong></a></li><li>OFAC sanctions check:<a href="http://sanctionssearch.ofac.treas.gov/"><strong>sanctionssearch.ofac.treas.gov</strong></a></li><li>EU sanctions check:<a href="http://sanctionsmap.eu/"><strong>sanctionsmap.eu</strong></a></li><li>Website history:<a href="http://archive.org/web/"><strong>archive.org/web/</strong></a></li><li>Adverse media:<a href="http://news.google.com/"><strong>news.google.com</strong></a></li></ul><p>This is business intelligence investigation. Not just reading filings. Tracing ownership. Mapping supply chains. Recovering deleted history. Building a complete picture from fragmented public data. Master this, and you can investigate any company on Earth.</p><h3>Module 6: Website OSINT &amp; Technical Intelligence</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5abC6wTVnANEshlUXmLUFQ.png" /></figure><p>A website is not just pages and text. It is a stack of technology, a history of ownership, a network of subdomains, and often a trail of exposed files and forgotten directories. Investigating a website means peeling back every layer until you understand who built it, how it runs, and what it accidentally left in the open.</p><p>This module is about technical reconnaissance. You will learn to pull domain records, map subdomains, fingerprint the technology behind a site, discover hidden directories, analyze SSL certificates, crawl for hidden content, and extract email addresses at scale. Every lecture is hands-on. Every tool has a purpose.</p><h4>Lecture 6.1: Domain Reconnaissance — WHOIS, DNS, and Registration History</h4><p>Before you touch the website itself, you investigate the domain. The domain tells you who registered it, when, through which service, and what servers handle its traffic. This is foundational intelligence.</p><h4>WHOIS Lookup</h4><p>WHOIS is a protocol that queries domain registration databases. When someone registers a domain, they must provide contact information. That information is stored in the WHOIS record.</p><p><strong>Start with a simple WHOIS lookup. The command line gives you the raw data</strong>:</p><pre>whois example.com</pre><p>This returns the <strong>registrar name</strong>, <strong>registration date</strong>, <strong>expiration date</strong>, <strong>name servers</strong>, and sometimes the <strong>registrant’s name</strong>, <strong>organization</strong>, <strong>email</strong>, <strong>phone number</strong>, and <strong>physical address</strong>.</p><p>Many domains now use privacy protection services that <strong>redact </strong>the <strong>registrant’s personal details</strong>. You will see “<strong>REDACTED FOR PRIVACY</strong>” or the registrar’s own proxy address. Do not stop there. The privacy shield only hides the current record. Historical WHOIS data often predates the privacy implementation or was captured before the owner enabled it.</p><h4>WHOIS History</h4><p>Use <a href="http://whois.domaintools.com/"><strong>whois.domaintools.com</strong></a> or <a href="http://whoisology.com/"><strong>whoisology.com</strong></a> to pull historical WHOIS records. A domain registered in 2010 may have had public contact details for the first five years before the owner learned about privacy protection. The historical record shows you those early details.</p><p>I have found personal email addresses, home addresses, and phone numbers in WHOIS records from 2015 that were redacted by 2018. People change their domains less often than you think. An old email address from a WHOIS record is a permanent pivot point.</p><h4>DNS Records</h4><p>DNS records tell you how the domain is configured. The <strong>dig </strong>command pulls them:</p><pre>dig example.com ANY</pre><h4>Key record types:</h4><ul><li><strong>A Record</strong>: Maps the domain to an IPv4 address. This is the server’s IP.</li><li><strong>AAAA Record</strong>: Maps to an IPv6 address.</li><li><strong>MX Record</strong>: Mail exchange server. Tells you where email for this domain is handled.</li><li><strong>NS Record</strong>: Name server. Tells you which DNS provider manages the domain.</li><li><strong>TXT Record</strong>: Text data. Often contains SPF records (email sending policies), DMARC policies, and sometimes verification tokens that reveal which services the domain uses.</li><li><strong>CNAME Record</strong>: Canonical name. Points one domain to another. Useful for finding related domains.</li></ul><p>The MX record is particularly valuable. If a domain uses Google Workspace for email, the MX record points to Google’s servers. That tells you their login portal is at a standard Google URL. If they use Microsoft 365, it points to Microsoft. If they self-host, the MX record may reveal their internal mail server hostname and IP.</p><h4>Reverse IP Lookup</h4><p>Once you have the server’s IP address from the A record, find every other domain hosted on that same IP. This is a reverse IP lookup.</p><p>Use <a href="http://viewdns.info/reverseip/"><strong>viewdns.info/reverseip/</strong></a> or <a href="http://yougetsignal.com/tools/web-sites-on-web-server/"><strong>yougetsignal.com/tools/web-sites-on-web-server/</strong></a>. Enter the IP address. The tool returns all domains sharing that server.</p><p>If your target domain shares an IP with five other domains, investigate those domains too. They may be related projects, test environments, or personal sites owned by the same individual. One of them may have a less careful configuration and leak information the target domain protects.</p><h4>Practical Workflow</h4><ol><li>Run <a href="http://whois example.com"><strong>whois example.com</strong></a>. Document registrar, dates, and name servers.</li><li>Check historical WHOIS on <a href="http://whois.domaintools.com/"><strong>whois.domaintools.com</strong></a>. Look for unredacted records.</li><li>Run <a href="http://dig example.com ANY"><strong>dig example.com ANY</strong></a>. Document A, MX, NS, and TXT records.</li><li>Run a reverse IP lookup on the A record IP. Investigate all co-hosted domains.</li><li>Cross-reference any discovered emails, names, or phone numbers against other modules.</li></ol><h4>Lecture 6.2: Subdomain Discovery &amp; Enumeration</h4><p>A domain is rarely just a single website. Organizations set up subdomains for different services. <strong>mail.example.com</strong> for email. <strong>dev.example.com</strong> for development. <strong>staging.example.com</strong> for testing. <strong>admin.example.com</strong> for internal tools. Many of these are not meant to be public. Some are exposed anyway.</p><h4>Certificate Transparency Logs</h4><p>When a <strong>TLS</strong>/<strong>SSL</strong> certificate is issued for a domain, the certificate authority logs it in a public transparency database. This database contains every subdomain that has ever had a certificate issued.</p><p>Go to <a href="http://crt.sh/"><strong>crt.sh</strong></a>. Enter the domain name. The site returns every subdomain that has appeared in a certificate. You will see<strong> current subdomains</strong>, <strong>old subdomains </strong>that no longer exist, and internal subdomains the organization never intended to be public.</p><p><strong>Example output for</strong> — <strong>example.com</strong>:</p><pre>example.com<br>www.example.com<br>mail.example.com<br>dev.example.com<br>staging.example.com<br>admin.example.com<br>vpn.example.com</pre><p>Every one of these is a new target for reconnaissance.</p><h4>Subdomain Enumeration Tools</h4><p><strong>Sublist3r</strong> automates subdomain discovery by querying multiple sources including search engines, certificate transparency logs, and DNS databases.</p><p><strong>Install and run</strong>:</p><pre>git clone https://github.com/aboul3la/Sublist3r.git<br><br>cd Sublist3r<br><br>python sublist3r.py -d example.com</pre><p><strong>Amass</strong> is a more advanced tool from OWASP. It maps the entire attack surface of a domain by combining DNS enumeration, certificate transparency, web archives, and active scanning.</p><pre>amass enum -d example.com</pre><p>Amass produces a comprehensive list of subdomains and can output the results in formats suitable for further analysis.</p><p><strong>Subfinder</strong> is a fast, lightweight subdomain discovery tool that focuses on passive sources.</p><pre>subfinder -d example.com</pre><h4>Google Dorks for Subdomain Discovery</h4><p>You can also use Google to find subdomains that have been indexed:</p><pre>site:*.example.com -www</pre><p>This returns all indexed subdomains except the main www site. Combine with keyword filters to find specific services:</p><pre>site:*.example.com inurl:admin<br><br>site:*.example.com inurl:login<br><br>site:*.example.com inurl:dev</pre><h4>Practical Workflow</h4><ol><li>Search the domain on <a href="http://crt.sh/"><strong>crt.sh</strong></a>. Document every subdomain found.</li><li>Run <strong>Sublist3r</strong>, <strong>Amass</strong>, or <strong>Subfinder </strong>for automated discovery.</li><li>Use Google dorks to find indexed subdomains.</li><li>For each discovered subdomain, visit it. Document what service runs there.</li><li>Prioritize <strong>dev</strong>, <strong>staging</strong>, <strong>admin</strong>, and <strong>internal </strong>subdomains. These are most likely to be misconfigured.</li></ol><h4>Lecture 6.3: Technology Stack Fingerprinting</h4><p>Every website is built on a stack of technologies. The web server, the programming language, the content management system, the JavaScript frameworks, the analytics tools, the hosting provider. Identifying this stack tells you what vulnerabilities may exist and how the site is maintained.</p><p><strong>Wappalyzer</strong></p><p>Wappalyzer is a browser extension that fingerprints the technology stack of any website you visit. Install it on your investigation browser. Visit the target site. Click the Wappalyzer icon. It displays:</p><ul><li>Web server (Apache, Nginx, IIS)</li><li>CMS (WordPress, Drupal, Joomla)</li><li>JavaScript frameworks (React, Angular, Vue)</li><li>Analytics (Google Analytics, Hotjar)</li><li>CDN (Cloudflare, Fastly)</li><li>Hosting provide</li></ul><p>This takes five seconds and gives you a complete technical profile.</p><p><strong>BuiltWith</strong></p><p>BuiltWith is a web-based tool that goes deeper than Wappalyzer. Enter a domain. BuiltWith returns the technology stack, technology history (showing when tools were added or removed), and a list of other sites using the same technologies.</p><p>The technology history is the unique value here. You can see that a site switched from WordPress to Shopify in 2022, or that they stopped using a particular analytics tool. Changes in technology stack indicate organizational changes.</p><p><strong>WhatWeb</strong></p><p>WhatWeb is a command-line tool for bulk technology fingerprinting. Install it:</p><pre>git clone https://github.com/urbanadventurer/WhatWeb.git<br><br>cd WhatWeb<br><br>./whatweb example.com</pre><p>The output is a single line of identified technologies. WhatWeb can scan multiple domains in sequence, which is useful when you have a list of subdomains to profile.</p><h4>Practical Workflow</h4><ol><li><strong>Install Wappalyzer</strong>. Visit the target site. Document the technology stack.</li><li>Run the domain through <strong>BuiltWith</strong>. Document the technology history.</li><li>For bulk analysis across subdomains, use <strong>WhatWeb</strong>.</li><li>Cross-reference identified technologies against known vulnerability databases. An outdated WordPress version or an exposed phpMyAdmin instance is a red flag.</li><li><strong>Document everything</strong>. The technology stack tells you how the site is built and maintained. That context informs every other step of your investigation.</li></ol><h4>Lecture 6.4: Directory Enumeration &amp; Exposed Files</h4><p>Web servers sometimes have directory listing enabled. This means you can browse the server’s file structure like a folder on your desktop. Even without directory listing, predictable directory names often exist and can be discovered through brute-force enumeration.</p><p><strong>Manual Directory Discovery</strong></p><p>Start with common paths. Append these to the target domain and see what loads:</p><pre>example.com/robots.txt<br><br>/robots.txt<br>/sitemap.xml<br>/admin/<br>/login/<br>/backup/<br>/uploads/<br>/.git/<br>/.env<br>/wp-admin/<br>/phpmyadmin/<br>/server-status/</pre><p><strong>robots.txt</strong> is especially valuable. It tells search engines what not to crawl. Those disallowed paths are often the most sensitive directories on the site. Read them carefully.</p><p><strong>Gobuster</strong></p><p>Gobuster is a directory and file brute-forcing tool. It takes a wordlist of common directory names and tests each one against the target domain.</p><p><strong>Install</strong>:</p><pre>sudo apt install gobuster</pre><p><strong>Run</strong>:</p><pre>gobuster dir -u https://example.com -w /usr/share/wordlists/dirb/common.txt</pre><p>Gobuster returns every directory that exists on the server, including hidden ones. Common wordlists include <strong>common.txt</strong>, <strong>big.txt</strong>, and specialized lists for specific CMS platforms.</p><p><strong>Dirb</strong></p><p>Dirb is a simpler alternative to Gobuster. It does the same job with less configuration:</p><pre>dirb https://example.com</pre><p><strong>ffuf</strong></p><p>ffuf (Fuzz Faster U Fool) is a high-speed web fuzzer that can enumerate directories, files, parameters, and subdomains.</p><pre>ffuf -u https://example.com/FUZZ -w /usr/share/wordlists/dirb/common.txt</pre><p>The <strong>FUZZ </strong>keyword is replaced by each entry in the wordlist. ffuf is fast and highly configurable.</p><p><strong>Finding Exposed Files</strong></p><p>Use Google dorks to find exposed files that search engines have already indexed:</p><pre>site:example.com filetype:pdf<br><br>site:example.com filetype:xlsx<br><br>site:example.com filetype:sql<br><br>site:example.com filetype:env<br><br>site:example.com filetype:log<br><br>site:example.com filetype:bak</pre><p>These queries find PDF documents, spreadsheets, database backups, environment configuration files, server logs, and backup files that are publicly accessible.</p><h4>Practical Workflow</h4><ol><li>Manually check common paths like <strong>/robots.txt</strong>, <strong>/admin/</strong>, <strong>/.env</strong>, and <strong>/backup/</strong>.</li><li>Run Gobuster or ffuf with a comprehensive wordlist.</li><li>Use Google dorks to find indexed exposed files.</li><li>For any discovered files, download them. Analyze them. A <strong>.env</strong> file may contain database credentials. A <strong>.sql</strong> file may contain an entire database dump. A <strong>.log</strong> file may contain internal IP addresses and server paths.</li><li>Document every exposed resource. These are security failures, and they are intelligence gold.</li></ol><h4>Lecture 6.5: SSL/TLS Certificate Analysis</h4><p>SSL/TLS certificates encrypt traffic between the <strong>user </strong>and the <strong>server</strong>. But the certificates themselves are public. They contain domain names, organization details, and issuance dates. Analyzing certificates reveals related domains and organizational information.</p><p><strong>Viewing a Certificate</strong></p><p>Click the padlock icon in your browser’s address bar. View the certificate details. You will see:</p><ul><li>Issued to (domain name).</li><li>Issued by (certificate authority).</li><li>Validity period.</li><li>Subject Alternative Names (SANs) — other domains covered by the same certificate.</li></ul><p>The SAN list is the most valuable field. A single certificate may cover <strong>example.com</strong>, <strong>www.example.com</strong>, <strong>mail.example.com</strong>, and <strong>internal.example.com</strong>. All of these are now known subdomains.</p><p><strong>crt.sh</strong></p><p>As covered in Lecture 6.2, <strong>crt.sh</strong> searches certificate transparency logs. Enter a domain. The site returns every certificate ever issued for that domain and its subdomains. This is passive and comprehensive.</p><p><strong>SSLScan</strong></p><p>SSLScan tests a server’s SSL/TLS configuration and reports supported protocols, cipher suites, and certificate details.</p><pre>sslscan example.com</pre><p>The output shows whether the server supports outdated protocols like SSLv3 or TLS 1.0, which are vulnerable to known attacks. This is useful for vulnerability assessment, but as an OSINT investigator, you are documenting it as a finding about the organization’s security posture.</p><h4>Practical Workflow</h4><ol><li>View the certificate in your browser. Document the SAN list.</li><li>Search the domain on <strong>crt.sh</strong>. Document all historical certificates and their SANs.</li><li>Run <strong>sslscan</strong> for a technical profile of the server&#39;s SSL configuration.</li><li>Cross-reference any new subdomains discovered through certificate analysis against the other lectures in this module.</li></ol><h4>Lecture 6.7: Automated Email Discovery with EmailCrawl</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsvVDntepixVrWg_BnKzXw.png" /></figure><p>Finding email addresses manually across a website is slow. You can scan the page source of each page, check the contact section, and look through the footer. But on a large site with hundreds of pages, you will miss things. EMAIL-CRAWL automates this.</p><p><strong>What EMAIL-CRAWL Is</strong></p><p>EMAIL-CRAWL is an open-source Python tool that spiders a target domain, crawls every page it finds, and extracts every email address embedded in the HTML. It is designed specifically for OSINT reconnaissance and email intelligence gathering.</p><p>GitHub repository: <a href="https://github.com/techenthusiast167/EMAIL-CRAWL"><strong>https://github.com/techenthusiast167/EMAIL-CRAWL</strong></a></p><p><strong>Installation &amp; Dependencies</strong></p><pre>Step 1: Download the script directly using wget with the &#39;Raw&#39; link<br><br>wget -O EmailCrawl.py https://gist.github.com/techenthusiast167/ed827569e6c464b042bbdd2a53847675<br><br>Step 2: Open the script in nano for verification<br><br>nano EmailCrawl.py<br><br>Step 3: Install the required Python dependencies<br><br>pip3 install requests beautifulsoup4 colorama tldextract tabulate lxml<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKj-W52N_tUMoOuTGFZZdg.png" /></figure><p>EMAIL-CRAWL uses <strong>requests </strong>and <strong>beautifulsoup4 </strong>for HTTP requests and HTML parsing, along with a crawling engine to move through the site. The requirements file handles all dependencies.</p><h4><strong>Basic Usage</strong></h4><p>Run EMAIL-CRAWL against a target domain:</p><pre>python emailcrawl.py example.com</pre><p>EMAIL-CRAWL starts at the homepage, follows every internal link it finds, and extracts any email address from each page. The output is a deduplicated list of every email address discovered across the entire site arranged in tabular format for easy analysis.</p><p><strong>Example output</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_SIUM_HMu1eCbNz5hVdWQ.png" /></figure><p><strong>Controlling the Crawl Depth</strong></p><p>Large sites can take time to crawl fully. You control the scope with two flags:</p><pre>python emailcrawl.py example.com --max-pages 100 --max-depth 2</pre><ul><li><strong>--max-pages 100</strong> limits the crawl to 100 pages maximum. Once the tool hits this number, it stops. This prevents endless crawling on massive sites.</li><li><strong>--max-depth 2</strong> controls how deep the crawler goes. Depth 0 is the starting page. Depth 1 is pages linked from the starting page. Depth 2 is pages linked from those pages.</li></ul><p>For most investigations, a max depth of 2 and a page limit of 100 is sufficient to cover the main sections of a site without getting lost in archives, blog pagination, or infinite loops.</p><h4>Output to File</h4><p>Save the results for your investigation records:</p><pre>python3 EmailCrawl.py https://target-company.com --output ./intel/results.json</pre><p>The <strong>--output</strong> flag specifies the file path where results are saved. In this example, the tool writes all discovered emails to <strong>results.json</strong> inside the <strong>intel </strong>directory. The output is structured JSON, which means you can parse it programmatically, import it into other tools, or read it directly.</p><p>Each entry contains the email address and the page where it was found, giving you full traceability back to the source.</p><h4>What You Do With the Emails</h4><p>Every email address EMAIL-CRAWL extracts becomes a pivot point. Plug each one into your email investigation workflow from Module 3. Run them through Google dorks. Search them on breach databases. Check if they are linked to social media accounts. A single corporate email address can lead to LinkedIn profiles, GitHub accounts, and personal websites.</p><p>If EMAIL-CRAWL finds <strong>john.doe@target.com</strong>, and you already know from LinkedIn that John Doe is the CTO, you have just confirmed his corporate email address. That is a direct contact path and an attribution anchor.</p><h4>Practical Workflow</h4><ol><li>Clone and install EMAIL-CRAWL from GitHub.</li><li>Run it against the target domain with <strong>--max-pages 100</strong> <strong>--max-depth 2.</strong></li><li>Filter for corporate domain emails.</li><li>Plug each email into your email intelligence workflow from Module 3.</li><li>Cross-reference discovered emails against LinkedIn, breach databases, and social media.</li><li>Document the emails, their sources, and any associated intelligence.</li></ol><h4>Full Documentation</h4><p>For complete usage instructions, all available flags, advanced configuration options, and output formats, refer to the official repository documentation:<a href="https://github.com/techenthusiast167/EMAIL-CRAWL"><strong>https://github.com/techenthusiast167/EMAIL-CRAWL</strong></a></p><p>The <strong>README </strong>covers everything from installation to advanced crawling strategies. If you need to customize the crawl behavior beyond what was covered here, the documentation is your first stop.</p><h4>Lecture 6.8: Advanced Document Discovery — Extracting Hidden Files from Target Websites</h4><p>Sometimes the most valuable intelligence on a website is not on the pages. It is in the files the owner forgot about. <strong>Backups</strong>. <strong>Internal PDFs</strong>. <strong>Spreadsheets</strong>. <strong>Configuration files</strong>. <strong>Database dumps</strong>. These files sit in directories with no links pointing to them. You cannot find them by browsing. You find them by thinking like an attacker and using the same techniques security professionals use to map exposed surfaces.</p><p>This lecture covers ethical, passive techniques to discover and extract publicly accessible documents from websites. Everything covered here works on files that are openly available. You are not bypassing authentication. You are not exploiting vulnerabilities. You are finding what was left in the open.</p><h4>Part 1: Common File Types That Leak Intelligence</h4><p>Before you start searching, know what you are looking for. Certain file types are more likely to contain valuable data.</p><p><strong>File Type_____________What It Might Contain</strong></p><ul><li><strong>.pdf </strong>&gt; Internal reports, strategy documents, training manuals, board minutes</li><li><strong>.xlsx</strong> / <strong>.xls</strong>&gt; Financial data, employee lists, project plans, client databases</li><li><strong>.docx</strong> / <strong>.doc</strong>&gt; Contracts, policies, internal memos, executive correspondence</li><li><strong>.csv </strong>&gt; Exported databases, contact lists, transaction records</li><li><strong>.sql </strong>&gt; Database dumps with user data, credentials, and table structures</li><li><strong>.env</strong> &gt; Environment configuration files with API keys and database passwords</li><li><strong>.log</strong>&gt; Server logs with internal IPs, error messages, and user activity</li><li><strong>.bak</strong> / <strong>.backup</strong>&gt; Backup files of websites, databases, or configuration</li><li><strong>.json</strong>&gt; API responses, configuration files, structured data exports</li><li><strong>.xml</strong>&gt; Sitemaps, configuration files, data exports</li><li><strong>.txt</strong>&gt; Notes, credentials, internal documentation</li><li><strong>.pem</strong> / <strong>.key</strong>&gt; Private keys and certificates</li></ul><p>Each of these is a potential intelligence goldmine. Your job is to find them.</p><h4>Part 2: Google Dorking for File Discovery</h4><p>Start passive. Google has already indexed millions of exposed files. Use dorks to find them.</p><p><strong>Find Specific File Types on a Domain</strong></p><pre>site:target.com filetype:pdf<br><br>site:target.com filetype:xlsx<br><br>site:target.com filetype:sql<br><br>site:target.com filetype:env<br><br>site:target.com filetype:log<br><br>site:target.com filetype:bak</pre><p><strong>Find Files with Specific Keywords</strong></p><pre>site:target.com filetype:pdf &quot;confidential&quot;<br><br>site:target.com filetype:xlsx &quot;password&quot;<br><br>site:target.com filetype:sql &quot;CREATE TABLE&quot;<br><br>site:target.com filetype:env &quot;DATABASE_URL&quot;<br><br>site:target.com filetype:docx &quot;internal&quot;</pre><p><strong>Find Backup Files</strong></p><pre>site:target.com inurl:backup<br><br>site:target.com intitle:&quot;index of&quot; &quot;backup&quot;<br><br>site:target.com ext:bak</pre><p><strong>Find Directory Listings with Exposed Files</strong></p><pre>site:target.com intitle:&quot;index of&quot; &quot;parent directory&quot;<br><br>site:target.com intitle:&quot;index of&quot; &quot;.pdf&quot;<br><br>site:target.com intitle:&quot;index of&quot; &quot;.sql&quot;</pre><p>These dorks return files that are publicly accessible. Google found them. You can access them. Download and analyze.</p><p>Keep in mind, what <strong>Google </strong>missed might be present on <strong>Yandex</strong>. Different search engines crawl different parts of the web. Google dominates the Western internet. Yandex indexes more deeply into Eastern European and Russian content. Bing often catches what both miss. Endeavor to run the same dorks across Google, Yandex, and Bing for effective intelligence gathering. A PDF invisible to Google may be the first result on Yandex. Do not leave intelligence on the table because you only searched one engine.</p><h4>Part 3: How to Discover File Paths Before Downloading</h4><p>You cannot download what you cannot find. Before you run any download command, you need to know the file exists and where it lives. Here are the techniques to discover hidden file paths.</p><h4>Method 1: Search Engines (Passive Discovery)</h4><p>The fastest way to find exposed files is to let search engines do the work. Each result is a direct URL to a file already indexed. You did not guess it. The search engine found it for you. Run dorks across Google, Yandex, and Bing. Collect every URL found.</p><h4>Method 2: robots.txt Mining</h4><p>The <strong>robots.txt</strong> file tells search engines what not to crawl. These disallowed paths are often the most sensitive areas of the site. The owner is literally telling you where the good stuff lives.</p><pre>curl -s https://target.com/robots.txt</pre><p><strong>If the output shows</strong>:</p><pre>Disallow: /internal-docs/<br>Disallow: /wp-content/uploads/private/<br>Disallow: /backup/</pre><p>You now have three directory paths to investigate. Every disallowed path is a directory worth probing. The owner does not want these indexed. That means they contain something worth hiding.</p><h4>Method 3: Sitemap.xml Enumeration</h4><p>The sitemap lists every page the owner wants search engines to find. Sometimes it includes files they did not realize were listed.</p><pre>curl -s https://target.com/sitemap.xml | grep -i &quot;.pdf&quot;<br><br>curl -s https://target.com/sitemap.xml | grep -i &quot;.xlsx&quot;<br><br>curl -s https://target.com/sitemap.xml | grep -i &quot;.sql&quot;</pre><p>Any matching URLs are direct file paths. The owner published them. You just extracted them.</p><h4>Method 4: Directory Listing Discovery</h4><p>Some servers leave directory listing enabled. When you visit a directory URL, instead of a web page, you see a list of every file in that folder.</p><p><strong>Find these with Google</strong>:</p><pre>site:target.com intitle:&quot;index of&quot; &quot;parent directory&quot;</pre><p><strong>Or probe common upload directories directly in your browser</strong>:</p><pre>https://target.com/uploads/<br><br>https://target.com/wp-content/uploads/<br><br>https://target.com/files/<br><br>https://target.com/documents/<br><br>https://target.com/backup/<br><br>https://target.com/media/</pre><p>If any of these display a file list instead of a <strong>403 </strong>or <strong>404 </strong>error, you have found an open directory. Every filename in that list is a direct download path.</p><h4>Method 5: Curl Header Probing</h4><p>Once you suspect a file exists, confirm it without downloading.</p><p><strong>You think there might be a backup file at</strong>:</p><pre>https://target.com/backup/database.sql</pre><p><strong>Probe it</strong>:</p><pre>curl -I https://target.com/backup/database.sql</pre><p>If the response is <strong>200 OK</strong>, the file exists. You now have a confirmed path. If the response is <strong>404 Not Found</strong>, it is not there. Move on to the next candidate.</p><h4>Method 6: Wordlist-Based File Discovery</h4><p>This technique lets you probe a website for common files without manually typing each URL. You create a list of filenames, then run a script that checks each one automatically.</p><p><strong>Step 1: Create the Wordlist File</strong></p><p>Open your terminal. Create a new file called <strong>common_files.txt</strong>:</p><pre>nano common_files.txt</pre><p><strong>Paste the following list into the file</strong>:</p><pre>backup.zip<br>database.sql<br>backup.sql<br>dump.sql<br>export.csv<br>report.pdf<br>users.xlsx<br>config.json<br>.env<br>archive.tar.gz<br>old_site.zip<br>internal-report.pdf<br>wp-config.php<br>phpinfo.php<br>adminer.php<br>server-status<br>.git/config<br>.DS_Store</pre><p>Save and exit. In nano, press <strong>Ctrl + X</strong>, then <strong>Y</strong>, then <strong>Enter .</strong></p><h4>Step 2: Write the Bash Loop Script</h4><p>Create a new script file:</p><pre>nano probe_files.sh</pre><p><strong>Paste the following</strong>:</p><pre>#!/bin/bash<br><br><br># Check if a directory URL was provided<br>if [ -z &quot;$1&quot; ]; then<br>    echo &quot;Usage: bash probe_files.sh https://target.com/uploads/&quot;<br>    echo &quot;Make sure the URL ends with a forward slash.&quot;<br>    exit 1<br>fi<br><br>TARGET_DIR=&quot;$1&quot;<br>WORDLIST=&quot;common_files.txt&quot;<br><br># Check if wordlist exists<br>if [ ! -f &quot;$WORDLIST&quot; ]; then<br>    echo &quot;[-] Wordlist file &#39;$WORDLIST&#39; not found.&quot;<br>    echo &quot;Create it with common filenames, one per line.&quot;<br>    exit 1<br>fi<br><br>echo &quot;[*] Probing files in: $TARGET_DIR&quot;<br>echo &quot;[*] Wordlist: $WORDLIST&quot;<br>echo &quot;&quot;<br><br>while read file; do<br>    # Skip empty lines and comments<br>    [[ -z &quot;$file&quot; || &quot;$file&quot; =~ ^# ]] &amp;&amp; continue<br>    <br>    response=$(curl -s -o /dev/null -w &quot;%{http_code}&quot; &quot;${TARGET_DIR}${file}&quot;)<br>    <br>    if [ &quot;$response&quot; = &quot;200&quot; ]; then<br>        echo &quot;[FOUND] ${TARGET_DIR}${file} — Status: $response&quot;<br>    elif [ &quot;$response&quot; = &quot;301&quot; ] || [ &quot;$response&quot; = &quot;302&quot; ]; then<br>        echo &quot;[REDIRECT] ${TARGET_DIR}${file} — Status: $response&quot;<br>    elif [ &quot;$response&quot; = &quot;403&quot; ]; then<br>        echo &quot;[FORBIDDEN] ${TARGET_DIR}${file} — Exists but access denied&quot;<br>    else<br>        echo &quot;[NOT FOUND] ${TARGET_DIR}${file} — Status: $response&quot;<br>    fi<br>done &lt; &quot;$WORDLIST&quot;<br><br>echo &quot;&quot;<br>echo &quot;[*] Probing complete.&quot;<br></pre><p>Save and exit (<strong>Ctrl + X</strong>, <strong>Y</strong>, <strong>Enter</strong>).</p><p><strong>Step 3: Make the Script Executable</strong></p><pre>chmod +x probe_files.sh</pre><p><strong>Step 4: Run the Script</strong></p><pre>bash probe_files.sh https://target.com/uploads/</pre><p>Make sure the URL ends with a forward slash. The script appends each filename from your wordlist to this base URL and checks if it exists.</p><p><strong>Step 5: Read the Output</strong></p><p>The script shows the status of each probed file:</p><pre>[*] Probing files in: https://target.com/uploads/<br>[*] Wordlist: common_files.txt<br><br>[NOT FOUND] https://target.com/uploads/backup.zip - Status: 404<br>[FOUND] https://target.com/uploads/database.sql - Status: 200<br>[NOT FOUND] https://target.com/uploads/backup.sql - Status: 404<br>[NOT FOUND] https://target.com/uploads/dump.sql - Status: 404<br>[FOUND] https://target.com/uploads/export.csv - Status: 200<br>[FOUND] https://target.com/uploads/report.pdf - Status: 200<br>[FORBIDDEN] https://target.com/uploads/.env - Exists but access denied<br>[NOT FOUND] https://target.com/uploads/archive.tar.gz - Status: 404<br>[*] Probing complete.</pre><p>Every [<strong>FOUND</strong>] result is a confirmed file path. You discovered it through methodical probing. Now download it with <strong>curl -O</strong>.</p><p><strong>Step 6: Download the Discovered Files</strong></p><p>For each [<strong>FOUND</strong>] URL, run:</p><pre>curl -O https://target.com/uploads/database.sql<br><br>curl -O https://target.com/uploads/export.csv<br><br>curl -O https://target.com/uploads/report.pdf</pre><p>You now have local copies for analysis.</p><p><strong>Step 7: Customizing Your Wordlist</strong></p><p>Add more filenames to <strong>common_files.txt</strong> based on your target.</p><p><strong>If you are investigating a WordPress site, add WordPress-specific files</strong>:</p><pre>wp-config.php.bak<br>wp-config.php.old<br>wp-content/debug.log</pre><p><strong>If investigating a company, add company-specific guesses</strong>:</p><pre>employee-list.xlsx<br>salary-2024.pdf<br>board-minutes.docx</pre><p>The better your wordlist matches the target, the more files you will discover. Build your wordlists over time. Save them. Reuse them across investigations.</p><h4>Method 7: Wayback Machine Discovery</h4><p>The Wayback Machine archives files, not just pages. If a file was once publicly accessible, it might be archived.</p><p><strong>Search for file paths on the Wayback Machine</strong>:</p><pre>https://web.archive.org/web/*/target.com/uploads/*<br><br>https://web.archive.org/web/*/target.com/*.pdf</pre><p>If a snapshot exists, the Wayback Machine gives you the direct URL the file once lived at. The original file may still be there. Probe it with <strong>curl -I</strong>. If it returns 200, download it.</p><h4>Part 4: Curl for Header and File Probing</h4><p>Curl is a command-line tool that fetches data from URLs. It is more surgical than a browser. You can probe for files, check headers, and download documents without ever clicking a link.</p><p><strong>Check if a File Exists Without Downloading It</strong></p><pre>curl -I https://target.com/backup/database.sql</pre><p>The <strong>-I </strong>flag fetches only the HTTP headers. If the server returns <strong>200 OK</strong>, the file exists. Document it.</p><p><strong>Probe Common Backup and Config Files</strong></p><pre>curl -I https://target.com/.env<br><br>curl -I https://target.com/backup.zip<br><br>curl -I https://target.com/database.sql<br><br>curl -I https://target.com/admin/backup.tar.gz<br><br>curl -I https://target.com/robots.txt<br><br>curl -I https://target.com/sitemap.xml</pre><p>Each <strong>200 OK</strong> response tells you a file exists and is publicly accessible.</p><p><strong>Download a File for Analysis</strong></p><pre>curl -O https://target.com/wp-content/uploads/2023/01/internal-report.pdf</pre><p>The <strong>-O</strong> flag saves the file with its original filename. You can now open it, analyze it, and extract metadata.</p><p><strong>Download and Pipe Directly to Analysis</strong></p><pre>curl -s https://target.com/document.pdf | strings | grep -i &quot;password&quot;</pre><p>This downloads the file, extracts readable strings, and searches for the word “<strong>password</strong>” all in one command. You never save the file. You just extract the intelligence.</p><h4>Part 5: Recursive Download with Wget</h4><p>Wget is a command-line downloader that can mirror entire directory structures. When you find an open directory, Wget downloads everything in it.</p><p><strong>Mirror an Open Directory</strong></p><pre>wget -r -np -R &quot;index.html*&quot; https://target.com/uploads/</pre><p><strong>Breakdown</strong>:</p><ul><li><strong>-r</strong> — Recursive. Follows links within the directory.</li><li><strong>-np</strong> — No parent. Stays within the specified directory.</li><li><strong>-R </strong>&quot;<strong>index.html</strong>*&quot; — Rejects index.html files. You want the documents, not the directory listing page.</li></ul><p>Wget downloads every file in that directory. PDFs, spreadsheets, backups, everything. You now have a local copy for analysis.</p><p><strong>Mirror with a Delay (Polite Scraping)</strong></p><pre>wget -r -np -w 2 --limit-rate=200k https://target.com/uploads/</pre><ul><li><strong>-w 2</strong> — Waits 2 seconds between requests. Polite. Reduces server load.</li><li><strong>--limit-rate=200k</strong> — Limits download speed to 200KB/s. Less aggressive.</li></ul><p>Be polite. You are an investigator, not an attacker. Aggressive downloading can crash the target server and turns your ethical investigation into a denial-of-service attack.</p><p><strong>Download Only Specific File Types</strong></p><pre>wget -r -np -A &quot;*.pdf,*.xlsx,*.docx,*.sql&quot; https://target.com/uploads/</pre><p>The <strong>-A</strong> flag accepts only the specified file types. Everything else is ignored. This is surgical extraction.</p><h4>Part 6: Extracting Metadata from Discovered Documents</h4><p>Once you have downloaded documents, extract their metadata. The same EXIF techniques from Module 2 apply here.</p><p><strong>Extract PDF Metadata</strong></p><pre>exiftool document.pdf</pre><p><strong>Look for</strong>:</p><ul><li>Author name (often a real employee name).</li><li>Software used (reveals internal tools).</li><li>Creation and modification dates.</li><li>Embedded usernames or file paths.</li></ul><p><strong>Extract Office Document Metadata</strong></p><pre>exiftool report.docx</pre><p>Word and Excel documents embed author names, company names, and sometimes internal network paths. A document authored by “<strong>John Doe</strong>” with the company “<strong>Acme Corp</strong>” and the file path <strong>\\internal-server\shared\finance\</strong> tells you who wrote it, where they work, and what their internal network structure looks like.</p><h4>Part 7: Extracting Images from Target Websites for Analysis</h4><p>Images on a website carry intelligence. Employee photos. Office locations. Product prototypes. Event photographs. Screenshots of internal tools. Every image is a potential source of metadata, geolocation data, and visual evidence.</p><p>This section covers how to discover, download, and analyze images from a target website ethically.</p><h4>What Images Can Reveal</h4><p><strong>Image Type___________Potential Intelligence</strong></p><ul><li><strong>Staff photos</strong>: Employee identities, dress code, office environment</li><li><strong>Office photos</strong>: Interior layout, security measures, building location</li><li><strong>Event photos</strong>: Attendees, partnerships, dates and venues</li><li><strong>Product photos</strong>: Unreleased products, manufacturing details, prototypes</li><li><strong>Screenshots</strong>: Internal software, usernames, project names</li><li><strong>Document scans</strong>: Full documents accidentally published as images</li><li><strong>Logo files</strong>: Brand assets, company identity</li><li><strong>Background images</strong>: Office views that can be geolocated</li></ul><h4>Manual Extraction via Page Source</h4><p>Before reaching for automated tools, learn to pull images directly from the page source. This works on any page, requires no tools, and often surfaces images that automated crawlers miss.</p><h4>Step 1: Open the Page Source</h4><p>Navigate to the target page. Right-click anywhere on the background. Select “<strong>View Page Source</strong>.” A new tab opens with the raw HTML.</p><h4>Step 2: Search for Image Files</h4><p>Press <strong>Ctrl + F</strong> to open the search bar. Search for common image extensions one at a time:</p><ul><li><strong>.jpg</strong></li><li><strong>.jpeg</strong></li><li><strong>.png</strong></li><li><strong>.gif</strong></li><li><strong>.svg</strong></li><li><strong>.webp</strong></li><li><strong>.ico</strong></li></ul><p>Each search jumps to a line containing that extension. You will see image URLs embedded in <strong>src</strong>, <strong>data-src</strong>, <strong>srcset</strong>, and <strong>content </strong>attributes.</p><h4>Step 3: Extract the Full URLs</h4><p>When you find a match, copy the full image URL. It will look something like:</p><pre>&lt;img src=&quot;https://target.com/wp-content/uploads/2024/03/team-photo.jpg&quot;&gt;<br><br>&lt;img data-src=&quot;https://target.com/assets/office-interior.png&quot;&gt;<br><br>&lt;meta property=&quot;og:image&quot; content=&quot;https://target.com/images/preview.jpg&quot;&gt;</pre><p>Open the URL in a new browser tab. If the image loads, right-click and save it to your investigation folder.</p><h4>Step 4: Search for Hidden Image Paths</h4><p>Some images are referenced in JavaScript, CSS, or JSON blobs. Search for these patterns:</p><ul><li><strong>background-image</strong></li><li><strong>url(https://medium.com/%3C/strong%3E%3C/li%3E%3Cli%3E%3Cstrong%3Eog:image%3C/strong%3E%3C/li%3E%3Cli%3E%3Cstrong%3Etwitter:image%3C/strong%3E%3C/li%3E%3Cli%3E%3Cstrong%3Efavicon%3C/strong%3E%3C/li%3E%3C/ul%3E%3Cp%3EThese%20often%20point%20to%20images%20not%20visible%20in%20standard%20%3Cstrong%3Eimg%20%3C/strong%3Etags%20but%20still%20publicly%20accessible.%3C/p%3E%3Ch4%3EStep%205:%20Check%20the%20Page%20with%20Inspect%C2%A0Element%3C/h4%3E%3Cp%3ERight-click%20on%20any%20image%20on%20the%20page.%20Select%20%E2%80%9CInspect%E2%80%9D%20or%20%E2%80%9CInspect%20Element.%E2%80%9D%20The%20developer%20tools%20panel%20opens,%20highlighting%20the%20exact%20HTML%20that%20renders%20that%20image.%20Look%20for%20the%20%3Cstrong%3Esrc%20%3C/strong%3Eattribute.%20Copy%20the%20full%20URL.%20This%20method%20catches%20images%20loaded%20dynamically%20by%20JavaScript%20that%20may%20not%20appear%20in%20the%20static%20page%C2%A0source.%3C/p%3E%3Ch4%3EStep%206:%20Bulk%20Download%20from%20Manual%20Extraction%3C/h4%3E%3Cfigure%3E%3Cimg%20alt=%22%22%20src=%22/service/https://cdn-images-1.medium.com/max/1024/1*ClrLHynfaevUR2LJ1cbhbA.png%22%20/%3E%3C/figure%3E%3Cp%3EOnce%20you%20have%20pulled%20image%20URLs%20from%20the%20page%20source,%20you%20do%20not%20need%20to%20open%20each%20one%20individually.%20Feed%20them%20all%20into%20a%20downloader%20at%C2%A0once.%3C/p%3E%3Cp%3EExtract%20all%20image%20URLs%20from%20the%20page%20source%20and%20download%20them%20in%20one%C2%A0command.%3C/p%3E%3Cpre%3Ecurl%20-s%20https://target.com%20|%20grep%20-oP%20&#39;(https?://[^&quot;]*\.(jpg|jpeg|png|gif|svg|webp))&#39; | sort -u | while read url; do curl -O &quot;$url&quot;; done</pre><p><strong>Breakdown</strong>:</p><ul><li><strong>curl -s https://target.com</strong> — Fetches the page source silently.</li><li><strong>grep -oP &#39;(https?://[^&quot;]*\.(jpg|jpeg|png|gif|svg|webp))&#39;</strong> — Extracts every image URL ending in common extensions.</li><li><strong>sort -u</strong> — Removes duplicates.</li><li><strong>while read url; do curl -O &quot;$url&quot;; done</strong> — Downloads each unique image to the current folder.</li></ul><p>This is fast. One command. Every image on the page lands in your working directory.</p><h4>Automated Image Extraction with WebRecon</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPQ0ZTTVQisD1JK1rkE7jw.png" /></figure><p>Manual extraction works for small pages. For comprehensive collection across an entire website, use WebRecon, a purpose-built OSINT image reconnaissance tool.</p><p>GitHub Repository:<strong> </strong><a href="https://github.com/techenthusiast167/WebRecon"><strong>https://github.com/techenthusiast167/WebRecon</strong></a></p><p>WebRecon crawls a target website, extracts every image it finds, and organizes everything into a structured intelligence package. No complex setup. No API keys. Point it at a URL and it handles the rest.</p><h4>What WebRecon Produces</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*07y_PeT5tqA97r3RSjCMxg.png" /></figure><p>When you run WebRecon against a target, it generates a complete output folder containing:</p><p><strong>Output__________Description</strong></p><ul><li><strong>raw/</strong> &gt;Full-resolution original images as they appear on the target site</li><li><strong>thumbnails/</strong>&gt; Smaller thumbnail versions for quick visual browsing</li><li><strong>gallery.html</strong>&gt; An interactive HTML gallery with all images arranged neatly, filterable by filename, and displaying metadata alongside each image</li><li><strong>image_summary.csv</strong>&gt; A spreadsheet containing every image URL, filename, alt text, file type, dimensions, and source page</li><li><strong>metadata.json</strong>&gt;tructured JSON file with all extracted metadata for programmatic analysis or import into other tools</li></ul><h4>How to Use WebRecon</h4><p><strong>Step 1: Direct Download using Wget</strong></p><pre>wget -O WebRecon.py https://gist.githubusercontent.com/techenthusiast167/dfdaff3b49df63a86e7860376288b7d3/raw/64ae31387c8e79cb39a7d0ace8f706a4cc6c06af/webrecon.py</pre><p><strong>Step 2: Install Dependencies</strong></p><pre>pip install requests beautifulsoup4 colorama tabulate tldextract dnspython python-whois pillow networkx pyvis lxml html5lib pysocks urllib3</pre><p><strong>Step 3: Run WebRecon</strong></p><pre>python3 webrecon.py https://target.com</pre><p>WebRecon begins crawling the target site. It discovers images embedded in <strong>img </strong>tags, <strong>srcset </strong>attributes, CSS backgrounds, meta tags, and lazy-loaded elements. All images are downloaded and organized into the output folder.</p><p><strong>Step 4: Open the Gallery</strong></p><p>Navigate to the output folder and open <strong>gallery.html</strong> in your browser. You will see every image displayed with its filename, source URL, alt text, and file type. Use the filter bar to search images by keyword. Click any image to open the full-resolution version.</p><p><strong>Step 5: Analyze the CSV</strong></p><p>Open <strong>image_summary.csv</strong> in any spreadsheet application. Sort by filename, file type, or source page. Identify patterns. All staff photos in one directory. All product images in another. The CSV gives you a bird&#39;s-eye view of every image asset on the target site.</p><p><strong>Step 6: Use the JSON Metadata</strong></p><p>Load <strong>metadata.json</strong> into any analysis tool or script. The structured format allows you to automate further processing. Feed image URLs into reverse image search scripts. Cross-reference filenames against known patterns.</p><h4>Reverse Image Search for Attribution</h4><p>Every image extracted can be traced back to its source or found elsewhere on the internet using reverse image search. This is how you discover if a staff photo appears on LinkedIn, if a product image matches a competitor’s catalog, or if a background photo has been used elsewhere with location tags.</p><p>Take any image from the <strong>raw/</strong> folder or one you manually extracted. Upload it to:</p><ul><li>Google Lens: <a href="https://lens.google.com/"><strong>https://lens.google.com </strong></a>— Best for general search and object identification.</li><li>Yandex Images:<a href="https://yandex.com/images"><strong> </strong></a><a href="https://yandex.com/images"><strong>https://yandex.com/images</strong></a> — Superior for facial matching and Eastern European sources.</li><li>TinEye: <a href="https://tineye.com/"><strong>https://tineye.com</strong></a> — Best for tracking when and where an image first appeared.</li><li>Bing Images: <a href="https://www.bing.com/images"><strong>https://www.bing.com/images</strong></a> — Often catches results missed by Google.</li></ul><p>If the image appears on a LinkedIn profile, you have a name. If it appears on a news article, you have context and a date. If it appears on a different domain, you have a connection between the two sites. Reverse image search turns a photograph into an attribution bridge.</p><h4>Other WebRecon Capabilities</h4><p>WebRecon is a full-spectrum website reconnaissance tool built for OSINT investigators. It handles crawling, email harvesting, social media discovery, image extraction, technology detection, DNS enumeration, document discovery, relationship graphing, and reporting.</p><p>For full documentation, usage examples, and configuration options, refer to the repository:<a href="https://github.com/techenthusiast167/WebRecon"><strong>https://github.com/techenthusiast167/WebRecon</strong></a></p><h4>Part 8: Practical Workflow Summary</h4><p><strong>Phase 1: Passive Discovery</strong></p><ol><li>Google dork the domain. Run <strong>site:target.com filetype:pdf</strong> and all other file type dorks. Repeat every dork on Yandex and Bing. Different engines index different files. Do not leave intelligence on the table.</li><li>Check <strong>robots.txt</strong>. Pull <strong>curl -s https://target.com/robots.txt</strong>. Note every disallowed directory. The owner is telling you where the sensitive files live. Probe each one.</li><li>Pull <strong>sitemap.xml</strong>. Run <strong>curl -s https://target.com/sitemap.xml | grep -i &quot;.pdf&quot;</strong> and repeat for <strong>.xlsx</strong>, <strong>.sql</strong>, <strong>.docx</strong>, and other extensions. Files listed here were published by the owner.</li><li>Check the Wayback Machine. Search <strong>https://web.archive.org/web/*/target.com/*.pdf</strong>. Historical snapshots reveal file paths no longer on the live site.</li></ol><p><strong>Phase 2: Active Probing</strong></p><p>5. Visit common directories in your browser. Try <strong>/uploads/</strong>, <strong>/wp-content/uploads/</strong>, <strong>/files/</strong>, <strong>/documents/</strong>, <strong>/backup/</strong>, <strong>/media/</strong>, <strong>/assets/</strong>. Look for directory listings. If you see a file list instead of a 403 or 404, you found an open directory.</p><p>6. Probe suspected file paths with <strong>curl -I</strong>. Confirm existence without downloading. <strong>200 OK</strong> means the file is there. <strong>404</strong> means move on.</p><p><strong>Phase 3: Download</strong></p><p>7. Mirror open directories with <strong>wget</strong>. Run <strong>wget -r -np -R &quot;index.html*&quot;</strong> to download everything inside. Add <strong>-w 2</strong> to be polite. Add <strong>-A </strong>to filter by file type.</p><p>8. Download discovered files with <strong>curl -O</strong>. For individual confirmed files, pull them directly.</p><p>9. Extract images. Start manual. View the page source and search for <strong>.jpg</strong>, <strong>.png</strong>, <strong>.gif</strong>, <strong>.svg</strong>, <strong>.webp</strong>. Extract key images directly. Use Inspect Element on images that appear on the page but not in the static source. For bulk download, extract all image URLs with <strong>curl -s https://target.com | grep -oP &#39;(https?://[^&quot;]*\</strong>.<strong>(jpg|jpeg|png|gif|svg|webp))&#39; | sort -u &gt; image_urls.txt</strong> and download.</p><p>10. For full coverage, run WebRecon. <a href="http://python3 webrecon.py https://target.com"><strong>python3 webrecon.py https://target.com</strong></a>. Open <strong>gallery.html</strong> for visual browsing. Review <strong>image_summary.csv</strong> for structured data. Use <strong>metadata.json</strong> for programmatic analysis.</p><p><strong>Phase 4: Analysis</strong></p><p>11. Extract metadata from every document. Run <strong>exiftool </strong>on PDFs, Office documents, and images. Pull author names, software versions, creation dates, GPS coordinates, and internal file paths.</p><p>12. Run reverse image search on key images. Use Google Lens, Yandex, TinEye, and Bing. Find where else they appear. Cross-reference with LinkedIn, news articles, and other domains.</p><p>13. Document everything. File names, full URLs, metadata fields, dates of access, and your analysis. If it is not documented, it did not happen.</p><h4>Ethical Reminder</h4><p>Every technique in this lecture targets publicly accessible files. You are not bypassing logins. You are not exploiting vulnerabilities. You are not accessing anything the server does not willingly serve to anyone who asks.</p><p>If a file is protected by authentication, you stop. If a directory returns <strong>403</strong> <strong>Forbidden</strong>, you move on. Aggressive scanning can crash a server. Use delays between requests. Limit your download speed.</p><p>This is reconnaissance, not intrusion. Stay on the right side of that line. Your reputation and your freedom depend on it.</p><h3>Module 7: Advanced Investigative Tradecraft</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qam3dwU-NEm5YVhwBCZpmA.png" /></figure><p>Most OSINT courses stop at tools and techniques. They teach you how to find data. They do not teach you how to think about what you found, how to protect the identity you use to find it, or how to move from one piece of data to the next without getting lost.</p><p>This module fills those gaps. You will learn how to build and maintain sock puppets that survive scrutiny. You will learn structured analytic techniques that force you to challenge your own conclusions. And you will learn how to pivot, the single most important skill in any investigation. Knowing how to move from one data point to the next, in the right order, without chasing noise, is what separates productive investigators from people who just collect bookmarks.</p><h4>Lecture 9.1: Sock Puppet Management &amp; Anti-Suspension Tactics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6_qPSGymeV83LGyXfnWobg.png" /></figure><p><strong>Module 0</strong> taught you to <strong>create a sock puppet</strong>. That was the start. Creation is easy. Maintenance is hard. A sock puppet that gets suspended on day three is worse than no sock puppet at all because you lost the time you invested and potentially exposed your investigation.</p><p>This lecture is about keeping your persona alive, credible, and undetected for the duration of your investigation and beyond.</p><h4>Part 1: Building a Believable Backstory</h4><p>A sock puppet is not a username and a profile picture. It is a person. People have histories. They have interests. They have friends. They have opinions. The more complete your persona, the less likely a platform is to flag it as fake.</p><p><strong>Start with the basics — </strong>Name, location, occupation. Keep these close to reality. If you have never been to Berlin, do not make your persona a Berlin native. You will slip up. A platform may ask for location verification. Someone may message you in German. Keep the persona within your own knowledge base.</p><p><strong>Give the persona a plausible birth year — </strong>Not too young. Platforms flag accounts claiming to be 18 with zero digital history. Not too old. A 65-year-old joining TikTok for the first time is unusual. Aim for 25–40. Old enough to have a history. Young enough to be platform-native.</p><p><strong>Give the persona interests — </strong>Three to five hobbies that align with the investigation’s needs. If you are investigating motorcycle forums, your persona should like motorcycles. If you are investigating corporate fraud, your persona should work in finance or compliance. The interests are your reason for being in the spaces you need to access.</p><p>Write this backstory down. Keep it in a text file inside your investigation VM. You will forget details over time. The file is your memory.</p><h4>Part 2: Aging the Account</h4><p>A brand-new account with zero friends, zero posts, and a profile picture uploaded ten minutes ago is a red flag. Platforms use account age and activity patterns to detect bots and fake profiles. You must age your sock puppet before you use it for any sensitive work.</p><p><strong>Create the account — </strong>Upload a profile picture. Fill out the bio. Add a few interests. Then leave it alone for at least two weeks. Preferably a month. During this time, log in occasionally. Scroll the feed. Like a few posts from public figures or brands. Do not add friends yet. Do not join groups. Do not message anyone. Just exist.</p><p><strong>After the aging period, start building activity slowly — </strong>Post once or twice a week. Nothing controversial. Nothing investigative. Share a news article with a neutral comment. Post a photo of a coffee cup with no location tag. Comment on a public post with something generic and friendly. The goal is to create a normal-looking activity history.</p><p><strong>Add friends gradually — </strong>Five in the first week after aging. Ten the next. Do not add fifty people in one day. That is bot behavior. Accept friend requests from real accounts. Let the network build naturally.</p><h4>Part 3: Anti-Suspension Tactics</h4><p>Platforms suspend accounts that trigger their automated detection systems. You need to know what triggers them.</p><p><strong>IP Consistency</strong></p><p>Your sock puppet lives in a specific location. Its IP address should reflect that. If you created the account while connected through a VPN in Manchester, always log into that account through a Manchester IP. If you switch to a New York IP tomorrow, the platform sees a user who teleported across the Atlantic. That triggers a security check.</p><p>Use a dedicated VPN server for each sock puppet. Document which server belongs to which persona. Never mix them.</p><p><strong>Browser Fingerprint Consistency</strong></p><p>Your browser fingerprint is a combination of your screen resolution, installed fonts, timezone, language settings, browser version, and dozens of other data points. Platforms use this to identify you across sessions.</p><p>If you created the sock puppet in Firefox with a specific set of privacy extensions and a 1920x1080 screen resolution, always use that same configuration for that persona. The Brave browser’s fingerprinting protection helps, but consistency matters more than protection. A consistent fingerprint is a normal fingerprint.</p><p><strong>Activity Patterns</strong></p><p>Real people do not log in at 3 AM every day for exactly twelve minutes, perform the same actions, and log out. They check their phone throughout the day. Sometimes they spend an hour scrolling. Sometimes they check for thirty seconds and close the app. Vary your activity. Log in at different times. Stay logged in for different durations. Do different things.</p><p><strong>Avoiding Platform Triggers</strong></p><p>Do not send friend requests to strangers at high volume. Do not post the same message in multiple groups. Do not use temporary email addresses for account creation. Do not use phone numbers from free SMS verification services. These are all known bot patterns.</p><p>If a platform asks for phone verification, provide it from a real number. Burner phones are an operational expense. Accept it. A $30 prepaid phone saves a sock puppet you spent a month building.</p><h4>Part 4: When to Retire a Sock Puppet</h4><p>No sock puppet lasts forever. Eventually, it will be compromised, suspended, or simply outlive its usefulness. Know when to retire it.</p><p><strong>Signs it is time to retire</strong>:</p><ul><li>The platform has requested identity verification you cannot provide.</li><li>The account has received unusual attention from other users suggesting someone is investigating you back.</li><li>The account has been flagged or restricted by the platform.</li><li>The investigation it was built for is complete and the persona is no longer needed.</li><li>You suspect your canary tokens have been triggered, indicating someone has accessed files or links associated with the puppet.</li></ul><p>When retiring, do not delete the account abruptly. That looks suspicious. Wind it down. Post less. Engage less. Let it go dormant. If you need to return to the same investigative space later, you do not want a trail of deleted accounts connected to your operational IP range.</p><h4>Part 5: Tools for Sock Puppet Management</h4><ul><li><strong>Burner phones</strong>: Prepaid SIM cards from local retailers. Cash purchase. No ID required.</li><li><strong>Dedicated VPN servers</strong>: One per persona. Document the mapping.</li><li><strong>Password manager</strong>: Store credentials inside your investigation VM. Never on your host machine.</li><li><strong>Canary tokens</strong>: Embed these in documents or links associated with your persona. If someone accesses them, you receive an alert. This tells you someone is investigating you.</li><li><strong>This Person Does Not Exist</strong>: <a href="http://thispersondoesnotexist.com/"><strong>thispersondoesnotexist.com</strong></a> generates AI-created faces for profile pictures. Reverse image search returns nothing. The face is not real. It cannot be traced to a real person.</li></ul><h4>Lecture 9.2: Structured Analytic Techniques for OSINT</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z7zVUS4EenbcFYgAs-K4wg.png" /></figure><p>Collecting data is easy. Making sense of it is hard. Structured analytic techniques are frameworks developed by the intelligence community to reduce bias, challenge assumptions, and evaluate evidence systematically. They turn a pile of findings into a defensible conclusion.</p><h4>Part 1: Analysis of Competing Hypotheses (ACH)</h4><p>ACH is a method for evaluating multiple possible explanations against the evidence you have collected. Instead of picking the explanation you like and looking for evidence to support it, ACH forces you to list all possible explanations and test each one against every piece of evidence.</p><h4>Here is the process</h4><p><strong>Step 1: Define the Question</strong></p><p><strong>Be specific — </strong>“Who is behind the anonymous account <strong>@Allen123</strong>?” Not “What is going on with this account?” Precision matters.</p><p><strong>Step 2: List All Possible Hypotheses</strong></p><p><strong>Write down every possible answer</strong> — Do not filter yet. Include options you think are unlikely. Include options you do not want to be true. The goal is to exhaust the possibilities.</p><p><strong>Example</strong>:</p><ul><li><strong>H1</strong>: The account is operated by a lone individual with no affiliation.</li><li><strong>H2</strong>: The account is operated by a competitor conducting corporate espionage.</li><li><strong>H3</strong>: The account is operated by a state-sponsored actor.</li><li><strong>H4</strong>: The account is operated by an insider at the target company.</li><li>H5: The account is a bot or automated persona with no human operator.</li></ul><p><strong>Step 3: List All Evidence</strong></p><p>Write down every piece of evidence you have collected. Only include verified evidence. Not assumptions. Not guesses. Things you can source.</p><p><strong>Example</strong>:</p><ul><li><strong>E1</strong>: Account created March 2025.</li><li><strong>E2</strong>: Posts exclusively during 9 AM–5 PM GMT.</li><li><strong>E3</strong>: Profile picture hashes to a LinkedIn photo of a known competitor employee.</li><li><strong>E4</strong>: Writing style uses British English spelling.</li><li><strong>E5</strong>: Account has never posted from a mobile device (only web client).</li></ul><p><strong>Step 4: Create a Matrix</strong></p><p>Put hypotheses across the top. Put evidence down the side. For each cell, rate whether the evidence is consistent <strong>©</strong>, inconsistent (<strong>I</strong>), or neutral (<strong>N</strong>) with that hypothesis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*2GM6hZ2rjiQpJOXDfsbZ-g.png" /></figure><p><strong>Step 5: Refine and Eliminate</strong></p><p>Look at the matrix. <strong>H2 </strong>(Competitor) has the fewest inconsistencies. <strong>H1 </strong>has an inconsistency on <strong>E3</strong>. <strong>H5 </strong>has an inconsistency on <strong>E2 </strong>(bots do not keep office hours). The evidence points toward <strong>H2</strong>. You do not conclude <strong>H2 </strong>is correct. You conclude <strong>H2 </strong>is the most consistent with the available evidence. That is an important distinction.</p><p><strong>Step 6: Identify Gaps</strong></p><p>What evidence would disprove your leading hypothesis? If <strong>H2 </strong>is correct, you would expect the account to post about competitor products. If it does not, that weakens <strong>H2</strong>. Identify the missing evidence. Go find it.</p><p>ACH does not give you certainty. It gives you clarity about what the evidence actually supports and where your gaps are.</p><h4><strong>Part 2: Key Assumption Check</strong></h4><p>Every investigation rests on assumptions. Some are explicit. Most are not. A Key Assumption Check forces you to list your assumptions and test whether they are valid.</p><p><strong>Step 1: List Your Assumptions</strong></p><p>Write down everything you are assuming about the investigation. Be honest.</p><p><strong>Example</strong>:</p><ul><li>“The target is operating from the country their IP address suggests.”</li><li>“The target’s LinkedIn profile accurately reflects their employment.”</li><li>“The email address found on the website belongs to the target.”</li><li>“The profile picture is actually a photo of the target.”</li><li>“The target is a single individual, not a group.”</li></ul><p><strong>Step 2: Rate Each Assumption</strong></p><p>For each assumption, ask: what evidence supports this? If the answer is “none” or “it seems reasonable,” the assumption is weak.</p><p><strong>Rate them</strong>:</p><ul><li>Solid: Supported by multiple independent sources.</li><li>Plausible: Supported by some evidence but not confirmed.</li><li>Weak: No supporting evidence. Just feels true.</li></ul><p><strong>Step 3: Challenge the Weak Assumptions</strong></p><p>For every weak assumption, ask: what if this is wrong? How would that change my conclusions?</p><p>If you assumed the target is in the UK because their IP says London, but they are actually using a VPN, your entire location assessment is wrong. If you assumed the LinkedIn profile is real but it is a fabricated persona, your attribution falls apart.</p><p><strong>Step 4: Document the Check</strong></p><p>Write down your assumptions, their ratings, and the impact if they are wrong. Include this in your report. It shows the client you have thought critically about your own work. It protects you if an assumption later proves false.</p><h4>Part 3: Cognitive Biases to Guard Against</h4><p>Your brain works against you in investigations. Here are the biases that destroy OSINT work.</p><p><strong>Confirmation Bias</strong>: You look for evidence that supports your initial theory and ignore evidence against it. Counter this by actively searching for disconfirming evidence. If you think the target is in London, search for evidence they are not in London.</p><p><strong>Anchoring Bias</strong>: The first piece of information you receive carries disproportionate weight. A flashy finding early in an investigation can anchor your thinking even if later evidence contradicts it. Counter this by revisiting early conclusions regularly.</p><p><strong>Availability Bias</strong>: You overweight information that is easy to recall. A dramatic news article about a company feels more significant than a dry regulatory filing, even if the filing contains more relevant information. Counter this by weighting evidence based on reliability, not memorability.</p><p><strong>Stereotyping Bias</strong>: You assume patterns based on demographic characteristics. “The target is a young male, so he must be technically skilled.” This is lazy. Counter this by building your profile on evidence, not assumptions.</p><p>Knowing these biases exist does not make you immune. The structured techniques exist because even trained analysts fall for them. Use the frameworks. They protect you from yourself.</p><h4>Part 4: Evidence Evaluation and Confidence Ratings</h4><p>Not all evidence is equal. Rate your evidence by source reliability and information credibility.</p><p><strong>Source Reliability</strong>:</p><ul><li><strong>A</strong>: Reliable — Proven track record. Official records. Verified accounts.</li><li><strong>B</strong>: Usually Reliable — Generally trustworthy. Minor inconsistencies.</li><li><strong>C</strong>: Unreliable — History of inaccuracy. Unverified claims.</li><li><strong>D</strong>: Unknown — New source. No track record.</li></ul><p><strong>Information Credibility</strong>:</p><ul><li><strong>1</strong>: Confirmed — Corroborated by multiple independent sources.</li><li><strong>2</strong>: Probably True — Consistent with other evidence but not independently confirmed.</li><li><strong>3</strong>: Possibly True — Plausible but unconfirmed.</li><li><strong>4</strong>: Doubtful — Inconsistent with other evidence.</li><li><strong>5</strong>: Unlikely — Contradicted by reliable evidence.</li></ul><p>Every finding in your report should carry a rating. “<strong>The target’s date of birth is May 1962</strong>” with a rating of <strong>A1 </strong>(Reliable source, independently confirmed) is solid. “<strong>The target may have ties to a competitor</strong>” with a rating of <strong>D3 </strong>(Unknown source, unconfirmed) is speculation. Label it accordingly.</p><h4>Lecture 9.3: The Art of Pivoting</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C2eFbr-0ktk8pmGoX-1n_w.png" /></figure><p>Pivoting is the core skill of OSINT investigation. You start with one piece of data. An email address. A username. A phone number. From that single point, you move outward. Each new discovery becomes a new starting point. The investigation expands until you have a complete picture.</p><p>Pivoting without a plan leads to chaos. You chase every link. You open fifty tabs. You collect data with no structure. At the end of the day, you have a lot of bookmarks and no conclusions.</p><p>This lecture teaches you to pivot with purpose.</p><p><strong>Part 1: What Is a Pivot Point</strong></p><p>A pivot point is any piece of data that connects to another piece of data. It is the bridge between where you are and where you need to go.</p><p><strong>Common pivot points</strong>:</p><ul><li><strong>Email address</strong> → Links to social media accounts, breach databases, domain registrations.</li><li><strong>Username</strong> → Links to other platforms, forum posts, GitHub repositories.</li><li><strong>Phone number </strong>→ Links to messaging apps, public records, carrier lookups.</li><li><strong>Profile picture</strong> → Links to other accounts via perceptual hash matching.</li><li><strong>Name </strong>→ Links to corporate registries, news articles, court records.</li><li><strong>Domain </strong>→ Links to WHOIS records, subdomains, email servers, IP addresses.</li><li><strong>Physical address</strong> → Links to property records, other residents, nearby businesses.</li></ul><p>Every piece of data you collect is a potential pivot point. Not every pivot point is worth pursuing. Knowing which ones to chase and in what order is the skill.</p><p><strong>Part 2: The Pivot Hierarchy</strong></p><p>When you have multiple pivot points available, pursue them in this order. This hierarchy prioritizes high-value, high-reliability pivots over speculative ones.</p><p><strong>Tier 1: Official Records</strong></p><p>Corporate registries.<strong> </strong>Court filings. Property records. Government databases. These are the most reliable sources available. They carry legal weight. They are rarely falsified. If you have a name, pivot to Companies House or SEC EDGAR first. If you have an address, pivot to property records first. Official records anchor your investigation in verifiable fact.</p><p><strong>Tier 2: Platform Metadata</strong></p><p>User IDs. Account creation dates. Linked accounts. These are platform-assigned and unchangeable. A numeric user ID extracted from Facebook page source is a permanent identifier. An account creation timestamp from GitHub is a temporal anchor. These pivots are technically verifiable and resistant to manipulation.</p><p><strong>Tier 3: Self-Reported Identity Data</strong></p><p>Social media bios. LinkedIn profiles. Personal websites. Forum signatures. These are what the target says about themselves. They may be accurate. They may be aspirational. They may be fabricated. Treat them as leads, not facts. Verify against Tier 1 and Tier 2 before relying on them.</p><p><strong>Tier 4: Third-Party Mentions</strong></p><p>News articles. Blog posts. Other people’s social media posts. These are what others say about the target. They provide context but are subject to the biases and errors of the source. A news article quoting the target is Tier 4. The court filing the article references is Tier 1. Always trace back to the original source.</p><p><strong>Tier 5: Inferred Connections</strong></p><p>Patterns you observe but cannot directly verify. Similar writing styles. Overlapping interests. Timezone correlations. These are analytical leads, not evidence. They guide further investigation. They do not go in your final report as facts.</p><p><strong>Part 3: The Pivot Decision Framework</strong></p><p>When you are at a data point and deciding where to pivot next, ask yourself four questions.</p><p><strong>Question 1</strong>: What question am I trying to answer?</p><p>Every pivot should serve an investigative objective. “I need to confirm the target’s location.” “I need to find a corporate email address.” “I need to link this anonymous account to a real identity.” If a pivot does not help answer a specific question, deprioritize it.</p><p><strong>Question 2</strong>: Is this pivot point reliable?</p><p>A corporate registry filing is reliable. A random forum post claiming the target lives in a specific city is not. Prioritize Tier 1 and Tier 2 pivots before chasing Tier 4 and 5.</p><p><strong>Question 3</strong>: Will this pivot produce new pivot points?</p><p>Some pivots are dead ends. A profile picture that hashes to nothing on other platforms stops there. An email address that appears in zero breach databases stops there. That is fine. Not every pivot produces results. But prioritize pivots likely to open new investigation paths.</p><p><strong>Question 4</strong>: Am I drifting from the objective?</p><p>It is easy to fall down rabbit holes. You start investigating a target’s business partner, who leads to their spouse, who leads to their charity work, and suddenly you are three degrees removed from the original question. Set a timer. Every thirty minutes, ask yourself: am I still investigating the right thing?</p><p><strong>Part 4: Building a Pivot Map</strong></p><p>A pivot map is a visual or written record of every pivot you have made and every pivot still available. It prevents duplication. It shows you where you have been and where you can go next.</p><p><strong>The format is simple. For each entity you discover, record</strong>:</p><ul><li><strong>Entity</strong>: What you found (email address, username, company name).</li><li><strong>Source</strong>: Where you found it (Companies House, Instagram page source, GitHub commit).</li><li><strong>Confidence</strong>: A1 through D5 based on the rating system from Lecture 9.2.</li><li><strong>Pivot Options</strong>: What new paths this entity opens.</li><li><strong>Status</strong>: Pending, In Progress, Completed, Dead End.</li></ul><p><strong>Example</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*-Yar1aaXiwn-hQaofdNPxA.png" /></figure><p>This map keeps your investigation organized. When you hit a dead end, you consult the map and see what other pivots are still pending. You never waste time wondering what to do next.</p><p><strong>Part 5: Knowing When to Stop Pivoting</strong></p><p>Pivoting is addictive. There is always one more link to follow. One more profile to check. One more database to search. The best investigators know when to stop.</p><p><strong>Stop pivoting when</strong>:</p><ul><li>You have answered the investigative question. The client asked for a risk assessment on a potential business partner. You have confirmed their identity, their corporate associations, their adverse media status, and their digital footprint. You have enough. Stop.</li><li>New pivots are producing diminishing returns. Each new branch yields less relevant information. You are learning about the target’s third cousin’s former roommate. This is not intelligence. This is noise.</li><li>You are circling back to already-visited entities. If your pivot map shows you revisiting the same types of sources without new findings, you have exhausted the available open source intelligence.</li><li>The cost of further investigation outweighs the value. Every hour you spend is an hour the client pays for. If two more days of investigation will not change the risk rating, deliver the report.</li></ul><p>You now have the operational tradecraft to sustain investigations over time without burning your persona. You have the analytic frameworks to evaluate what you find and challenge your own conclusions. You have the pivoting methodology to move through an investigation with purpose, not chaos.</p><p>Anyone can learn to run a tool. Anyone can memorize dorks. What you have now is different. You know how to think through an investigation. How to structure your analysis. How to protect yourself while you work. How to move from one data point to the next with discipline.</p><p>These are the skills that separate collectors from analysts. A collector gathers data. An analyst understands what it means. Be the analyst.</p><h3>Module 8: Python for OSINT Automation — Building Your Own Tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xga17MyvjRx57_rPUphZ_g.png" /></figure><p>Every investigator eventually hits the same wall. You have a technique that works, but doing it manually across ten targets or a hundred data points is eating hours you do not have. Automation is the answer. But copying someone else’s script without understanding it makes you dependent. The moment the target platform changes its layout, or the API updates, or your needs shift, the script breaks and you cannot fix it.</p><p>This section is not about giving you five scripts to copy. It is about teaching you how to build your own. You will learn a repeatable process for turning any manual OSINT task into a working Python tool. You will use AI as your coding assistant. You will use Kali Linux as your development environment. By the end, you will not need anyone else’s scripts. You will write your own.</p><h4>The Automation Development Framework</h4><p>Every automation project follows the same five phases. Learn this framework, and you can apply it to any task you encounter.</p><p><strong>Phase 1: Define the Manual Process</strong></p><p>Before you write a single line of code, you must understand exactly what you do manually. Write it down step by step. Be specific. “I go to this URL. I type this query. I look for this element on the page. I copy this data. I paste it here.” If you cannot describe the manual process precisely, you cannot automate it.</p><p><strong>Phase 2: Identify the Data Flow</strong></p><p>Where does the data come from? Where does it go? What format is it in at each stage? The input might be a username from a text file. The output might be a CSV of profile URLs. The transformation happens in between. Map this flow before you code.</p><p><strong>Phase 3: Select Your Tools</strong></p><p>For OSINT automation on Kali Linux, your core toolkit is:</p><ul><li><strong>Python 3</strong> — The language. It is installed by default on Kali. It has libraries for HTTP requests, HTML parsing, JSON handling, and file operations.</li><li><strong>Requests </strong>— For making HTTP requests to websites and APIs.</li><li><strong>BeautifulSoup </strong>— For parsing HTML and extracting specific elements.</li><li><strong>aiohttp </strong>— For making many requests simultaneously when speed matters.</li><li><strong>Subprocess </strong>— For calling external tools like ExifTool from within Python.</li><li><strong>JSON/CSV modules</strong> — For structured data input and output.</li></ul><p><strong>Phase 4: Build with AI Assistance</strong></p><p>You do not need to memorize syntax. You need to know how to ask the right questions. <strong>Modern AI coding assistants</strong> can generate boilerplate, suggest libraries, and debug errors. But they only produce good output when you give them good input.</p><h4>The key is providing context. Do not ask “write me a script.” Ask:</h4><ul><li>“I need a Python script that sends a GET request to a URL, parses the HTML with BeautifulSoup, and extracts all links with the class ‘result-link’. Show me the code with error handling.”</li><li>“This function returns a list of URLs. I need to check each URL to see if it returns a 200 or 404 status code. Make it async with aiohttp for speed. Handle timeouts.”</li><li>“I have a JSON file with this structure. Show me how to extract the ‘email’ field from every object and write them to a CSV.”</li></ul><p>The AI becomes your pair programmer. You provide the logic and the requirements. It provides the syntax. You review, test, and refine.</p><p><strong>Phase 5: Test, Break, Fix, Repeat</strong></p><p>Your first version will break. This is normal. Run it against a known target. See where it fails. Is the HTTP request timing out? Add a longer timeout. Is the HTML structure different than expected? Inspect the page again. Is the site blocking your requests? Add proper User-Agent headers. Each failure teaches you something about how the target platform works. Debugging is intelligence gathering.</p><h4>The Kali Linux Advantage</h4><p>Kali Linux is built for security work. It comes with Python pre-installed. It comes with network tools, proxy support, and a terminal environment designed for technical work. For OSINT automation development, Kali gives you:</p><ul><li><strong>Python 3 out of the box</strong>. No setup required. Open a terminal and start coding.</li><li><strong>Virtual environment support</strong>. Create isolated Python environments for each project so dependencies do not conflict.</li><li><strong>Proxy integration</strong>. Route your script’s traffic through Tor or a VPN with simple terminal commands.</li><li><strong>Cron scheduler</strong>. Schedule your finished scripts to run automatically at set intervals.</li></ul><h4>Your development workflow on Kali:</h4><pre>mkdir osint_project<br><br>cd osint_project<br><br>python3 -m venv venv<br><br>source venv/bin/activate<br><br>pip install requests beautifulsoup4 aiohttp<br><br>nano my_tool.py<br><br>python3 my_tool.py</pre><p>That is it. Five commands, and you have an isolated development environment ready for any automation project.</p><h4><strong>Scripting Lab 1: Multi-Engine Dork Orchestrator</strong></h4><p><strong>The Manual Process</strong></p><p>You have a Google dork. You type it into Google. You scroll through results. You copy the links. You type the same dork into Bing. You scroll. You copy. You type it into DuckDuckGo. You scroll. You copy. Then you combine all three lists, remove duplicates, and save the final list. This takes fifteen minutes per dork.</p><p><strong>Building the Tool — Step by Step</strong></p><p>Start by writing the manual process as pseudocode:</p><pre>1. Take a dork query as input<br>2. Send query to Google<br>3. Extract all result links from Google&#39;s response<br>4. Send query to Bing<br>5. Extract all result links from Bing&#39;s response<br>6. Send query to DuckDuckGo<br>7. Extract all result links from DuckDuckGo&#39;s response<br>8. Combine all links<br>9. Remove duplicates<br>10. Save to file</pre><p>Now you have a <strong>blueprint</strong>. Each step becomes a function or a block of logic.</p><p>Ask your AI assistant: “<strong>I need a Python function that takes a search query, sends it to Google via HTTP GET, parses the HTML with BeautifulSoup, and returns a list of result URLs. Include a proper User-Agent header</strong>.”</p><p>It gives you the Google function. You test it. It works for some results but misses others. You inspect Google’s actual HTML and realize the class names vary. You update the parsing logic. You repeat this process for Bing and DuckDuckGo.</p><p>The orchestration function combines the results, uses Python’s <strong>set()</strong> to deduplicate, and writes the output file. You now have a working tool.</p><p><strong>Testing and Refinement</strong></p><p>Run it with a simple dork: <strong>site:example.com</strong>. Compare the results against a manual search. Are you getting the same links? If not, inspect the HTML of the search results page. The class names or element structures may have changed. Update the parsing logic. This is the reality of web scraping. Sites change. Your tools must adapt.</p><p><strong>Add error handling</strong>. What if the request times out? What if the site blocks you? Wrap each request in a try-except block. Log errors instead of crashing.</p><h4>Scripting Lab 2: Bulk EXIF Extractor &amp; Geolocation Plotter</h4><p><strong>The Manual Process</strong></p><p>You have a folder of images. You open each one in ExifTool. You copy the GPS coordinates. You paste them into Google Maps. You note the device model and timestamp. You do this for every image. After processing fifty images, you have a scattered collection of notes and no clear picture of the target’s movements.</p><h4><strong>Building the Tool — Step by Step</strong></h4><p>The pseudocode:</p><pre>1. Walk through a directory and find all image files<br>2. Run ExifTool on each image in JSON mode<br>3. Extract GPS coordinates, timestamp, device make, model, serial number<br>4. Convert GPS from degrees-minutes-seconds to decimal<br>5. Write all data to a CSV file<br>6. Generate an HTML map with pins at every GPS location</pre><p>The key decision is how to call ExifTool. Python’s <strong>subprocess </strong>module lets you run terminal commands and capture the output. You call <strong>exiftool -json image.jpg</strong> and parse the JSON response.</p><p>Ask your AI assistant: “<strong>Show me how to use Python’s subprocess module to run ExifTool with the -json flag on an image file, capture the output, and parse it into a Python dictionary</strong>.”</p><p><strong>GPS conversion is the trickiest part</strong>. ExifTool returns GPS as strings like “40 deg 45&#39; 30.00” N”. You need to parse this and convert it to decimal degrees. Write this logic once, test it with known coordinates, and reuse it.</p><p>The map generation uses <strong>Leaflet.js</strong>, a JavaScript library for interactive maps. Your Python script generates the HTML file with JavaScript embedded. This is a clean approach. No external dependencies for mapping. Just a single HTML file that opens in any browser.</p><p><strong>Testing and Refinement</strong></p><p>Test with images that have known GPS coordinates. Verify the pins appear in the correct locations on the map. Test with images that have no GPS data. The script should handle these gracefully, skipping map pins but still recording metadata in the CSV.</p><h4>Scripting Lab 3: Intelligent Permutation &amp; Availability Engine</h4><p><strong>The Manual Process</strong></p><p>You have a username. You guess variations. You type each variation into Twitter’s URL bar. You check if the profile loads. You repeat for Instagram, GitHub, Reddit, and a dozen other platforms. Each check takes thirty seconds. Checking fifty permutations across ten platforms is 500 manual checks. You will miss things.</p><h4>Building the Tool — Step by Step</h4><p>The pseudocode:</p><pre>1. Take a username as input<br>2. Generate permutations using substitution rules, separator changes, and suffix additions<br>3. For each permutation, check against a list of platform profile URLs<br>4. A 200 status code means the profile exists<br>5. A 404 means it does not<br>6. Collect and report only the hits</pre><p><strong>The permutation logic is the intelligence</strong>. You are encoding the patterns you already know from Module 3. Character substitution: o becomes 0, e becomes 3. Separator variation: underscores become periods become hyphens. Suffix addition: appending 123, 2024, official, real.</p><p>Ask your AI assistant: “I need a Python function that takes a username string and generates permutations using character substitution, separator variation, and common suffix addition. Return a deduplicated list.”</p><p>The profile checking must be fast. Checking 500 combinations sequentially takes minutes. Async with <strong>aiohttp</strong> drops this to seconds. Ask: &quot;<strong>Show me how to use aiohttp to asynchronously check 100 URLs and return the status code for each. Handle timeouts and errors</strong>.&quot;</p><h4>Testing and Refinement</h4><p>Start with a known username. Run the script. Do the hits match platforms where you know the account exists? Are there false positives? Some sites return 200 for nonexistent profiles because they show a “page not found” message with a 200 status code instead of a proper 404. You must handle this by checking the page content, not just the status code. Look for “not found” text in the response body.</p><p>This is real-world scraping. The status code is a starting point, not the final answer. Validate with content checks.</p><h4>Scripting Lab 4: Username-to-User ID Cross-Reference Tool</h4><p><strong>The Manual Process</strong></p><p>You have a list of Twitter usernames. For each one, you view the page source, search for <strong>id_str</strong>, and copy the numeric ID. You do the same for Facebook, searching for <strong>profile_id</strong> or <strong>userID</strong>. Each username takes two minutes. A list of 50 usernames takes nearly two hours of repetitive work.</p><h4>Building the Tool — Step by Step</h4><p>The pseudocode:</p><pre>1. Read usernames from a text file<br>2. For each username, request the public profile page on Twitter<br>3. Search the HTML for the id_str pattern using regex<br>4. Request the public profile page on Facebook<br>5. Search the HTML for profile_id, userID, or entity_id patterns<br>6. Write results to a CSV</pre><p><strong>The core technique is regular expressions</strong>. You are searching raw HTML for specific patterns. Twitter embeds the user ID in a JSON block within the page. The pattern is &quot;<strong>id_str&quot;:&quot;123456789</strong>&quot;. Facebook uses multiple patterns depending on how the page loads.</p><p>Ask your AI assistant: “<strong>I need a Python function that takes HTML source text and uses regex to extract the value of id_str from a JSON-like structure. Show me the regex and error handling</strong>.”</p><h4><strong>Testing and Refinement</strong></h4><p>Test with known accounts where you have manually verified the numeric IDs. Does the script return the correct values? Test with accounts that have custom URLs versus default numeric URLs. Test with accounts that are private versus public. Each variation may require a different extraction approach.</p><p>Facebook is particularly challenging because it changes its page structure frequently. Your regex patterns that work today may break next month. This is why you build the tool yourself instead of relying on someone else’s unmaintained script. When it breaks, you know how to fix it.</p><h4>Scripting Lab 5: Reddit Historical Monitoring Bot</h4><p><strong>The Manual Process</strong></p><p>You check a Reddit user’s profile every day. You scroll through their recent comments. You try to remember what you have already seen and what is new. You copy interesting posts into your notes. You wonder if they deleted anything since your last check. This is unreliable and time-consuming.</p><h4>Building the Tool — Step by Step</h4><p>The pseudocode:</p><pre>1. Take a Reddit username as input<br>2. Request the user&#39;s comment JSON feed from Reddit&#39;s public API<br>3. Compare returned comment IDs against a local storage file of previously seen IDs<br>4. New comments are appended to an activity log<br>5. The storage file is updated with the latest comment IDs<br>6. Schedule the script to run daily</pre><p>Reddit provides a public JSON API at <a href="https://medium.com/reddit.com/user/username/comments.json"><strong>reddit.com/user/username/comments.json</strong></a>. No authentication required. No API key. Just add <strong>.json</strong> to the end of the user profile URL. This returns structured data with comment IDs, timestamps, subreddits, and content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YRv8UUHf8KMSjpjeoFMktQ.png" /></figure><p>Ask your AI assistant: “<strong>Show me how to request JSON data from Reddit’s public API using Python requests, parse the nested structure to extract comment ID, subreddit, body, and timestamp, and handle the case where the user has no comments</strong>.”</p><p>The state tracking is what makes this a monitoring tool instead of a one-time scraper. You store seen comment IDs in a local JSON file. Each run compares new IDs against stored IDs. Only unseen comments are reported.</p><h4>Testing and Refinement</h4><p>Run the script twice on the same user without any new activity between runs. The second run should report zero new comments. Have the user post a new comment. Run the script again. It should detect exactly one new comment. Verify the timestamp and content are correct.</p><p><strong>Schedule it with cron on Kali Linux</strong>:</p><pre>0 8 * * * /home/user/osint_project/venv/bin/python3 /home/user/osint_project/reddit_monitor.py</pre><p>This runs the script every day at 8 AM. You wake up to a fresh activity report.</p><h4>Building Your Own Automation Toolkit</h4><p>The five labs above are templates. The real skill is applying this development framework to any task you encounter.</p><p>When you find yourself doing something manually, stop. Write down the manual process. Convert it to pseudocode. Identify the data sources and outputs. Ask your AI assistant for help with specific functions. Test against known targets. Refine until it works reliably. Save the tool. You now own it.</p><p>Over time, you build a personal library of automation tools. Each one solves a specific problem you have faced in real investigations. Each one is code you understand because you built it. When a platform changes, you adapt your tool. When a new investigative need arises, you build a new tool.</p><p>This is not about <strong>learning Python perfectly</strong>. It is about <strong>learning how to solve problems with code</strong>. The syntax you can always look up. The logic is what matters.</p><h4>The Automation Mindset</h4><p>Start small. Automate one repetitive task. Gain confidence. Automate another. Before long, you will have a suite of tools that handle the mechanical work of OSINT collection, freeing your mind for the work that actually requires human intelligence. Analysis. Attribution. Judgment.</p><p>The machine collects. The investigator thinks.</p><h3>Module 9: Intelligence Report Writing &amp; Entity Graph Visualization</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mt0oXn70ihB5DaevwjvLoQ.png" /></figure><p>You can run the most brilliant investigation of your career. You can uncover connections nobody else found. You can piece together a target’s entire digital footprint from a single username. <strong>But if you cannot communicate what you found in a way that your client understands, believes, and can act on, your investigation - failed</strong>.</p><p><strong>Report writing</strong> is not the boring part of OSINT. It is the part that gives everything else <strong>meaning</strong>. The report is your product. The client does not see your late nights. They do not see your clever dorks or your elegant scripts. They see the document you put in front of them. <strong>That document must be clear, accurate, sourced, and professional</strong>. This module teaches you how to build it.</p><h4>Lecture 8.1: Structuring the Intelligence Report</h4><p>A professional intelligence report follows a predictable structure. This is not about being creative. It is about being clear. The client should know exactly where to find the answer to any question within seconds of opening your document.</p><h4>Here is the standard structure. Use it for every report you write</h4><ol><li><strong>Executive Summary</strong></li></ol><p><strong>This is the most important section</strong>. Many clients will read nothing else. The executive summary must answer the original question in plain language, with no jargon, in under one page. State the investigation objective. State the key findings. State the risk rating or assessment. State the recommended next steps.</p><p>If your executive summary is vague, the client assumes the whole report is vague. Write it last. Write it after you know everything. Then make it sharp.</p><h4>Example:</h4><p><em>This investigation examined </em><strong><em>John Doe</em></strong><em> in connection with a proposed business partnership. Public records confirm </em><strong><em>Mr. Doe</em></strong><em> is a British national, born May 1962, residing in </em><strong><em>London</em></strong><em>. He is the sole director of </em><strong><em>HALL OR NOTHING MANAGEMENT LIMITED</em></strong><em> (dissolved </em><strong><em>January 2023</em></strong><em>). No adverse media, sanctions listings, or legal actions were identified. Open source intelligence revealed three additional social media profiles consistent with the subject’s known identity. Based on available information, the subject presents a LOW risk for partnership. A full finding summary follows.</em></p><p>2.<strong> Investigation Objective</strong></p><p>Restate exactly what you were asked to do. This sets the scope. If something is outside scope, note it here. This protects you if the client later asks why you did not investigate something you were never asked to investigate.</p><p>3.<strong> Methodology</strong></p><p>Explain how you gathered information. Do not list every tool. Summarize the approach. “<strong>Public records searches </strong>were conducted using <strong>UK Companies House</strong> and <strong>OpenCorporates</strong>. Social media analysis was performed using <strong>native platform search</strong> and <strong>public profile review</strong>. <strong>Historical data</strong> was retrieved via the <strong>Internet Archive Wayback Machine</strong>. All information was collected from publicly available sources without contacting the subject.”</p><p>This section establishes that your methods were legal, ethical, and repeatable.</p><p>4. <strong>Key Findings</strong></p><p>This is the body of the report. Organize findings by category. Corporate records. Personal identity. Digital footprint. Historical intelligence. Risk indicators. Each finding gets its own subsection with a clear heading. Each claim is supported by evidence.</p><p>5. <strong>Evidence Log</strong></p><p>A table linking each finding to its source. <strong>This is what makes your report defensible</strong>. If a client questions a claim, you point to the evidence log. Every row contains the finding, the source URL or document reference, the access date, and any relevant notes.</p><p>6. <strong>Risk Assessment</strong></p><p>A clear rating of <strong>Low</strong>, <strong>Medium</strong>, or <strong>High </strong>with justification. Do not hedge. The client is paying you for your professional judgment. Give it.</p><p>7. <strong>Recommendations</strong></p><p>What should the client do with this information? Proceed? Investigate further? Decline the partnership? Be specific.</p><h4>Lecture 8.2: Writing for Your Audience — Client, Legal, or Internal</h4><p>Your writing style changes depending on who reads the report. The structure stays the same. The language adapts.</p><p><strong>Corporate Client</strong></p><p>A business client wants answers, not education. Use plain language. Avoid jargon. Put the conclusion first. Bullet points are your friend. They are not paying you to show off your vocabulary. They are paying you to help them make a decision.</p><p><strong>Legal Referral</strong></p><p><strong>If your report may end up in court</strong>, every <strong>word matters</strong>. State facts, not opinions, unless clearly labeled as such. Use precise language. “<strong>The subject’s LinkedIn profile listed employment at XYZ Corp from 2018 to 2022</strong>” is a fact. “The subject appears to have exaggerated their employment history” is an opinion. Label opinions clearly. Cite every source. Courts destroy reports with unsupported claims.</p><p><strong>Internal Security Team</strong></p><p>An internal team wants technical detail. They want your methodology in depth. They want to replicate your findings. Give them the dorks you used. Give them the API endpoints. Give them the tool commands. They may need to run the same investigation again in six months. Your report should make that possible.</p><h4>Lecture 8.3: Evidence Documentation &amp; Source Citation Standards</h4><p>Every claim in your report needs a source. Not most claims. Every claim. If you cannot cite it, you cannot write it.</p><p><strong>The Standard Citation Format</strong></p><p>For each piece of evidence, record:</p><ul><li><strong>Source URL or Document Reference</strong>: The exact web address or filing number.</li><li><strong>Access Date</strong>: When you retrieved the information. Websites change. The access date proves what you saw existed on that date.</li><li><strong>Screenshot Reference</strong>: A filename or page number pointing to the visual record you preserved.</li><li><strong>Notes</strong>: Any context about the source’s reliability or limitations.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*quXhqAVnQiAsyry93T0DaA.png" /></figure><p><strong>Preserving Evidence</strong></p><p>Screenshots are not optional. Websites disappear. Profiles get deleted. Filings get updated. Your screenshot is the permanent record. Take full-page screenshots. Save them with descriptive filenames. Store them in a folder alongside your report. If your report says something, there should be a screenshot proving it.</p><h4>Lecture 8.4: Entity Graph Visualization — Tools &amp; Methodology</h4><p>An entity graph turns your written findings into a visual map. It shows connections between people, companies, accounts, emails, and locations in a way that text cannot. A good graph tells the story at a glance.</p><p><strong>Why Graphs Matter</strong></p><p>Your client may not read all twenty pages. They will look at the graph. If the graph clearly shows the target at the center with connections radiating outward to companies, social media accounts, and risk indicators, they understand the investigation immediately. The graph is your executive summary in visual form.</p><p><strong>Tools for Entity Graph Building</strong></p><p><strong>Maltego </strong>is the industry standard for OSINT graph building. It is commercial software with a free Community Edition. Maltego allows you to create entities (people, companies, domains, emails), connect them with relationships, and run transforms that automatically discover new connections. The learning curve is real, but the output is professional-grade.</p><p><strong>Gephi </strong>is a free, open-source graph visualization platform. It is less automated than Maltego but gives you complete control over the visual output. You build a spreadsheet of nodes and edges, import it into Gephi, and the software renders the graph. This is the tool to use when you need publication-quality visuals.</p><p><strong>Obsidian </strong>is a free knowledge management tool that doubles as an investigation mapping platform. It uses Markdown files and supports a graph view that visually connects your notes. Create a note for each entity (person, company, email, account). Link notes together using wiki-style links. Obsidian’s graph view renders the connections automatically. This is ideal for building an investigation knowledge base that grows over time. You can toggle between reading your structured notes and viewing the connection graph. For long-term investigations with many entities, Obsidian keeps everything organized and visually traceable.</p><p><strong>OSINTTracker</strong> is a purpose-built OSINT investigation management tool. It is designed specifically for investigators who need to track entities, relationships, and findings across complex cases. Unlike general-purpose graph tools, OSINTTracker understands OSINT workflows. You log entities, define relationships, attach evidence, and the platform generates connection maps automatically. It bridges the gap between note-taking and graph visualization in a single interface built for the work you actually do.</p><p><strong>Google Drawings</strong> /<strong> </strong><a href="https://draw.io/"><strong>draw.io</strong></a><strong> </strong>are free, simple options for small graphs. If your investigation found five entities and six connections, you do not need Maltego. A clean diagram in <a href="https://draw.io/">draw.io</a> is faster and equally clear.</p><h4>Lecture 8.5: Building the Final Intelligence Package</h4><p>The final package is more than the report. It is everything the client needs to understand, verify, and act on your findings.</p><p><strong>The Package Contents</strong></p><ol><li>The Written Report (<strong>PDF</strong>) — The structured document from Lecture 8.1.</li><li>The Entity Graph (<strong>PNG </strong>or <strong>PDF</strong>) — The visual map from Lecture 8.4.</li><li>The<strong> Evidence Folder</strong> — All screenshots, organized by finding. Filenames match the evidence log.</li><li>The<strong> Raw Data</strong> (Optional) — CSV files, JSON output, tool results. Include this if the client has technical staff who may want to verify or extend your work.</li></ol><h4>Packaging for Delivery</h4><p>Zip everything into a single archive. Name it clearly: <strong>Investigation_SubjectName_YYYY-MM-DD.zip</strong>. Include a README file that lists the contents and explains the folder structure.</p><p>If delivering via email, encrypt the attachment. The report contains personal data. Protect it.</p><h4>The Final Review Checklist</h4><p>Before you submit, go through this list:</p><ul><li>Every claim in the report has a cited source.</li><li>Every cited source has a matching screenshot in the evidence folder.</li><li>The entity graph is clear and labeled.</li><li>The executive summary answers the original question.</li><li>The risk rating is justified.</li><li>The report has been proofread for spelling and grammar.</li><li>The client’s name, your name, and the date are on the cover page.</li><li>The file is encrypted if sent electronically.</li></ul><p>If any item on this list is unchecked, you are not done.</p><h4>Additional Resources for Report Writing</h4><p>These OSINT practitioners have published excellent content on report writing and investigation methodology. Study their work.</p><ul><li><strong>Tactical OSINT Academy </strong>— Entity graph building and investigation workflow. The video referenced in Lecture 8.4 is a strong starting point.</li><li><strong>Bellingcat </strong>— The public face of professional open source investigation. Their published reports are models of structure, sourcing, and clarity. Read them. Study how they present findings.</li><li><strong>Trace Labs</strong> — Missing persons OSINT. Their methodology emphasizes speed, accuracy, and actionable intelligence. Their report templates are worth reviewing.</li><li><strong>Michael Bazzell</strong> (IntelTechniques) — His books and training materials cover report writing for private investigators. Practical, no-nonsense guidance.</li></ul><h4>Building Your First Entity Graph — A Walkthrough</h4><p>This video by <strong>CyberSudo / UK OSINT Community </strong>are one of the clearest tutorials on entity graph building for investigators. Watch it before you build your first graph:</p><ul><li><a href="https://www.youtube.com/watch?v=lUgGR7CZlKg"><strong>https://www.youtube.com/watch?v=lUgGR7CZlKg</strong></a></li><li><a href="https://www.youtube.com/watch?v=DM5vGq4mJzk"><strong>https://www.youtube.com/watch?v=DM5vGq4mJzk</strong></a></li></ul><p>These videos covers selecting entities, establishing relationships, and structuring the graph so it tells a coherent story rather than becoming a tangled mess. This is essential viewing.</p><p><strong>Graph Methodology</strong></p><ol><li>Start with the primary entity. Your target. Place them in the center.</li><li>Add confirmed connections. Companies they direct. Social media accounts you verified. Email addresses you extracted. Each connection gets its own node.</li><li>Add secondary connections. The company’s other directors. The email domain’s owner. Each layer moves outward from the center.</li><li>Color code by confidence. Green for confirmed. Yellow for probable. Red for unverified. The client sees immediately what is solid and what needs further work.</li><li>Label every edge. Do not just draw lines. Label them. “Director of.” “Owns.” “Linked via profile picture hash.” “Registered email address.” The label explains the connection.</li><li>Keep it clean. A graph with 200 nodes is noise. A graph with 20 nodes and clear relationships is intelligence. If the graph is too dense, split it into multiple views. One for corporate structure. One for digital footprint. One for risk indicators.</li></ol><h4>Choosing the Right Tool</h4><p><strong>Tool________Best_________ForCost</strong></p><ul><li><strong>Maltego </strong>— Automated transforms, large investigations &gt; Free CE / Paid Pro</li><li><strong>Gephi </strong>— Publication-quality static graphs &gt; Free</li><li><strong>Obsidian </strong>— Investigation knowledge base with graph view &gt; Free</li><li><strong>OSINT </strong>— TrackerPurpose-built OSINT case management and graphing &gt; Free / Paid</li><li><a href="https://draw.io/"><strong>draw.io</strong></a><strong> / </strong>Google — Drawings Simple, small graphs &gt; Free</li></ul><h3>Capstone Course: The Integrated Investigation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MTruW5iKL39PKAhOUkapjw.png" /></figure><p><strong>Capstone Course</strong>: The Integrated Investigation</p><p>This final module is not a lecture. It is a simulated, real-world investigation. Every technique, every tool, every methodology you have learned across this course now comes together in a single assignment. There are no walkthroughs. Only the target, the task, and your training.</p><h4>Scenario</h4><p>A client is considering a business partnership with an individual named Michael Hall. Before proceeding, they require a discreet background investigation. The client has provided only a name, a dissolved company, and a LinkedIn profile. You must find everything else.</p><h4>Target Information</h4><ul><li>Subject Name: <strong>Michael Hall</strong></li><li>Known Company: <strong>HALL OR NOTHING MANAGEMENT LIMITED</strong></li><li>LinkedIn Profile: <a href="https://www.linkedin.com/in/michael-hall-8256b964/"><strong>https://www.linkedin.com/in/michael-hall-8256b964/</strong></a></li></ul><h4>Investigation Tasks</h4><p>Using only open-source intelligence, gather comprehensive intelligence on the subject to inform your client’s decision. Answer the following questions with documented methodology for each.</p><p><strong>Task 1</strong>: Who is Michael Hall, and what is his affiliation with HALL OR NOTHING MANAGEMENT LIMITED?</p><p><strong>Task 2</strong>: What is his role within the company? Provide any appointment dates, resignation dates, or changes in position.</p><p><strong>Task 3</strong>: What is his country of residence and date of birth? Cite the source document.</p><p><strong>Task 4</strong>: What is the company registration number?</p><p><strong>Task 5</strong>: What was the company’s previous name, and during what period was that name in use?</p><p><strong>Task 6</strong>: What is the current company status? Is it still active?</p><p><strong>Task 7</strong>: On 22 May 2008, what was the company’s full legal name, registered office address, post town, country, and postcode?</p><p><strong>Task 8</strong>: Extract Michael Hall’s LinkedIn numeric User ID. Document your extraction method.</p><p><strong>Task 9</strong>: Discover any corporate or personal email addresses associated with Michael Hall or his company. Document how each was found and validated.</p><h4>Deliverable Requirements</h4><p>Your report must include:</p><ul><li>Clear, concise answers to each task.</li><li>The methodology, techniques, and tools used for each phase of intelligence collection.</li><li>Source citations for every finding (URLs, document references, access dates).</li><li>A professional tone suitable for client delivery.</li></ul><h4>Submission</h4><p>Submit your completed report to: <strong>cybershieldmentor@gmail.com</strong></p><h4>Operational Boundaries</h4><ul><li>Use only publicly available information.</li><li>Do not contact the subject or any associated individuals.</li><li>Do not attempt to access any private accounts or systems.</li><li>This is a training exercise. All findings are for educational purposes only.</li></ul><p>Begin your investigation. Your client is waiting.</p><h4>A Final Word to the Analyst</h4><p>You have reached the end of this course. You now know how to extract unchangeable numeric IDs from social media platforms. You know how to geolocate an image from a single street sign. You know how to trace a company’s real owners through layers of offshore entities. You know how to recover deleted Reddit posts, extract commit emails from GitHub, and pull profile pictures from phone numbers without ever making a call.</p><p><strong>These skills are powerful. Do not confuse power with permission</strong></p><p>Every technique in this course works on real people. Real people with real lives, real families, and real expectations of privacy, even when they post publicly. The fact that you can find something does not mean you should. The fact that information is publicly accessible does not mean the subject intended for it to be collected, analyzed, and filed in a report about them.</p><p><strong>Before you investigate anyone, ask yourself three questions</strong></p><p><strong>First</strong>, is the purpose legitimate? Due diligence for a business partner. Locating a missing person. Supporting a legal case. Investigating a threat. These are legitimate purposes. Investigating an ex-partner out of jealousy is not. Investigating a stranger out of curiosity is not. If you cannot explain your purpose to a colleague without feeling uncomfortable, stop.</p><p><strong>Second</strong>, are you minimizing harm? Collect only what you need for the investigation. Do not hoard data. Do not share findings with anyone outside the authorized audience. When the investigation is complete, securely dispose of what you no longer need. The less personal data sitting in your investigation folders, the less can be leaked, stolen, or misused.</p><p><strong>Third</strong>, are you operating within the law? Laws vary by jurisdiction, but the principle is universal. If you are unsure whether a technique is legal, consult a lawyer before using it. “I read it in an OSINT course” is not a legal defense. This course has taught you what is technically possible. It is your responsibility to determine what is legally permissible in your jurisdiction and your context.</p><p>The OSINT community has a saying: “<strong>Trust but verify</strong>.” I will add one more: “<strong>Investigate</strong>, <strong>but do not become the story</strong>.”</p><p>Your operational security failures become someone else’s headline. Your ethical failures become ammunition against the entire profession. <strong>Every time an investigator uses these techniques for harassment, stalking, or personal gain, it damages the credibility of legitimate OSINT work</strong>. Do not be that person.</p><p>You have the tools. You have the methodology. You have the technical skills. What you do with them defines who you are as a professional.</p><p>Go do good work. Be thorough. Be accurate. Be ethical. The field needs more investigators like that.</p><h4>About the Author</h4><p>This course was built by someone who does the work. No theory without practice. No technique without testing.</p><p>If you want to connect, ask questions, or share what you have built using these skills, you can find me here:</p><p>- <strong>LinkedIn</strong>: <a href="https://www.linkedin.com/in/precious-vincent-669279263/%60">https://www.linkedin.com/in/precious-vincent-669279263/`</a><br>- <strong>X </strong>(<strong>Twitter</strong>): <a href="https://x.com/d4rk_intel%60">https://x.com/d4rk_intel`</a><br>- <strong>GitHub</strong>: <a href="https://github.com/techenthusiast167%60">https://github.com/techenthusiast167`</a></p><p><strong>End of Course</strong></p><h3>Appendix B: Complete Tools Index</h3><p>Every tool referenced in this course, organized by category, with URLs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjGhItN3z6H7tf996hMIcQ.png" /></figure><p><a href="https://drive.google.com/file/d/10eYgoMZcVxiFhkUh8Vs7XSnqnNcDQlgE/view?usp=sharing"><strong>https://drive.google.com/file/d/10eYgoMZcVxiFhkUh8Vs7XSnqnNcDQlgE/view?usp=sharing</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0baa7ce97e6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSINT Challenge: Operation “Vinyl Vault”]]></title>
            <link>https://preciousvincentct.medium.com/osint-challenge-operation-vinyl-vault-4d631350a1a3?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d631350a1a3</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 22:58:38 GMT</pubDate>
            <atom:updated>2026-06-23T22:58:38.097Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8QBOknNVEA1CqoDyqkjBg.png" /><figcaption><strong>CLASSIFICATION</strong>: Confidential</figcaption></figure><p>Welcome, Analyst.</p><p>You are a member of a specialized OSINT unit tasked with a unique historical investigation. In 2025, an independent film production company, “Echoes of the Past Productions,” has acquired the rights to produce a documentary about the UK music industry in the early 1990s.</p><p>During their research, they stumbled upon a single, scanned page from a 13 July 1991 issue of Music Week, a key trade publication. This document appears to mention several significant events and figures.</p><p>However, the page is incomplete and contains numerous typographical errors. The producers need our assistance to validate the information, find additional context, and locate potential interview subjects who were involved in these historical events. Your mission, should you choose to accept it, is to use open-source intelligence techniques to “fill in the blanks” and contextualize the events in this document.</p><h4>Your investigation will be divided into three phases:</h4><ol><li><strong>Phase 1</strong>: The Present-Day Connection (Reconnaissance)</li><li><strong>Phase 2</strong>: The Paper Trail (Historical Analysis)</li><li><strong>Phase 3</strong>: The Human Element (Media &amp; PAI)</li><li><strong>Phase 4</strong>: Behind the Image (Technical Analysis)</li></ol><h4>Rules of Engagement:</h4><ul><li>Use only open-source, publicly available information.</li><li>Do not attempt to hack, socially engineer, or contact any real individuals mentioned.</li><li>Document your findings and the specific search methods (e.g., Google Dorks, Wayback Machine URL, reverse image search queries) used in each task.</li><li>The goal is to demonstrate your proficiency in using various OSINT tools and techniques.</li></ul><p>Good luck, Analyst. The past is waiting to be uncovered.</p><h3>Phase 1: The Present-Day Connection (Reconnaissance)</h3><p><strong>Scenario</strong>: Our first task is to see how the organizations and people mentioned in the 1991 article have evolved. Specifically, we need to understand the current status of some of the key organizations and find a lead on a company mentioned in a later page.</p><h4>Tasks:</h4><ol><li><strong>Identify the Legacy Company</strong>: The article on Page 1 mentions “<strong>MCPS</strong>”. What does MCPS stand for? Did the organization cease to exist, or did it merge with another entity? If it merged, what is its current name?</li><li><strong>Modern Presence of the Trade Body</strong>: Page 6 mentions the “<strong>BPI</strong>”. Locate the official, modern-day website for this organization.</li><li><strong>Geolocation of a Company</strong>: The last page of the document contains an advertisement for a PR company. Based on the address provided in the ad, geolocate their office in 1991, and current relocation address. Provide the exact latitude and longitude coordinates for that office building in 1991. What is the approximate distance from this location to the nearest London Underground station?</li></ol><h3>Phase 2: The Paper Trail (Historical Analysis)</h3><p><strong>Scenario</strong>: A key part of your analysis is to find the missing context surrounding the stories in the article. We need to find the source of this document and see if related news articles can shed light on the events.</p><h4>Tasks:</h4><ol><li><strong>Identify the Source</strong>: This document appears to be a scanned page from a publication. Using the text, header, and date format (e.g., the footer “MUSIC FESTIVAL 11 JANUARY 1981”), identify the full, official title and publisher of this publication. What is its current publication status: First issue date, ISSN, Current status?</li></ol><h4>Complete the note on evolution:</h4><p>The publication has undergone several changes. Between 17 January ____ and 1983, it was briefly renamed _____ &amp; _____ ____ to reflect the growing importance of sell-through videos, before reverting to <em>Music Week</em> . In April 1991 (just months before this document was published), Music Week incorporated ______ ______ as a chart supplement .</p><p><strong>2. Historical Record via the Wayback Machine</strong>: The “documentary producers” want to see the evolution of the BPI’s website and how they’ve presented their history. Using the Wayback Machine, find the BPI’s website from the early 2000s and again in the present day. Compare and contrast the “About Us” section from both periods. What are the key differences?</p><p>3. <strong>Google Dorking for a Lost Article</strong>: The article mentions “Maurice Oberstein” and his role as the new BPI chairman. Using google dork, find a PDF file on a UK government website that might contain his name or history related to the UK music industry. Construct a specific dork that would find a PDF from gov.uk containing the &quot;POI’s full name&quot;. Report the dork used and the title of any relevant results and what it entails about the POI.</p><h3>Phase 3: The Human Element (Media &amp; PAI)</h3><p><strong>Scenario</strong>: Your investigation must identify potential living leads for the documentary. We need to verify the existence and current professional standing of a key figure from the article.</p><h4>Tasks:</h4><ol><li><strong>Verify a Primary Source</strong>: The article on Page 1 quotes “Warner’s director of commercial and business affairs, ____ _______”. Research this individual using professional social networks and news searches. What is their actual, full name and their current job title? Which major music company do they now work for?</li><li><strong>Social Media Profiling</strong>: The advertisement for “Hall Or Nothing” PR on Page 36 is a key artifact. Find the current official account for this company on a major social media platform (like X/Twitter/LinkedIn). When was their first post or when was the account created on any of these platforms and company director?</li><li><strong>LinkedIn Intel — Company Email Pattern Discovery: </strong>Based on previous intelligence gathered during this investigation, a key individual has been identified as a director of the company in question. Preliminary research on professional networking platforms (specifically LinkedIn) has yielded references to Michael Hall as one of the company’s directors. However, further investigation on the platform has proven inconclusive, as any existing profiles or direct presence appear to be inactive or no longer accessible — — As an OSINT analyst, you are tasked with conducting a comprehensive investigation to locate and verify information on the aforementioned director, <strong>Michael Hall</strong>, using only open-source intelligence methodologies and official public records. Your investigation must uncover the following information: <strong>Company email address </strong>(based on identified email patterns for the organization), <strong>Date of birth</strong>, Correspondence address (registered office or service address), <strong>Country of residence</strong>, <strong>Appointment date</strong> (as a director of the company),<strong> Resignation date</strong> (if applicable), One <strong>close associate</strong> (specifically, the Secretary of the company.</li></ol><h3>Phase 4: Behind the Image (Technical Analysis)</h3><p><strong>Scenario</strong>: We have a high-quality scan of the original document. The producers suspect there might be embedded information in the file that could help with the investigation.</p><h4>Tasks:</h4><p>Metadata Mining: By analysing the PDF file you have found from the initial phase, provide the answers to the tasks below:</p><ul><li>The software used to create the PDF</li><li>The author of the PDF</li><li>The date and time the PDF was created.</li><li>The application used to produce the document before it was converted to PDF (producer).</li></ul><h3>Final Report Submission</h3><h3>Report Requirements</h3><p>Prepare a comprehensive investigative report containing all your findings from Phases 1–4.</p><h3>Report Structure</h3><ol><li><strong>Executive Summary </strong>&gt; Brief overview of investigation and key findings</li><li><strong>Phase 1 Findings </strong>&gt; MCPS, BPI, and Hall Or Nothing geolocation results</li><li><strong>Phase 2 Findings </strong>&gt; Source identification, Wayback Machine comparison, Google Dork results</li><li><strong>Phase 3 Findings</strong> &gt; Fran Nevrkla verification, Hall Or Nothing social media, Michael Hall director intel</li><li><strong>Phase 4 Findings</strong> &gt; PDF metadata extraction results</li><li><strong>Methodology Summary</strong> &gt; List of all OSINT tools, techniques, and dorks used</li><li><strong>Sources Cited</strong> &gt; All URLs, databases, and references used</li><li><strong>Appendix </strong>&gt; Screenshots, URLs, and supporting evidence</li></ol><h3>Submission Guidelines</h3><ul><li><strong>Format</strong>: Microsoft Word (.docx) or PDF (.pdf)</li><li><strong>Length</strong>: Minimum 5 pages</li><li><strong>Deadline</strong>: 7 days from start of challenge</li><li><strong>Email</strong>: cybershieldmentor@gmail.com</li><li><strong>Subject Line</strong>: Vinyl Vault Report - [Your Name/Team Name]</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d631350a1a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AN OSINT MOVIE – OSINTer]]></title>
            <link>https://preciousvincentct.medium.com/an-osint-movie-osinter-00b804a54c85?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/00b804a54c85</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 08:52:00 GMT</pubDate>
            <atom:updated>2026-06-22T08:54:20.933Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone, for months, I have been developing <strong>OSINTer</strong> – a feature film about an OSINT investigator who uses open-source intelligence to track down a cybercriminal group responsible for a massive global data breach.</p><p>This is not a gadget-heavy spy thriller. It is grounded in real OSINT methodology – tools used by real investigators every day.</p><p>I have completed the opening scenes and I am seeking production partners, sponsors, and collaborators who believe in telling authentic tech-driven stories from Africa and beyond.</p><blockquote>If this resonates, or if you know someone who might be interested, please share or connect. Let us bring OSINTer to life.</blockquote><blockquote>Attach below is the link to the opening scenes:</blockquote><blockquote><a href="https://drive.google.com/file/d/1bNNQ6mNg9YlB-OlfZsE5TzpbpZlc-OgZ/view"><em>https://drive.google.com/file/d/1bNNQ6mNg9YlB-OlfZsE5TzpbpZlc-OgZ/view</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*j-ZziTsO3NZfpuYuwMvFog@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*Qp6wl1HBLI-qsGDF46FehA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=00b804a54c85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSINT CHALLENGE: Operation LeakRoot]]></title>
            <link>https://preciousvincentct.medium.com/osint-challenge-operation-leakroot-faa191cb17cf?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/faa191cb17cf</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Sun, 14 Jun 2026 22:03:13 GMT</pubDate>
            <atom:updated>2026-06-15T08:49:59.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmaH-ntz25xOn8F0maainQ.png" /></figure><h3>Scenario: “Has My Data Been Leaked?”</h3><h4>The Request:</h4><p>A private individual — call <strong>Lindadida832</strong> — has approached you as a security/OSINT analyst. <strong>Linda </strong>is concerned that their personal credentials may have been exposed in past data breaches, particularly the <strong>Facebook 2019 breach</strong> or other public data leaks.</p><p><strong>Linda </strong>admits to reusing the same password across multiple personal accounts over the years. Recently, <strong>Linda </strong>received several suspicious login attempt notifications and wants to know:</p><ul><li>Has my email address, address, password hash, or username appeared in any public breach data?</li><li>If so, where is it hosted, and who else might have access?</li></ul><p><strong>Linda </strong>has given you permission to conduct open-source intelligence on their behalf, using only publicly available information.</p><h4>Your Mission:</h4><p>Using advanced search queries and public records, determine:</p><ol><li>Whether <strong>Linda</strong>’s credentials (email, address, password hash, or username tied to their domain) appear in any publicly accessible breach data, paste site, or exposed file.</li><li>If exposure is confirmed, identify the infrastructure (domain name, hosting details) where that breach data resides.</li></ol><h4>The Only Clue Linda Can Provide:</h4><p>A phone number &amp; an email address that Linda believes may be associated with one of their old online accounts or a domain registration they were connected to years ago:</p><blockquote><em>KzIxMy4wNTU1NjI3NTIx</em></blockquote><blockquote><em>bGluZGFkaWRhODMyQGdtYWlsLmNvbQ0K</em></blockquote><h3>Challenge Objective</h3><blockquote><em>Determine if Linda’s</em> <em>personal data (Phone number, email, address, password, or username) has been exposed online, and identify the domain hosting that breach data.</em></blockquote><p><strong>Hint:</strong> Your initial lead is right in front of you &gt; <strong>string</strong>. Begin by decoding the client’s phone number. A Facebook breach lookup tool could provide the first hint. Next, decode the email address, then follow the trail using advanced search operators and breach intelligence methods to find the website where the client’s email and related data were exposed. Gather all evidence to determine the full extent of the breach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hhE3Af3zGXRjfPR7WKgKYA.png" /></figure><h3>Professional Report Template (For Participants)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CMKeolnr76nS0Bur_3uqvQ.png" /><figcaption><a href="https://drive.google.com/file/d/1lbhAPOA6wTs_w7J8zP-Uno3MTAH0LlHf/view?usp=sharing">https://drive.google.com/file/d/1lbhAPOA6wTs_w7J8zP-Uno3MTAH0LlHf/view?usp=sharing</a></figcaption></figure><p>All reports are to be submitted to the challenge email address: <strong>cybershieldmentor@gmail.com</strong></p><h4>This is a REAL OSINT investigation involving publicly available data</h4><h3>NO UNAUTHORIZED ACCESS</h3><p><strong>You shall not</strong>:</p><ul><li>Attempt to log into any account, system, or service discovered during this investigation</li><li>Use any discovered password, hash, token, or credential to authenticate anywhere</li><li>Access any password-protected area of any website, even if credentials are publicly exposed</li><li>Modify, delete, or exfiltrate any data from any discovered source</li><li>Scan, probe, or exploit any vulnerability on any target domain</li></ul><p>Observing publicly indexed data is permitted. Interacting with live systems is not.</p><h3>NO DATA RETENTION OR REDISTRIBUTION</h3><p><strong>You shall not</strong>:</p><ul><li>Download, copy, store, or archive any breach data, credential material, or personally identifiable information (PII) discovered during this investigation beyond what is necessary to document findings for the client</li><li>Share, publish, redistribute, or transmit any raw breach data to any third party</li><li>Upload findings to any public repository, paste site, or forum</li><li>Use any discovered data for any purpose outside this authorized investigation</li></ul><p>All notes, screenshots, and extracts must be deleted upon completion of the client report unless required for legal or audit purposes.</p><h3>ACKNOWLEDGMENT</h3><p>By proceeding with this investigation, you affirm that you have read, understood, and agree to be bound by the terms above.</p><p>If you do not agree, stop immediately and do not proceed!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faa191cb17cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of the Query: Advanced Google Dorking Matrices for OSINT Investigators]]></title>
            <link>https://preciousvincentct.medium.com/the-art-of-the-query-advanced-google-dorking-matrices-for-osint-investigators-ab129564af38?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab129564af38</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Sat, 13 Jun 2026 02:13:11 GMT</pubDate>
            <atom:updated>2026-06-16T18:24:36.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6oManVFP3swlFEY-lHwIxQ.png" /><figcaption>One chain form an entity — Two form a footprint — Three form an Intelligence collection</figcaption></figure><p><strong>Google Dorking</strong> — often referred to as Google Hacking- is one of the most powerful passive reconnaissance techniques available. Because Google’s crawlers index everything they can touch, misconfigured servers, forgotten directories, and exposed personal or corporate data routinely end up in the public index.</p><p>By utilizing advanced search operators, you can force Google to act as a precision filter rather than a generic search bar. This article categorizes these techniques into <strong>Beginner</strong>, <strong>Intermediate</strong>, and <strong>Advanced</strong> tiers, tailored for gathering intelligence on digital footprints, personnel assets, and infrastructural exposures.</p><p>As an open-source intelligence (OSINT) analyst, security researcher, or digital investigator, mastering advanced search operator techniques is paramount. In the digital age, footprints are scattered across fragmented ecosystems; these advanced directives serve as a surgical filter, enabling you to extract critical pieces of evidence regarding a Person of Interest (POI) that standard queries would completely miss.</p><p>In this guide, we will break down the mechanics of advanced Google Dorking, walking through structured, multi-operator methodology to harvest actionable intelligence on a target — efficiently, systematically, and ethically.</p><h3><strong>Phase 1: The Building Blocks (Beginner Operators)</strong></h3><p>Before combining complex strings, you must understand the core operators that restrict search scope. These are the structural foundation of any target-specific search query.</p><ul><li><strong>site</strong>: Restricts results exclusively to a specific domain, subdomain, or top-level domain (e.g., site:gov, site:linkedin.com).</li><li><strong>filetype</strong>: (or <strong>ext</strong>:) Filters results to specific file extensions (e.g., <strong>pdf</strong>, <strong>xlsx</strong>, <strong>docx</strong>, <strong>txt</strong>).</li><li><strong>inurl</strong>: Looks for specific keywords anywhere within the URL path.</li><li><strong>intitle</strong>: Restricts results to pages containing the specified keyword inside the HTML &lt;title&gt; tag.</li><li><strong>intext</strong>: Searches exclusively within the body text of a webpage, ignoring URLs, titles, and links.</li><li><strong>“”</strong> (<strong>Double Quotes</strong>): Forces an <strong>exact phrase match</strong> instead of breaking the words apart.</li><li><strong>- </strong>(<strong>Minus Sign</strong>): Excludes specific words or entire operators from your search results to eliminate noise.</li></ul><h3><strong>Phase 2: Beginner Dorks: Footprint, Social Media &amp; Email Address </strong>Discovery</h3><p>At this stage, single operators or simple combinations are used to map a target’s primary digital footprint, public social presence and email address discovery.</p><h4><strong>2.1 Social Media Footprint</strong></h4><p>To track down an individual’s presence across multiple social networks without sifting through unrelated web results:</p><ul><li><strong>Dork:</strong> “John Doe” site:instagram.com OR site:twitter.com OR site:linkedin.com</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8Z8cKs93BExdNnSlo0bPg.png" /><figcaption>NOTE: <em>You can further customize the chain to make it longer by additionally incorporating different social media footprints.</em></figcaption></figure><p><strong>What It Does:</strong> Forces Google to find pages containing the exact name “John Doe” strictly hosted on the specified social platforms.</p><h4>2.2 Tracking Email Address Mentions</h4><p>To find where a POI’s personal email address has been published on public notice boards, domain registrations, or school listings:</p><ul><li><strong>Dork: </strong>“<a href="/service/mailto:johndoe99@gmail.com">johndoe99@gmail.com</a>” OR “<a href="/service/mailto:johndoe@company.com">johndoe@company.com</a>” site:*</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6FrTeU7pGOetUlsn-XlcQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZM9SoQvmmsx_DC8NXtb2w.png" /></figure><p><strong>What It Does:</strong> Searches the entire indexed web for any literal occurrence of their specific email addresses.</p><h4>2.3 The Target-Specific Explicit Chain</h4><p>Instead of relying on a broken wildcard, explicitly list the specific target email layouts inside a parenthetical <strong>OR </strong>group. This forces Google to respect the exact domain parameters.</p><ul><li><strong>Dork: </strong>“John Doe” (“gmail.com” OR “yahoo.com” OR “hotmail.com” OR “outlook.com”)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pv_nj72J38EXZBYFjOK5dw.png" /></figure><p><strong>What It Does:</strong> Google looks for the exact phrase “<strong>John Doe</strong>” on pages that also contain at least one of those complete email domain strings. This is highly effective for discovering public directory pages, contact lists, or old forum sign-up sheets.</p><h4>2.4 The “Intext” Precision Dump Chain</h4><p>If you want to skip regular articles that happen to mention a person named John Doe and instead find raw text entries where they actually typed out an email address block.</p><ul><li><strong>Dork: </strong>“John Doe” (intext:”@gmail.com” OR intext:”@yahoo.com”)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUX7cLHo8JnS7OKV4Mr6Hw.png" /></figure><p><strong>What It Does:</strong> By prepending <strong>intext:</strong>, you instruct Google&#39;s parsing engine to ignore the code, URLs, and metadata, looking strictly inside the viewable body text for the character footprint of an active inbox handle.</p><h4>2.5 The Wide-Open Extraction Chain</h4><p>If you are hunting for <em>any</em> corporate or custom domain email address linked to them (not just Gmail or Yahoo), use a proximity identifier phrase instead of a domain wildcard.</p><ul><li><strong>Dork: </strong>“John Doe” “email me at” OR “contact email” OR “email:”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CoU7tYtfdIJ5fIiiH-q1hA.png" /></figure><p><strong>What It Does:</strong> It tricks human behavior. When people post their custom domain emails on personal portfolios or classified sites, they almost always prefix it with structural introductory phrases like <em>“</em><strong><em>Contact email</em></strong><em>: </em><strong><em>johndoe@domain.com</em></strong><em>”</em>. This chain targets those exact behavioral footprints.</p><h4>2.6 Finding Internal Document Assets</h4><p>When organizations compile contact databases or communication directories internally, they regularly publish or store them as PDFs.</p><ul><li><strong>Dork: </strong>filetype:pdf “<a href="http://twitter.com/company">@company</a>.com” “email”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kj6NrGw9aYeRvCkpQmGWhA.png" /></figure><ul><li><strong>What It Does:</strong> Filters search parameters strictly to PDF documents containing the literal domain handle <strong>@company.com</strong> alongside the specific text marker <strong>&quot;email&quot;</strong>. This frequently surfaces internal employee directories, invoice trails, or project sign-off sheets that were accidentally left in indexable directories.</li></ul><h4>2.7 Identifying Exposed Inboxes on Live Domains</h4><p>This query bypasses the metadata structure of a website to scan the visible, client-facing text of a target’s live domain for active email footprints.</p><ul><li><strong>Dork:</strong> site:company.com intext:”<a href="http://twitter.com/company">@company</a>.com”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MLGIoC3Om-eKqzPIse7-Lw.png" /></figure><ul><li><strong>What It Does:</strong> Restricts the search boundaries entirely to the target’s web domain, using the <strong>intext</strong>: operator to locate any page where a full, functional corporate email address string has been literally printed into the body text.</li></ul><h4>2.8 High-Value Core Role &amp; Department Harvesting</h4><p>Instead of searching for random employee names, an investigator can sweep an entire corporate domain for primary operational distribution groups or high-value executive entry points.</p><ul><li><strong>Dork:</strong> “sales@” OR “ceo@” OR “info@” site:company.com</li></ul><p><strong>What It Does:</strong> Combines an explicit logical OR parenthetical block to hunt for highly targeted prefixes right next to the domain, pinpointing the direct contact lines for the sales department, the Chief Executive Officer, or the centralized administrative information desk.</p><h3>Phase 3: Advanced POI OSINT Chains (Task-Based Blueprints)</h3><p>In a live investigation, you combine these strategies into precise chains to eliminate false positives (people with the same name) and uncover hidden links.</p><h4>Chain 3.1 The “Identity Linkage” Chain (Connecting Real Name to Alias)</h4><p>If you have a target’s real name but don’t know their internet handles, this chain forces Google to look for instances where their real name is mentioned right next to a username format or social handle.</p><ul><li><strong>Dork</strong>: “John Doe” (“handle” OR “username” OR “alias” OR “aka” OR “@”) -site:linkedin.com</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_6MjbTGkoVULZtdtGa5oDw.png" /></figure><p><strong>What It Does:</strong> It mandates that the real name must appear alongside profile indicators while explicitly filtering out LinkedIn to avoid corporate fluff, forcing Google to surface alternative platforms, personal blogs, or gaming profiles.</p><h4>Chain 3.2: The “Pattern of Life &amp; Location” Chain</h4><p>To find out what city a POI lives in, what events they attend, or what local communities they belong to, you chain their identity with localized identifiers.</p><ul><li><strong>Dork</strong>: “John Doe” (“Port Harcourt” OR “Rivers State”) “resident” OR “member” OR “student” OR “alumni”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WBTzJpvfRk38EWdSiJ8okA.png" /></figure><p><strong>What It Does:</strong> This loops the POI’s name with specific geographic boundaries and high-probability relationship words, surfacing school graduation lists, local news mentions, church bulletins, or local sports registries.</p><h4>Chain 3.3: The “Associate &amp; Relationship” Map</h4><p>If a target has a clean digital footprint, you can often find information by investigating the people around them (colleagues, family, business partners).</p><ul><li><strong>Dork</strong>: “John Doe” “married” OR “son of” OR “daughter of” OR “partner” OR “director”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mo-zXHw3TrI4q8oXeyCsHQ.png" /></figure><p><strong>What It Does:</strong> This hunts for vital statistics, obituaries, wedding announcements, or corporate registration documents that link your POI to their immediate real-world network.</p><h4>Chain 3.4: The “Volatile Content &amp; Deleted Footprint” Chain</h4><p>If a POI recently wiped their social media profiles or deleted a personal website because they knew they were under scrutiny, you can use Google to dig up the ghost remnants.</p><ul><li><strong>Dork</strong>: site:targetpoi.blogspot.com OR site:targetpoi.com inurl:cached</li></ul><h4><strong>Alternative Archive Dork:</strong></h4><p>- <strong>Dork</strong>: site:web.archive.org/web/*/http://<em>targetpoi.com</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FnbfNoGKh1GRFXbG05VNCg.png" /></figure><h3>Phase 4: Professional OSINT Chains (Task-Based Blueprints)</h3><p>In professional investigations, individual operators are rarely used alone. <strong>Dork Chaining</strong> combines multiple advanced commands to systematically eliminate false positives and extract exact intelligence points.</p><h4>Chain 4.1: Target Email Footprint &amp; Breach Scouting</h4><p>This chain bypasses standard corporate landing pages to hunt for leaked email addresses, historical breach logs, and credential text dumps across the web and known paste-repositories.</p><ul><li><strong>Dork</strong>: (site:pastebin.com OR site:controlc.com OR site:justpaste.it) “@targetcompany.com”</li></ul><p><strong>Advanced Multi-Format Variant:</strong></p><ul><li><strong>Dork</strong>: site:com filetype:sql OR filetype:txt OR filetype:log “@targetcompany.com” “password” OR “hash”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVw8lGnkj4I5DxqVyvRVuw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qe832iDp3vnZTnahlLLk4g.png" /><figcaption>Utilize these advanced search techniques strictly within ethical boundaries — this is mainly for Cyber Threat Intelligence (CTI) analysts and security researchers hunting for external breach exposures, identifying compromised infrastructure, and mitigating digital risks.</figcaption></figure><p><strong>What It Does:</strong> The first query forces a scan across volatile text-sharing platforms for any raw mentions of the target’s corporate domain. The second variant searches public web assets for raw database exports (.sql) or server logs containing target emails paired alongside security keys or passwords.</p><h4>Chain 4.2: Corporate Employee Detail Infiltration</h4><p>When tasked with finding an organization’s specific employee base, titles, and internal IDs without touching the live network, this chain systematically maps their workforce via directory paths and document metadata.</p><h4>- The In-Text Roster Swarm</h4><p>Instead of forcing Google to look inside the URL, instruct it to search the actual visible body text of the website for common directory elements.</p><ul><li><strong>Dork</strong>: site:targetdomain.com intext:”our team” OR intext:”staff directory” OR intext:”contact us”</li></ul><h4>- Bypassing the Main Domain to LinkedIn</h4><p>If an organization’s primary website completely hides its employee rosters, you can bypass their domain architecture entirely and use Google to scrape LinkedIn’s index for profiles associated with that employer.</p><ul><li><strong>Dork</strong>: site:linkedin.com/in “Company Name”</li></ul><h4>Refining to a specific POI:</h4><ul><li><strong>Dork</strong>: site:linkedin.com/in “Company Name” “Engineer”</li><li><strong>Dork</strong>: site:linkedin.com/in “Company Name” “Manager”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbzOjT0pnan4glPIPsWI6A.png" /></figure><h4>- The Document Metadata Trap</h4><p>Corporate employee lists are frequently compiled into onboarding attachments or PDF phone sheets that are uploaded to subdomains but never linked on the main homepage.</p><ul><li><strong>Dork</strong>: site:targetdomain.com filetype:pdf “employee list” OR “staff roster” OR “directory”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmHBTm0lXZHuTOanFVGJOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JaehCjhxkE6IST9kgyCa-g.png" /></figure><h3>Phase 5: Target Phone Number &amp; SMS Log Harvesting</h3><p>Phone numbers are difficult to query due to varying international formatting standards. This chain utilizes regex-style variations and platform indexing to extract phone metrics linked to a target.</p><ul><li><strong>Dork</strong>: “target name” (“+234” OR “080” OR “070”) “phone” OR “contact” OR “WhatsApp”</li></ul><p><strong>Exposed Gateway Log Variant:</strong></p><ul><li><strong>Dork</strong>: intitle:”index of” “sms.log” OR “call_log.txt” OR “whatsapp_backup”</li></ul><p><strong>What It Does:</strong> The target-specific chain accounts for international country codes and localized prefix layouts while forcing an exact match on the target’s identity. The gateway log variant uncovers misconfigured SMS or communication server logs stored openly online.</p><h3>Phase 6: Advanced Subdomain Attack Surface Mapping</h3><p>To comprehensively list an organization’s forgotten staging environments, test servers, or internal portals without executing an active port scan.</p><ul><li><strong>Dork</strong>: site:*.targetcompany.com -site:www.targetcompany.com -site:blog.targetcompany.com -site:shop.targetcompany.com</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zm6_0bLqHncNgtNc3dZdJw.png" /></figure><p><strong>What It Does:</strong> This is an <strong>elimination chain</strong>. By using the wildcard (<strong>*</strong>), you tell Google to show every subdomain it knows. As you find high-traffic subdomains (<strong>www</strong>, <strong>blog</strong>, <strong>shop</strong>), you append them with a minus sign (<strong>-</strong>). This systematically strips away public web layers, forcing Google to surface hidden, low-traffic subdomains like <strong>dev.targetcompany.com</strong>, <strong>beta-testing.targetcompany.com</strong>, or <strong>internal-api.targetcompany.com</strong>.</p><h3>Phase 7: Simple POI OSINT Chains</h3><p>Simple dorking combines multiple operators to target specific data formats, pattern leaks, or common platform behaviors.</p><h4><strong>7. 1 Finding Work Email Addresses</strong></h4><p>Find corporate platforms or public registers format contact sections predictably. You can hunt for specific email domains tied to names within plain text document formats.</p><ul><li><strong>Dork:</strong> “@targetcompany.com” filetype:txt OR filetype:csv</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1rW_r8P3WO5qAlni6z4f8g.png" /></figure><p><strong>What It Does:</strong> Searches public text or comma-separated files indexed by Google that contain the literal string @targetcompany.com, which frequently yields clean email lists.</p><p><strong>Alternative Search:</strong></p><ul><li><strong>Dork</strong>: “person of interest” filetype:txt inurl:”email.txt”</li></ul><h4>OR</h4><ul><li><strong>Dork</strong>: “John Doe” filetype:txt (inurl:email.txt OR inurl:emails.txt OR inurl:contacts.txt OR inurl:list.txt)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mijb_BicQe_BQiPmibWnXg.png" /></figure><p><strong>What It Does:</strong> Filters search results exclusively to flat, raw text documents (<strong>.txt</strong>) where the file name or URL path contains the string &quot;<strong>email.txt</strong>&quot;, while forcing an exact phrase match on the target’s name inside the file body. This bypasses standard websites to isolate unencrypted contact directories, scraped lead databases, or text-based credential logs that contain the target’s identity.</p><h4><strong>7.2 Open Directory Discovery (The Classic Index)</strong></h4><p>When web servers are misconfigured, they serve a raw folder view called an “Index of” instead of rendering a proper web page. This is a critical vector for discovering forgotten backups and directories.</p><ul><li><strong>Dork:</strong> intitle:”index of” “contacts.txt” OR “employees.db”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIt9gNJaId_I0XXdTJCVVg.png" /></figure><p><strong>What it does:</strong> Finds open directories exposing raw files specifically matching database files or contact text sheets.</p><h4><strong>7.3 Open Directory Sorting</strong></h4><p>Expanding on open folder structures, this variant hunts for broader server operating system listings rather than individual text files.</p><ul><li><strong>Dork:</strong> intitle:”index of” “parent directory”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Tsuj3SodWWyx69DmRtjCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uWvOXC1j5myB47knTy1WaA.png" /></figure><p><strong>What It Does:</strong> Surfaces root-level directories that allow users to navigate upward through the server’s file system framework.</p><h3>Phase 8: Exploiting the robots.txt Boundary for Directory Refinement</h3><p>A sophisticated investigator never assumes a target’s perimeter is completely flat. One of the highest-signal, low-effort reconnaissance vectors involves inspecting the target’s configuration files — specifically their <strong>robots.txt</strong> file.</p><p>[ Because developers sometimes make the mistake of using <strong>robots.txt</strong> as a security control instead of a visibility filter, analyzing it gives you a <strong>custom roadmap</strong> of the <strong>backend directories</strong>, <strong>hidden endpoints</strong>, and <strong>staging areas </strong>that the website owner wants to keep secret. You then use Google Dorks to find the files inside these forbidden directories that Google managed to index anyway ]</p><h4>How to Build Your Dork Strategy</h4><p>You can construct targeted OSINT queries based on the discoveries in a target’s <strong>robots.txt</strong> using common Advanced Google Search Operators:</p><ol><li><strong>Targeting specific paths:</strong> Find files inside disallowed folders.</li></ol><ul><li><strong>Formula</strong><em>:</em> site:target.com inurl: [FolderFromRobots.txt]</li></ul><p><strong>2. Finding specific file types:</strong> Look for sensitive files left in directories.</p><ul><li><strong>Formula</strong><em>:</em> site:target.com filetype:log OR filetype:env OR filetype:txt</li></ul><p><strong>3. Locating login portals:</strong> Discover hidden administrative areas.</p><ul><li><strong>Formula</strong><em>:</em> site:target.com inurl:admin OR inurl:login OR inurl:dashboard</li></ul><h4>Common Endpoints to Look For</h4><p>When you read a target’s <strong>robots.txt</strong>, keep an eye out for these specific <strong>high-value directories</strong> and dork them to see if they are publicly exposed:</p><ul><li><strong>/admin/</strong> or <strong>/login/</strong> (Backend administration panels)</li><li><strong>/backup/</strong> or <strong>/db_backup/</strong> (Unsecured SQL, ZIP, or SQL.GZ files)</li><li><strong>/staging/</strong>, <strong>/dev/</strong>, or <strong>/test/</strong> (Developer environments often lacking authentication)</li><li><strong>/logs/</strong> or <strong>/tmp/</strong> (Files that might leak usernames, error paths, or API keys)</li><li><strong>/config/</strong> (Directories that may expose <strong>.env</strong> or configuration files with plaintext passwords)</li></ul><p>By analyzing the paths an administrator explicitly tells search engines <em>not</em> to crawl, we can harvest highly targeted directory names and feed them right back into customized Google Dorks to find indexing failures.</p><h4>Step 1: Extracting the Map</h4><p>First, we navigate directly to the root domain’s scraper configuration file via the browser: https://targetcompany.com/robots.txt. Suppose the file yields the following restrictions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YAwe3L5U58IXK82zfEhHzg.png" /><figcaption>While Googlebot will respect these rules and avoid actively crawling these paths going forward, legacy exposures or cross-linked resources within these directories may <em>already</em> be sitting inside Google’s database.</figcaption></figure><h4>Step 2: Weaponizing the Disallowed Paths</h4><p>Now, we build highly specialized dork matrices using the explicit paths harvested from the target’s own file. This strips away the guesswork and tells Google exactly where to look.</p><h4>The Staging Leak Probe</h4><ul><li><strong>Dork</strong>: site:targetcompany.com inurl:/dev-staging/ filetype:env OR filetype:yaml OR filetype:conf</li></ul><p><strong>What It Does:</strong> Narrows the search scope strictly to the forbidden <strong>/dev-staging/ </strong>directory, looking for raw environmental files (<strong>.env</strong>), configuration maps, or deployment scripts that leak backend database credentials or API keys.</p><h4>The Archive Integrity Audit</h4><ul><li><strong>Dork</strong>: site:targetcompany.com inurl:/private_archive/ “internal use only” OR “confidential”</li></ul><p><strong>What It Does:</strong> Forces Google to surface any document inside the hidden archive directory that contains sensitive corporate markings, bypassing the main web interface to locate orphaned PDF or DOCX assets.</p><h4>The Log Leak Intercept</h4><ul><li><strong>Dork</strong>: site:targetcompany.com inurl:/secure_logs/ filetype:log OR filetype:txt</li></ul><p><strong>What It Does:</strong> Targets the target’s explicit log storage path to catch system-generated transaction outputs, session tokens, or internal error logs that were indexed before the <strong>robots.txt</strong> restriction was applied.</p><h3>The Intelligence Takeaway</h3><p>This phase demonstrates a critical flaw in traditional perimeter defense: <strong>obscurity is not security</strong>. By analyzing what the “Target-Company” attempted to hide, we refined our search parameters from broad keyword guesses to high-precision structural queries, turning their own defensive configuration into an investigative roadmap.</p><h3>Important OSINT Considerations</h3><ul><li><strong>The </strong><strong>robots.txt fallacy:</strong> Never assume that just because a directory is listed in <strong>robots.txt</strong> as &quot;<strong>Disallow</strong>,&quot; it is hidden from the public. If it is linked elsewhere, Google will index it.</li><li><strong>Legality &amp; Ethics:</strong> Always stick to querying <em>publicly indexed</em> information. Never use dorking to download unauthorized databases, breach firewalls, or exploit the server.</li></ul><h3>Conclusion</h3><p><strong>Google Dorking</strong> is not merely about memorizing a series of search commands; it is an analytical mindset that treats the public web index as a vast, semi-structured relational database. By mastering individual operational primitives and combining them into multi-layered OSINT chains, investigators, security researchers, and threat analysts can rapidly cut through open-source noise.</p><p>True intelligence collection, however, must remain search-engine agnostic. While Google provides unmatched precision across the Western corporate index, true mastery requires knowing when to pivot. Integrating engines like <strong>Yandex</strong> into the analytical matrix breaks through the compliance boundaries, regulatory purges, and regional blind spots that often restrict Western databases. By leveraging Yandex’s unique proximity operators and resilient historical caches, an investigator ensures that what has been scrubbed or deprioritized on one side of the digital landscape can be unearthed on the other.</p><p>Whether you are mapping an enterprise attack surface, tracking a threat actor’s infrastructure, or enumerating a person of interest’s digital footprint, the ability to dynamically manipulate and cross-deck search engine logic remains an indispensable, boundary-defying tool in the digital investigator’s arsenal.</p><h3>Disclaimer</h3><blockquote><strong><em>IMPORTANT LEGAL AND ETHICAL NOTICE:</em></strong><em> This article is published strictly for educational, defensive security, and authorized threat intelligence research purposes. Google Dorking leverages publicly indexed data; however, using these techniques to identify vulnerabilities or exposed data for malicious exploitation, unauthorized access, or harassment is illegal and violates computer fraud regulations globally. Analysts must execute these queries responsibly, respect data privacy boundaries, and ensure that any exposed Personal Identifiable Information (PII) or credentials discovered during an investigation are handled, triaged, and reported through proper, ethical disclosure channels.</em></blockquote><p><strong>Investigator Toolkit:</strong> A pre-configured, searchable list of these dork structures has been uploaded to Google Drive for quick copy-pasting. You can view, save, and import the list directly into your notes by visiting the <a href="https://drive.google.com/file/d/1xj9XWarbt4M88WDw6hWep_rgKP5tBG7K/view?usp=sharing">https://drive.google.com/file/d/1xj9XWarbt4M88WDw6hWep_rgKP5tBG7K/view?usp=sharing</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab129564af38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSINT CHALLENGE: The Cofield Trace]]></title>
            <link>https://preciousvincentct.medium.com/osint-challenge-the-cofield-trace-907cf289e683?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/907cf289e683</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 22:13:09 GMT</pubDate>
            <atom:updated>2026-06-06T22:40:27.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N4pfmQIDwcauxg5mV_4S6Q.jpeg" /><figcaption>OSINT For BEGINNERS</figcaption></figure><p>You are an intelligence analyst. <strong>Arthur Lee Cofield</strong>, a convicted fraudster, has escaped from a federal prison camp in Jesup, Georgia. The FBI has announced a $10,000 reward for information leading to his capture . Your mission is to locate the fugitive.</p><p><strong>The Goal</strong>: Using only open-source intelligence techniques, create a comprehensive “Person of Interest” (POI) profile on Arthur Cofield. The final deliverable should include:</p><ol><li>A verified dossier containing his physical description, known aliases, and identifying marks (tattoos).</li><li>A financial map tracing his $11 million fraud scheme.</li><li>Actionable intelligence on his likely email address, location and potential associates.</li></ol><h3>Part 1: Building the Fugitive’s Dossier</h3><p>This section focuses on identifying the subject and his key identifiers, analysts. The answers are publicly available through news reports and official alerts.</p><h4>Task 1.1: Physical Description &amp; Tattoos</h4><ul><li><strong>Question</strong>: What is Arthur Cofield’s height, weight, place of birth, and most distinguishing physical features (specifically, his facial tattoos)?</li></ul><h4>Task 1.2: Known Aliases (AKAs)</h4><ul><li><strong>Question</strong>: Arthur Cofield uses several aliases. Identify at least three.</li></ul><h4>Task 1.3: Timeline of Incarceration &amp; Escape</h4><ul><li><strong>Question</strong>: From which specific facility did Cofield escape, and on what date was his absence discovered? complete timestamp</li></ul><h4>Task 1.3 Co-conspirators</h4><p>. <strong>Questions</strong>: Who were the co-conspirators named in a seven-count Indictment charged with Cofield for conspiracy to commit bank fraud in violation of 18 U.S.C.</p><h3>Part 2: Tracing the $11 Million Fraud Scheme</h3><p>This is the core of the narrative, analysts — you are to trace the flow of illicit money, which is a key OSINT skill.</p><h4>Task 2.1: Identifying the Victim</h4><ul><li><strong>Question</strong>: Cofield impersonated a specific Hollywood billionaire to steal the money. Who was the victim?</li></ul><h4>Task 2.2: Following the Money Trail</h4><ul><li><strong>Question</strong>: What specific asset did Cofield purchase with the stolen funds, and where is it located?</li></ul><h4>Task 2.3: The Method &amp; The Weapon</h4><ul><li><strong>Question</strong>: How was Cofield in a maximum-security prison able to commit this crime?</li></ul><h3>Part 3: Cofield’s First Arrest</h3><p>Rumored has it that the target has been arrested at an initial stage of their life. Kindly help verify this claimed.</p><h4>Task 1: Cofield first arrested and age</h4><ul><li><strong>Question</strong>: What year was cofield first arrested and age?</li></ul><h3>Part 4: Escape” Attempt, Email Permutation, Last Known Location</h3><p>You have successfully identified the contraband phone, the TextNow VOIP account, and the co-conspirators. The trail has now gone cold. The subject is actively evading law enforcement, and his current whereabouts are unknown.</p><p>However, digital breadcrumbs often remain long after a subject goes dark. Your objective is to reconstruct the subject’s potential email address using pattern analysis, then use that address to uncover his last known physical location through publicly posted reviews.</p><h4>Task 4.1: Previous “Escape” Attempt</h4><ul><li><strong>Question</strong>: This might not be Cofield’s first attempt to evade law enforcement. What suspicious search was found on a previous contraband phone?</li></ul><h4>Task 4.2: Determining his Likely Email Address &amp; Location</h4><ul><li><strong>Question</strong>: What is Cofield’s potential email address and last known location? (Geolocate the target last known location)</li></ul><h3>SUBMISSION REQUIREMENTS &amp; DISCLAIMER</h3><h3>OSINT CHALLENGE: THE TRACE</h3><p>Subject: Arthur Lee Cofield (Fugitive)<br>Challenge Coordinator: CyberShield Mentor</p><h3>DISCLAIMER</h3><h4>IMPORTANT — READ BEFORE PROCEEDING</h4><p>This OSINT challenge is designed strictly for educational and training purposes to develop open-source intelligence collection skills in a controlled, ethical environment.</p><h4>Legal &amp; Ethical Notice:</h4><ol><li><strong>No Real-World Action</strong>: Participants are strictly prohibited from contacting, attempting to locate, surveilling, or communicating with Arthur Lee Cofield, his known associates, family members, or any individual connected to this case.</li><li><strong>Law Enforcement Notification</strong>: If, during this exercise, you encounter information that you reasonably believe represents the current, real-time location of the subject or evidence of imminent criminal activity, you are legally and ethically obligated to immediately report this information to the FBI Tip Line at 1–800-CALL-FBI (1–800–225–5324) or your local field office. Do not take independent action.</li><li><strong>No Interference</strong>: Do not access, probe, scan, or otherwise interact with any systems, accounts, or devices that you do not have explicit legal authorization to access. This includes attempting to log into any email accounts, social media profiles, or financial systems, even if you believe they belong to the subject.</li><li><strong>Historical Focus</strong>: This challenge is designed to use historical, publicly available data from court records, news archives, property records, and similar sources dated prior to May 26, 2026 (the subject’s escape date). Any data dated after this point should be treated with extreme caution and may constitute active intelligence for law enforcement rather than historical OSINT training material.</li><li><strong>No Doxing</strong>: Do not publish, share, distribute, or otherwise disseminate any personal identifying information (PII) about any individual uncovered during this challenge, including but not limited to: names, addresses, phone numbers, email addresses, social media profiles, or financial information.</li><li><strong>Good Faith Use</strong>: This challenge material is provided in good faith for skill development. The challenge coordinator assumes no liability for misuse of these techniques, unauthorized access to systems, unlawful harassment, stalking, or any violation of local, state, or federal laws by participants.</li><li><strong>Educational Purpose Only</strong>: The techniques demonstrated in this challenge are identical to those used by law enforcement, private investigators, and cybersecurity professionals operating within legal boundaries. These techniques become illegal when applied without authorization to living individuals, active cases, or protected systems.</li></ol><p>By submitting a report to this challenge, you affirm that you have conducted your research in compliance with all applicable laws and these ethical guidelines.</p><h3>SUBMISSION REQUIREMENTS</h3><p><strong>All reports must be submitted to</strong>: cybershieldmentor@gmail.com</p><p>Submission Deadline: [Null]</p><p>Subject Line Format: OSINT CHALLENGE: THE TRACE – [YOUR NAME OR TEAM NAME]</p><h3>Required Deliverable 1: Professional Intelligence Report</h3><p>Format: PDF document</p><p><strong>Structure</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2V42CaYp5hzb_rDLUaANBw.png" /></figure><h3>Required Deliverable 2: Entity Graph (Link Analysis Chart)</h3><p>Format: Image file (PNG, JPG, or PDF) embedded within the report or submitted separately</p><h4><strong>Requirements</strong>:</h4><p><strong>Visually map relationships between</strong>:</p><ul><li>Arthur Lee Cofield (central node)</li><li>All dentified aliases (minimum 3)</li><li>Co-conspirators</li><li>The victim</li><li>Physical assets (gold coins, Buckhead mansion)</li><li>Digital artifacts (Samsung phone, TextNow account, reconstructed email)</li><li>Geographic locations (Jesup prison, West Paces Ferry, Idaho gold dealer)</li><li>Timeline events (arrest 2008, fraud 2020, escape 2026)</li></ul><h3>Required Deliverable 3: Screenshot Evidence Package</h3><p>Format: Single PDF document containing multiple screenshots OR a ZIP archive of individual image files</p><h4>Requirements:</h4><ul><li>Minimum 10 distinct screenshots demonstrating key findings</li><li>Each screenshot must include visible timestamp and URL (browser address bar visible)</li><li>Screenshots must be annotated with:</li><li>Red box/circle highlighting the relevant finding</li><li>Brief caption explaining what the screenshot proves</li><li>Phase and task number correlation (e.g., “Phase 1.1 — Facial tattoos from FBI wanted poster”)</li></ul><p>Good hunting, analysts. The trail is cold only if you stop tracing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=907cf289e683" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Digital Ghost: A Comprehensive Guide to Identifying Owners of Covert LinkedIn Accounts]]></title>
            <link>https://preciousvincentct.medium.com/the-digital-ghost-a-comprehensive-guide-to-identifying-owners-of-covert-linkedin-accounts-0ed2c7310468?source=rss-9b988def4bd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ed2c7310468</guid>
            <dc:creator><![CDATA[D4rk_Intel]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 19:32:42 GMT</pubDate>
            <atom:updated>2026-06-04T22:47:18.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_Jv42pwVmT1aQ-AewXVIw.png" /></figure><p>In the world of professional networking, a “covert” LinkedIn account presents a unique paradox: a profile designed to be found professionally, yet stripped of the direct contact details — <strong>email </strong>and <strong>phone number</strong> — that enable immediate real-world identification. You are presented with a digital ghost: a name, a work history, and an education, but no keys to the kingdom.</p><p>This guide moves beyond guesswork. We will explore a layered investigative methodology combining advanced Google searching, specialized browser extensions, email discovery tactics, and data aggregation tools to uncover the person behind the profile. Whether you are a recruiter vetting a candidate, a sales professional seeking a decision-maker, or an individual verifying a connection, these techniques will empower you to bridge the gap between the digital profile and the physical person.</p><h3>Step 1: The 5W1H Framework for Covert LinkedIn Investigation</h3><p>Before touching a single tool, answer these six questions about your <em>investigation itself</em>. This prevents wasted effort and legal missteps.</p><h4>Element______Question_______Investigative_______Implication</h4><ul><li><strong>Who</strong>: <em>Who is the target</em>? _________ Do you have a full name, location, or mutual connections? __________ More identifiers = higher success rate. A common name (“<strong>John Smith</strong>”) requires additional filters (<strong>company, city</strong>).</li><li><strong>What</strong>: <em>What specific data is missing</em>? ____________ Email? Phone? Both? ___________ Email is easier to find via dorks; phone requires aggregators or breach data.</li><li><strong>Where</strong>: <em>Where does the target work</em>? ___________ Where did they study? ____________ Use company domain for email guessing; use university alumni directories.</li><li><strong>When</strong>:<em> When was the profile last active</em>? _______________ When was the job listed? ____________ Recent activity suggests the email is still valid; old jobs may have dead corporate domains.</li><li><strong>Why</strong>: <em>Why do you need to identify them</em>? ____________ Recruiting? Sales? Personal safety? _____________ Defines ethical boundaries. Sales = cold outreach allowed. Stalking = illegal.</li><li><strong>How</strong>: <em>How will you verify identity once you find an email or phone</em>? _________ Cross-reference via reverse lookup tools (Contact-Out, SignalHire, ContactOut, BeenVerified).</li></ul><p><strong>Pro Tip</strong>: Write down your <strong>5W1H </strong>answers before starting. If you cannot articulate a legitimate “Why,” stop — you may be crossing into unethical territory or miss out on your investigation.</p><h3>Step 2: Tool Assemblage — Your Tactical Toolkit</h3><p>Below is every tool mentioned in this guide, organized by function. Bookmark this table.</p><h4>Category_____Tool_____Name_____Best For</h4><ul><li><strong>Google Dorking</strong> &gt; Google Search (manual) &gt; Finding PDFs, spreadsheets with emails</li><li><strong>Email Discovery</strong> &gt;Email Permutator/EmailCrawl &gt; Generating possible email formats</li><li><strong>Browser Extensions</strong> &gt; SignalHire &gt; Reverse lookup from LinkedIn URL</li><li><strong>Browser Extension &gt; </strong>ContactOut &gt; Personal emails (Gmail, Yahoo)</li><li><strong>Email Reverse Lookup </strong>&gt; IntelBase &gt; Behind-The-Mail &gt; Verifying if an email exists</li></ul><h3>Step 3: Passive Reconnaissance with Google Dorks</h3><p>Before using any external tools or alerting the profile owner, begin with passive reconnaissance. If the profile displays their current or past employer and university, you have enough data to execute a successful Google Dork. This method queries Google for specific footprint, file types or website structures that likely contain the target’s email address.</p><p><strong>The Core Logic</strong>: Most companies publish employee directories, press releases, or conference attendee lists in PDFs or spreadsheets. By searching for a company name alongside a file type, you can uncover these documents.</p><h3>Step-by-Step Execution:</h3><ol><li><strong>Identify Unique Identifiers</strong>: From the covert profile, note: POI full name (exact spelling), Current company name, Previous companies, University + graduation year, Location (city/metro area), Job title, and Profile photo (if any).</li><li><strong>Build Your Search String</strong>: Use the following syntax in Google:</li></ol><ul><li>site:companywebsite.com filetype:pdf &quot;Name&quot; Find PDFs (press releases, reports) containing the name</li><li>site:companywebsite.com filetype:xlsx &quot;Company Name&quot; Find spreadsheets (event attendee lists, org charts)</li><li>&quot;Name&quot; &quot;Company Name&quot; &quot;email&quot; Find any webpage with name, company, and the word “email”</li><li>&quot;Name&quot; &quot;University&quot; &quot;email&quot; Find alumni directory entries</li><li>inurl:contact &quot;Full Name&quot; company-domain.com Find contact pages mentioning the person</li><li>&quot;Full Name&quot; @companydomain.com Direct search for the exact email address</li><li>intitle:&quot;Full Name&quot; &quot;companydomain.com&quot; Search page titles containing name and domain</li></ul><p><strong>Pro Tip</strong> — The <strong>@ Operator</strong>: Use the @ symbol to search for email addresses specifically. Google interprets @domain.com as a search for that exact string within any visible text.</p><pre>&quot;Jane Doe&quot; @acmecorp.com</pre><p>If Jane’s email appears anywhere publicly (GitHub commit, forum post, comment section), this search will find it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4Cd5-U_-J6C2B6AlYq0TA.png" /></figure><h3>Step 4: Email Permutation &amp; Automation With EmailCrawl — Guessing Without Public Traces</h3><p>When Google Dorks return nothing, the person’s email likely exists but is not publicly indexed. However, 95% of companies follow predictable email syntaxes. Your job is to guess the correct pattern and then verify it (verification tools covered in step 6).</p><h4>4.1 Identify the Corporate Domain</h4><p>Do not assume www.companyname.com. Find the actual email domain used by employees:</p><p><strong>Method A — Check Other Employees</strong>:<br>Search LinkedIn for <em>any other employee</em> at the same company. If their profile shows an email (some do), note the domain.</p><p><strong>Method B — Check the Company Website</strong>:<br>Go to the company’s “Contact” or “Team” page. Look for any email address. The domain after the @ is your target format.</p><p><strong>Method C — Use </strong><a href="https://hunter.io/"><strong>Hunter.io</strong></a><strong> (Free Tier)</strong>:<br>Go to hunter.io &gt; Domain Search. Enter the company domain. Hunter will show you <em>actual</em> email formats used by other employees at that company.</p><p>Once you have the domain (e.g., acmecorp.com) and the person&#39;s name (e.g., Jane Marie Doe), generate permutations using common patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wcYg6EGX4uF0NHEZ4-HRw.png" /></figure><p><strong>Method D—Automating POI Company Website with EmailCrawl</strong>:</p><p><strong>Tool</strong>: EmailCrawl</p><p><strong>GitHub URL</strong>: <a href="https://github.com/techenthusiast167/EMAIL-CRAWL">https://github.com/techenthusiast167/EMAIL-CRAWL</a></p><h3>What It Does</h3><p>EmailCrawl crawls a target company website and extracts all publicly visible email addresses. By analyzing the email patterns of other employees, you can determine the company’s email syntax and construct your POI’s email address from their name on the covert LinkedIn profile.</p><h4><strong>Filter the output manually</strong>:</h4><p>Remove system emails (info@, admin@, support@, sales@, noreply@). Keep only name-based employee emails (e.g., jdoe@, s.smith@).</p><h4><strong>Identify the email pattern from the remaining results</strong>:</h4><h4>Emails____Found____Pattern</h4><p>jdoe@, ssmith@, ___________mchen@firstinitiallastname@</p><p>john.doe@, sarah.smith@first.last@</p><p>doe.j@, smith.s@last.firstinitial@</p><h4><strong>Apply the pattern to your POI’s name</strong>:</h4><p>Apply the pattern to your POI’s name: If POI is “<strong>Jane Marie</strong>” and the pattern is firstinitiallastname@, the potential email is jmarie@company.com.</p><p>Verify the constructed email using any reverse email lookup tool (see Step 6).</p><p><strong>Note</strong>: Nevertheless, EmailCrawl may occasionally locate the POI’s exact email address directly on the company website, saving you the step of pattern analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycbq8gBgOM5c2-iMcnfCXg.png" /></figure><h3>Why This Works</h3><p><strong>Why This Works</strong>: You are not searching for your POI’s email directly. You are crawling the company to find the pattern used by multiple employees, then applying that pattern to your POI. This method succeeds when Google Dorks return nothing and no employee directory is publicly available.</p><h3>Step 5: The Browser Extension Arsenal (SignalHire &amp; ContactOut)</h3><p>Once you have a LinkedIn URL, passive searching ends, and active tool-based investigation begins. Two Chrome extensions dominate this space: <strong>SignalHire </strong>and <strong>ContactOut</strong>. Both function by scraping their massive databases (SignalHire claims 850M+ profiles) to match a LinkedIn profile to a verifiable email or phone number.</p><h3>SignalHire: The Data Heavyweight</h3><p>SignalHire is designed for reverse lookups. If you have a LinkedIn URL, SignalHire can find the contact info.</p><ul><li><strong>How to use</strong>: Install the Chrome extension, navigate to the covert profile, and click the SignalHire icon.</li><li><strong>Strengths</strong>: Real-time verification ensures emails are active, boasting over 95% accuracy. It allows you to find a profile by phone number if you have one, or vice versa.</li><li><strong>Limitations</strong>: Free plans are extremely limited (often only 5 credits per month), making this a tool for targeted investigations rather than bulk searching.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*bKfa9mtWt604u6Ku5HcFaA.png" /><figcaption>POI details — corporate and personal email addreses mapped out with SignalHire:</figcaption></figure><h3>ContactOut: The Recruiter’s Standard</h3><p>ContactOut is widely considered the industry standard for finding personal emails, used by a significant portion of Fortune 500 recruiters.</p><ul><li><strong>How to use</strong>: After installing the Chrome extension, open the LinkedIn profile. ContactOut overlays a sidebar that reveals email addresses and phone numbers directly on the page.</li><li><strong>Strengths</strong>: It specializes in finding <em>personal</em> emails (Gmail, Yahoo, etc.) rather than just work emails, which is critical if the target uses a personal address for their LinkedIn account.</li><li><strong>Reality Check</strong>: Do not expect a 100% hit rate. Industry experts report a success rate of 30–60% depending on the niche, though ContactOut advertises a database covering 75% of professionals.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*mz_Q3vhIvT2eBnBiSf4Puw@2x.jpeg" /><figcaption>POI details (email addresses &amp; phone numbers pulled out)</figcaption></figure><p><strong>Tactical Note</strong>: Use these extensions in “<strong>Incognito</strong>” or “<strong>Private</strong>” mode if you are concerned about LinkedIn tracking your views, but know that the extensions still require you to be logged into LinkedIn to function.</p><h3>Step 6: Email Deep-Dives (IntelBase/BehindTheMail)</h3><p>Behind the Email is a reverse email lookup tool that reveals a person’s public work history, education, social media accounts, and data breach exposure from an email address you already possess. No validation. No guessing. Just direct profile lookup.</p><p>Once the Chrome extensions have successfully pulled out the POI’s email addresses, the next step is to map the POI’s footprint via reverse email lookup using IntelBase or Behind-The-Email.</p><h3>How to Use It for Your Covert LinkedIn Investigation</h3><p>Use this tool AFTER you have an email address. Do not use it to find or guess an email.</p><h4>Step-by-step:</h4><ol><li>Obtain a candidate email using Google Dorks, EmailCrawl, or SignalHire.</li><li>Go to <a href="https://intelbase.is/">https://intelbase.is</a> / <a href="https://behindtheemail.com/">https://behindtheemail.com/</a></li><li>Paste the email into the search box.</li><li>Review the returned profile.</li><li>Compare the profile data (employer, job title, education) to your covert LinkedIn profile.</li><li>If the data matches, you have confirmed the email belongs to your POI.</li></ol><h4>Example:</h4><ul><li>You have a candidate email: sarah.jenkins@gmail.com</li><li>IntelBase/Behind the Email returns: “Senior Product Designer at Parallel Labs” + “RISD”</li><li>Your covert LinkedIn profile shows: Senior Product Designer at Parallel Labs, RISD graduate</li><li><strong>Conclusion</strong>: Confirmed. Same person.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4e6GKYKp0XwOZlFYxkhcMA.png" /></figure><h3>Step 7: The “Photo” Shortcut (Liveness Detection)</h3><p>Many investigators overlook the most powerful identifier: the profile photo.</p><ul><li><strong>Google Reverse Image Search</strong>: Download the profile picture (use a screenshot if download is disabled). Upload it to Google Images. If the person uses the same photo on Twitter, Facebook, or a company “About Us” page, you have a direct link to their verified identity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H6eXjDhiOq_LC3jM3ZRhWw.png" /></figure><ul><li><strong>Cross-Platform Search</strong>: A unique photo (not a stock image) used on a “covert” LinkedIn profile suggests the user does not mind being seen, just not contacted directly. Finding that photo on a corporate website often reveals their direct work email listed publicly.</li></ul><h3>The Ethical Hard Stop: Legal and Platform Risks</h3><p>Before you execute this plan, you must understand the boundaries. LinkedIn’s User Agreement explicitly prohibits scraping or automated data collection. Using extensions like ContactOut or SignalHire puts your account in a gray area; while widely used by recruiters, aggressive use (e.g., scraping 1000 profiles a day) can lead to a permanent IP or account ban.</p><p>Furthermore, using found email addresses for unsolicited marketing (spam) violates CAN-SPAM and GDPR laws. If you use these techniques to identify someone, your subsequent communication must be professional, transparent, and relevant.</p><h3>Summary Execution Checklist</h3><p>If you are facing a covert profile right now, execute this chain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*50vu-q0EWnqvVeVpCrIpjQ.png" /><figcaption>SignalHire Reverse Email Linked To A User LinkedIn Account</figcaption></figure><ol><li><strong>The Dork</strong>: Google &quot;Full Name&quot; &quot;Company Name&quot; filetype:pdf. Customize further to fit your investigation.</li><li><strong>The Extension</strong>: Install SignalHire or ContactOut.</li></ol><ul><li>Open the LinkedIn profile.</li><li>Click the extension.</li><li>Copy the revealed email.</li></ul><p>3. <strong>The Validation</strong>: If no email appears, use the photo. Go to Google Images &gt; Search by image.</p><p>4. <strong>The Association</strong>: Take any email you find (or guess) and put it into SignalHire’s reverse lookup to see <em>all</em> social accounts attached to that person.</p><p>5.<strong> The Verification &amp; Footprints</strong>: Use IntelBase or BehindTheMail to confirm the email exist and tied to other social footprints</p><p>By combining these technical layers — Boolean logic, professional scrapers, and image recognition — you effectively dissolve the anonymity of a “covert” profile, transforming a digital ghost into a verifiable contact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ed2c7310468" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>