Repository navigation
OSINT Open Source Intelligence Basic General Guide
Source and visual review: November 17, 2026. This is a source-reviewed reference, not an executed investigation. No tools were installed, accounts created, targets contacted, identifier APIs queried or reports submitted. Check installed versions and provider terms before use.
Companion directory: Curated Awesome OSINT List maps additional public-record, imagery, geographic, transport and evidence services into scoped investigation workflows.
Master reference for OSINT - methodology, a categorized tool reference, investigation VM setup, per-identifier investigation procedures, evidence handling, and legal/OPSEC guidance. This is the foundational/general guide; ../Tradecraft/osint-threat-intel.md (linked above) is the advanced, threat-intelligence-focused counterpart. Within this folder, OSINT_CHEATSHEET.md is the condensed command-only version of this same material.
Twelve sections moving from OSINT theory (the intelligence cycle, framework categories) through tool reference (organized by identifier type: email, username, domain, phone), VM setup (Buscador, Trace Labs, Tsurugi), per-identifier investigation procedures and full workflows, then evidence preservation, abuse reporting, OPSEC, and legal considerations - ending in a quick-reference cheat sheet.
Plan scoped research, select sources, distinguish leads from verified findings and report evidence with its limitations. No single tool covers every identifier or jurisdiction.
- Learning OSINT methodology and the intelligence cycle for the first time
- Setting up an OSINT investigation VM or looking up which tool covers a given identifier type
- Reference for legal/OPSEC requirements before starting any investigation
- Introduction to OSINT
- OSINT Methodology & Framework
- Core OSINT Tools
- OSINT by Category
- OSINT VM Setup
- Investigation Procedures by Identifier Type
- Investigation Workflows
- Evidence Preservation & Chain of Custody
- Abuse Reporting Workflow
- OSINT Best Practices & OPSEC
- Legal & Ethical Considerations
- Resources & Learning
Open Source Intelligence (OSINT) refers to the collection and analysis of information gathered from publicly available sources. OSINT is used across multiple domains including:
- Cybersecurity: Threat intelligence, vulnerability research, and attack surface mapping
- Law Enforcement: Investigations, missing persons cases, and criminal intelligence
- Corporate Security: Competitor analysis, due diligence, and brand protection
- Journalism: Investigative reporting and fact-checking
- Personal Security: Background checks and reputation monitoring
- Publicly accessible data from the internet, social media, public records
- Public availability describes access; it does not establish accuracy, consent, lawful processing or permission to republish.
- Collect within documented authority, purpose and retention limits; do not bypass access controls.
- Distinguish existing-record lookups, DNS requests and direct target interaction.
Figure 1 โ Original conceptual cycle based on Bellingcat's toolkit and the source-verification guide; no real investigation is depicted.
1. Requirements Definition
โโ> Define objectives and intelligence questions
2. Source Identification
โโ> Identify relevant data sources
3. Data Collection
โโ> Gather information from sources
4. Data Processing
โโ> Organize, filter, and prepare data
5. Analysis
โโ> Connect dots, identify patterns
6. Dissemination
โโ> Present findings in actionable format
7. Feedback
โโ> Refine approach based on results
The OSINT Framework categorizes investigations by:
- Username - Social media presence, online accounts
- Email Address - Account enumeration, breach data
- Domain Name - DNS records, WHOIS, website info
- IP Address - Geolocation, network information
- Phone Number - Carrier lookup, social media links
- Person - Public records, social profiles
- Company - Corporate records, employees, infrastructure
- Cryptocurrency - Wallet tracing, scam database lookups
Figure 2 โ Original scope model informed by theHarvester's activity definitions. Querying a provider still discloses the query to it; classification depends on selected options and modules.
Examples are illustrative. example.test, example.invalid and documentation IPs are placeholders; replace them only with an approved target for the specific activity. A discovered related asset is not automatically in scope. Record exact versions, settings, outcomes and errors. No network examples were executed.
# Inspect installed options and available sources first.
theHarvester -h
# Bounded provider lookup; placeholder requires an approved replacement.
theHarvester -d example.test -l 50 -b crtsh,certspotter- Use Case: Domain-related leads from provider datasets. DNS and direct actions require separate scope.
-
Version note: Current upstream uses Python 3.14 and
uv; packaged versions can differ. Old hard-codedgoogle, LinkedIn and Twitter source assumptions are unreliable. Use the installed catalog and source outcome records. - Limit: A source error, partial result and successful zero-result query are different outcomes.
# Search for username across social media platforms
sherlock username
# Export results to file
sherlock username -o results.txt
# Search specific sites
sherlock username --site GitHub- Use Case: Candidate profiles from the installed site database. Coverage and false positives change; a username match is not identity verification.
- GitHub: https://github.com/sherlock-project/sherlock
# Candidate profile discovery; compare coverage and errors
maigret username
# Username permutations; may expand collection scope
maigret username --permute
# Full export with reports
maigret username --pdf --html --folderoutput ./username_results/- Use Case: Candidate profiles and public profile data; site coverage changes.
-
Flags: The option reference distinguishes
--permutefrom--use-disabled-sites; the latter enables disabled definitions and may increase false positives. - GitHub: https://github.com/soxoj/maigret
# Username enumeration - alternative/complement to Sherlock & Maigret
python blackbird.py --username username- Use Case: Candidate username/email profiles; coverage overlaps other tools.
-
Identity/launch: The old p1ngul1n0 URL redirects to antoniaci/blackbird. Source instructions use
python blackbird.py; a globalblackbirdwrapper is not assumed. Review optional AI/export data flows before enabling them. - GitHub: https://github.com/antoniaci/blackbird
# Email OSINT & breach hunting
h8mail -t research@example.invalid
# Provider keys use named configuration fields, not a universal bare key.
h8mail -t research@example.invalid -c /path/to/protected-h8mail-config.ini
# Export results to CSV
h8mail -t research@example.invalid -o breach_results.csv- Use Case: Authorized breach-exposure review. Provider support and permitted use vary; minimize secrets collected or exported. A hit does not prove current compromise.
- GitHub: https://github.com/khast3x/h8mail
# Check if email is used on different sites
holehe research@example.invalid
# Filter positive service responses; errors and false positives remain possible
holehe research@example.invalid --only-used- Use Case: Possible registration inferred from service responses, not authoritative ownership. This directly interacts with services; review scope and request effects.
- GitHub: https://github.com/megadose/holehe
# Phone number OSINT
phoneinfoga scan -n +1234567890- Use Case: Number-format, carrier and external-source leads; scanners require configuration.
- Status: Upstream declares the project stable but unmaintained. Provider compatibility is unverified.
- Limit: No precise device location or guaranteed owner/social-account identification.
- GitHub: https://github.com/sundowndev/phoneinfoga
# Full-featured web reconnaissance framework
recon-ng
[recon-ng][default] > workspaces create target_company
[recon-ng][target_company] > marketplace search
# Inspect a selected module's behavior and dependencies before installing.
[recon-ng][target_company] > modules search- Use Case: Comprehensive reconnaissance automation
- Modules: DNS, WHOIS, breaches, social media, more
- GitHub: https://github.com/lanmaster53/recon-ng
# Review the selected major version's help before constructing a run.
amass -h- Use Case: Asset discovery using provider information and active reconnaissance.
-
Version note: Current source uses module path
github.com/owasp-amass/amass/v5. Match the documentation to the installed release; old v4 install lines and historicenum -passive/-bruterecipes are not universal. - Scope: Review DNS behavior, sources and direct actions. Passive provider queries still disclose the target string.
# Fast subdomain discovery
subfinder -d example.test
# With specific sources
subfinder -d example.test -sources virustotal,shodan
# Silent output for piping
subfinder -d example.test -silent- Use Case: Subdomain enumeration for attack surface mapping
- GitHub: https://github.com/projectdiscovery/subfinder
Use the ProjectDiscovery binary/documentation, which is distinct from the Python HTTPX library. These probes contact targets directly; technology labels are heuristic and do not prove vulnerabilities.
# Probe live hosts and fingerprint web stack
httpx -l subdomains.txt -td -server -title -asn -status-code
# Single target with technology detection
echo example.test | httpx -td -server -title
# Pipeline: subfinder โ httpx
subfinder -d example.test -silent | httpx -td -server -title -asn- Use Case: Live host probing, tech stack fingerprinting, ASN lookup
- Pairs With: subfinder โ httpx pipeline for attack surface mapping
- GitHub: https://github.com/projectdiscovery/httpx
# Retrieve archive-index URL candidates; not a complete history
echo example.test | waybackurls > historical_urls.txt
# Combined with subfinder for full historical surface
subfinder -d example.test -silent | waybackurls | sort -u- Use Case: Historical URL candidates, with incomplete coverage. An archived URL does not establish current availability or permission to request it.
- GitHub: https://github.com/tomnomnom/waybackurls
# One-shot ASN, network range, and abuse contact lookup
asn 8.8.8.8
asn example.test- Use Case: Quick ASN identification, abuse email discovery for reporting
- GitHub: https://github.com/nitefood/asn
# Incredibly fast web crawler for OSINT
python photon.py -u https://example.test -o output -l 1 -t 2
# Extract specific data types
python photon.py -u https://example.test --dns --keys- Use Case: URL extraction, JavaScript files, endpoint discovery
-
Scope: Crawling contacts target resources; bound depth, concurrency and destinations. The inspected parser has no
--emailsoption; extraction is part of its behavior. - GitHub: https://github.com/s0md3v/Photon
# Automated OSINT collection
python3 sf.py -h- Use Case: Module-based collection; modules can be passive or active and may require keys.
-
Launch: Source instructions use
python3 ./sf.py -l 127.0.0.1:5001for a local UI. Inspect selected modules before scanning; a globalspiderfootwrapper is distribution-specific. - GitHub: https://github.com/smicallef/spiderfoot
# Archive a webpage as a single self-contained HTML file (evidence preservation)
monolith https://example.test -o evidence_$(date -u +%Y%m%dT%H%M%SZ).html
# Remove scripts from the saved document; -j does not execute JavaScript.
monolith -j https://example.test -o archived.html-
Use Case: Single-file capture with omissions/transformations to document. Monolith has no built-in JavaScript engine; current source offers optional browser-assisted
-B, which is version-specific and can make additional requests. Capture is not automatically complete or authenticated. - GitHub: https://github.com/Y2Z/monolith
# CLI screenshot capture for evidence
cutycapt --url=https://example.test --out=screenshot_$(date +%Y%m%d_%H%M%S).png- Use Case: Headless screenshot capture, evidence documentation
# Submit pages to the Wayback Machine for archiving
waybackpy --url "https://example.test" --save- Use Case: Archive submission discloses the URL and may publish page content. Review disclosure/approval first. Archive copies corroborate context, not authorship or truth.
- GitHub: https://github.com/akamhy/waybackpy
- Use Case: Visual link analysis, relationship mapping
- Features: Provider-dependent transforms; identifiers may be sent to external services.
- Data Sources: DNS, WHOIS, social media, public records
- Plans: Check current Maltego plans; legacy Classic/XL labels are not current purchase guidance.
- Website: https://www.maltego.com
-
Use Case: The maintained opsdisk fork discovers and optionally downloads public documents. It delegates metadata analysis to other tools; the old
-f results.htmlrecipe describes a different implementation.
# Analyze already acquired local documents without uploading them.
exiftool -r ./approved-documents/- Limit: Editable author/software/path fields may describe a template or processing system rather than a creator.
# Website fingerprinting
whatweb example.test
# Aggressive mode
whatweb example.test -a 3- Use Case: Identify web technologies, CMS, frameworks
site:example.test filetype:pdf
site:example.test inurl:admin
site:example.test intitle:"index of"
"@example.test" site:pastebin.com
site:*.example.test -www
- Shodan (https://shodan.io) - Search engine for Internet-connected devices
- Censys (https://censys.com) - Internet-wide scanning and analysis
- GreyNoise (https://greynoise.io) - Internet background noise intelligence
- Hunter.io (https://hunter.io) - Email finder and verification
- Have I Been Pwned (https://haveibeenpwned.com) - Breach notification service
- CriminalIP (https://www.criminalip.io) - Cyber threat intelligence with IP/domain reputation
- Netlas (https://netlas.io) - Internet-wide scanning, similar to Shodan/Censys
- FullHunt (https://fullhunt.io) - Attack surface discovery and monitoring
- ZoomEye (https://www.zoomeye.ai) - Cyberspace search engine; coverage and access are provider-dependent.
- AbuseIPDB (https://www.abuseipdb.com) - Crowdsourced IP abuse database
- SecurityTrails (https://securitytrails.com) - DNS history, passive DNS, subdomain data
- WhoisXML API (https://whoisxmlapi.com) - WHOIS data + DNS intelligence
- DNSDumpster (https://dnsdumpster.com) - Free DNS recon and research
- urlscan.io (https://urlscan.io) - Search existing scans or submit new ones. Submission visits the URL; visibility settings affect disclosure. Do not submit private/tokenized URLs without approval.
- crt.sh (https://crt.sh) - Certificate transparency log search
# Certificate transparency - find related domains via shared certs
curl -s "https://crt.sh/?q=%25.example.test&output=json" | jq '.[].name_value' | sort -u- Sherlock - Username search across platforms
- Social-Analyzer - Profile analysis across social networks
- X/social-platform interfaces - Verify current official search/export/API access; old TweetDeck/TweetBeaver workflows are not a verified current collection path.
- Instagram OSINT tools (various)
- LinkedIn - Review permitted access and automation limits; do not assume scraping is allowed.
- Username correlation across platforms
- Profile picture reverse image search
- Connection mapping and network analysis
- Metadata extraction from posts
- Geolocation from photos and posts
- Google Earth Pro - Historical imagery, elevation data
- Google Street View - Ground-level imagery
- Yandex Maps - Alternative mapping (strong in Russia/Eastern Europe)
- Baidu Maps - China-focused mapping
- Bing Maps - Microsoft's mapping service
- EXIF data extractors - Photo metadata analysis
- Reverse image search (Google, Yandex, TinEye)
- Shadow analysis for time/location verification
- Landmark identification
- EXIF GPS coordinate extraction
- Cross-referencing multiple map sources
- Tor Browser - Access .onion sites
- I2P - Alternative anonymous network
- Tails OS - Privacy-focused live operating system
- Ahmia.fi - .onion search engine
- Index coverage and service status vary. Check the operator's current documentation and approved environment; no search index is complete.
- Hunchly - Web capture tool, not a dark-web search engine.
- Company registries (state/national business databases)
- SEC EDGAR - US public company filings
- LinkedIn - Employee enumeration
- Glassdoor / Indeed - Company reviews, salaries
- Crunchbase - Startup and investment data
- ZoomInfo / RocketReach - Contact information databases
- PACER - Federal court records
- State court systems - Civil and criminal records
- Property records - County assessor databases
- Corporate registrations - Secretary of State databases
- Professional licenses - State licensing boards
- Have I Been Pwned - Email breach notification
- DeHashed - Breach search engine (paid)
- LeakPeek / Snusbase - Breach databases
- IntelX - Data breach search
- Leak-Lookup - Breach search engine
- Pastebin monitoring - Automated paste site scanning
- ChainAbuse (https://www.chainabuse.com) - Public reports to corroborate; allegations do not establish fraud or address ownership.
- CryptoScamDB (https://cryptoscamdb.org) - Known crypto scams and malicious addresses
- blockchain.info - Bitcoin blockchain explorer
- Etherscan (https://etherscan.io) - Ethereum blockchain explorer
- BlockCypher - Multi-chain explorer
- OXT / Breadcrumbs - Bitcoin cluster analysis tools
- Creator: Michael Bazzell (IntelTechniques)
- Based on: Ubuntu
- Status: Historical distribution; do not rely on unsupported images for current live work.
- Use Case: General OSINT investigations
- Download: Buscador was discontinued by IntelTechniques; no longer available. Consider Trace Labs OSINT VM or Tsurugi Linux as alternatives.
- Purpose: Search and rescue operations
- Tools: Curated set for finding missing persons
- Community: Active Trace Labs community
- Download: https://docs.tracelabs.org/vm/vm-introduction
- Focus: Digital forensics and OSINT
- Features: DFIR/OSINT tooling; verify the selected image and installed versions rather than assuming an update cadence.
- Website: https://csilinux.com
- Focus: DFIR (Digital Forensics and Incident Response), with a dedicated OSINT profile
- Documented release (checked 2026-11-17): LAB 26.03, based on Ubuntu 24.04.3 LTS
- OSINT Tools: Comprehensive suite included; confirm the current installed versions before use
- Website: https://tsurugi-linux.org; verify release downloads and platform documentation.
- Platform-specific setup and practical workflows: Tsurugi Linux OSINT Guide
Use a supported guest/host release, verify the image through publisher checksums/signatures and record snapshot date and network mode. A snapshot aids recovery, not anonymity or evidence authentication.
Minimal Debian/Ubuntu starting packages, subject to the selected release:
sudo apt update
sudo apt install python3 python3-venv pipx git curl jqOS upgrades and native build dependencies belong in an approved maintenance plan rather than a blind investigation setup.
Install one selected tool at a time using a publisher package, dedicated venv, pipx or reviewed container as supported upstream. Do not force system-wide pip changes in externally managed environments.
| Tool | Primary installation reference |
|---|---|
| theHarvester |
README: current source uses uv sync; check the required Python and uv run theHarvester -h. |
| Sherlock |
Upstream documents pipx install sherlock-project; verify sherlock --help. |
| Recon-ng | Project/wiki; do not assume a similarly named PyPI package is official. |
| SpiderFoot | Source instructions; separate its environment and inspect modules. |
| Amass | Current documentation must match the major version. |
| Photon, Maigret, h8mail, Holehe | Follow the source links above and record dependencies/provider configuration. |
| PhoneInfoga | Unmaintained project; current compatibility is unverified. |
Record version/revision, environment and installation results. Directly invoking a venv interpreter makes activation optional. A venv separates packages; it does not sandbox untrusted code.
Follow Monolith, CutyCapt and WaybackPy instructions matching the selected version. Record renderer/browser versions and output limitations. Install Python clients in their own environment. Local capture and public archive submission have different disclosure effects.
Select DNS/RDAP clients, curl, jq, ExifTool, media tools and hash utilities according to the plan. Verify distribution package names. Port scanners, high-speed network scanners and recursive crawlers are active tools, not requirements for reading public records.
The former bulk installer mixed system pip changes, nested checkouts and unpinned releases, then printed success without verifying tools. Use a reviewed installation manifest:
| Record | Required context |
|---|---|
| Identity | Canonical publisher/repository |
| Selected build | Release tag or full commit |
| Environment | OS, runtime and dependency lock/record |
| Method | Publisher package / venv / reviewed container |
| Local check | Version/help/import results, including errors |
| Approved behavior | Modules, destinations, limits and output path |
Automate only after one tool's setup works on the chosen platform. A successful --help does not establish reliable results or software security.
Figure 3 โ Original synthetic entity-resolution model; see the source-verification guide. No real identities or personal records are depicted.
# Find services where this email is registered
holehe research@example.invalid --only-usedUse only accounts/data you are authorized to assess. HIBP API v3 email search requires an appropriate key/subscription, descriptive user agent and rate-limit/error handling. URL-encode identifiers and protect keys from shell history/logs. Empty results and request failures do not establish no exposure.
h8mail may query providers or local data when configured; its ordinary target invocation is not inherently local-only. Do not test recovered credentials.
Hunter's verifier documentation describes provider output and limits. Verification can interact with mail servers; it does not prove a person's ownership or that a message was read. Minimize identifiers shared with third parties. No test email is required by this guide.
If you have the original email source:
- Extract full headers from your email client
- Analyze the
Received:chain for routing path - Start with headers added by the receiving system you trust, then walk toward earlier hops only while the trust boundary is supported. The bottom-most
Receivedline may be forged; it is not automatically the sender's IP. - Review receiver-generated SPF / DKIM / DMARC results and alignment; success does not establish content safety or an individual author.
- Consider forwarding, mailing lists and legitimate envelope/header differences before treating a mismatch as spoofing proof.
Primary references: SMTP trace fields, RFC 5321 ยง4.4 and Authentication-Results trust boundaries, RFC 8601. Preserve the original message; avoid uploading private headers.
Tools: Prefer approved local analysis. Third-party analyzers receive what you upload.
Extract the email's domain and proceed to the Domain Investigation Procedure.
# One-shot ASN, network range, and abuse contact
asn 192.0.2.10Use these as distinct sources: RDAP is registration/allocation metadata; any commercial geolocation provider supplies an estimate, not a device's physical location. These examples use a public demonstration IP, not a customer asset.
# RDAP registration information; HTTPS bootstrap redirects, not geolocation.
curl --fail --silent --show-error --location \
--proto '=https' --proto-redir '=https' --max-redirs 5 --max-time 30 \
'https://rdap.org/ip/8.8.8.8' | jq
# Optional provider geolocation estimate; access, quotas, license and fields may vary.
# The queried address is disclosed to the provider.
curl --fail --silent --show-error --max-time 30 \
'https://ipinfo.io/8.8.8.8/json' | jqIf a lookup fails or returns no result, record the error as unverified, not "no registration" or "no location". Check vendor terms before client use, and enable Bash pipefail when adapting these pipelines into automated evidence collection.
# AbuseIPDB
curl -s "https://api.abuseipdb.com/api/v2/check?ipAddress=192.0.2.10&maxAgeInDays=90" \
-H "Key: YOUR_KEY" -H "Accept: application/json" | jq
# Shodan host details
curl -s "https://api.shodan.io/shodan/host/192.0.2.10?key=YOUR_KEY" | jq# Resolver request about a documentation IP, not ownership/geolocation proof.
dig -x 192.0.2.10 +shortPort discovery contacts a destination. Use a separate active-assessment plan with explicit hosts, rates and timing; a public-record lookup does not authorize scanning. Record ASN, source/date, uncertainty and contact roles without equating allocation with the responsible person.
Start with authoritative RDAP and the registrar's verified abuse channel. ICANN explains RDAP's replacement of WHOIS; WHOIS availability varies. Registration, hosting and content responsibility are different roles. Redacted registration is not evidence of wrongdoing.
Record query source/time, registrar and its advertised reporting channel; verify that provider's reporting requirements.
dig +short example.test A
dig +short example.test MX
dig +short example.test TXT
dig +short example.test NSsubfinder -d example.test -silent -o subs.txt
cat subs.txt | httpx -td -server -title -asn# Historical URLs
echo example.test | waybackurls > historical_urls.txt
# Certificate transparency - find related domains
curl -s "https://crt.sh/?q=%25.example.test&output=json" | jqwhatweb https://example.testPrefixes below are non-exhaustive hints, not validators or proof of chain/owner. Validate the full address and checksum using chain-specific documentation. EVM addresses can occur on multiple chains; record network and asset explicitly.
| Cryptocurrency | Address Format |
|---|---|
| Bitcoin | Starts with 1, 3, or bc1
|
| Ethereum | Starts with 0x followed by 40 hex chars |
| Litecoin | Legacy L/M and SegWit ltc1; historical formats can overlap other chains |
| Monero | Standard/subaddress hints 4/8; integrated/network-specific forms differ |
| Solana | Base58-encoded 32-byte account address (public key or PDA); length alone is not validation |
Primary format references: Litecoin addresses, Monero address forms, Solana accounts. These describe encoding, not identity.
Public reports supply leads, including mistaken/stale claims. Absence of a report does not clear an address.
- ChainAbuse: https://www.chainabuse.com/address/ADDRESS
- CryptoScamDB: https://cryptoscamdb.org/search
Bitcoin:
curl -s "https://blockchain.info/rawaddr/ADDRESS?limit=50" | jqEthereum (Etherscan API): v2 transaction endpoint. This normal-transaction query is not every possible activity type; check pagination and token/internal endpoints.
# Etherscan v2 uses chainid (1 = Ethereum mainnet); review access, pagination and response status.
curl -s "https://api.etherscan.io/v2/api?chainid=1&module=account&action=txlist&address=ADDRESS&apikey=YOUR_KEY" | jqExamine:
- Total received / sent
- Number of transactions
- First and last transaction timestamps
- Current balance
- Linked addresses (transaction graph)
For significant addresses:
- Record observed transactions with chain, hash, block, time and confirmation state.
- Distinguish native transfers, tokens, fees and contract/internal activity; paginate before claiming totals.
- Treat exchange labels and clustering as provider claims with source/date, not established identities.
- Consider custodial wallets, CoinJoin, contract routers and alternative explanations. A transaction edge does not prove common ownership.
Record:
- Full address (case-sensitive for some chains)
- Blockchain type and explorer URL
- Total value transacted (in crypto and approx. fiat)
- Scam database results (with screenshots)
- Transaction screenshots with timestamps
phoneinfoga scan -n "+12025550123"The local library parses numbering-plan metadata, not current subscribers or devices. libphonenumber's FAQ distinguishes validity from assignment/reachability and explains portability limits.
import phonenumbers
from phonenumbers import carrier, geocoder
pn = phonenumbers.parse("+12025550123")
print(carrier.name_for_number(pn, 'en'))
print(geocoder.description_for_number(pn, 'en'))Line-type/carrier labels may be stale or incomplete, particularly after number portability. VoIP has legitimate uses and does not establish fraud. Scanner results need provider context; no universal VoIP or owner-detection guarantee applies.
- Search the number on major social platforms (some allow phone search)
- Truecaller (manual web check)
- Reverse phone lookup services
The numeric heading is retained for navigation; it is historical, not guaranteed coverage. Choose a bounded approved site set.
maigret target_username --pdf --html --folderoutput ./username_results/The numeric heading is historical. Enumeration supplies candidate matches, not identity verification.
sherlock target_username --csvpython blackbird.py --username target_usernameFor each discovered profile:
- Bio/Description: contact info, links, claims
- Profile Photo: reverse image search (Google, Yandex, TinEye)
- Post History: timeline, posting patterns, time zones
- Connections: friends, followers, group memberships
- Activity: frequency, language patterns, devices
Document legitimate purpose and authority/consent, minimize bystander data and define access/retention limits. Username reuse, names, photos and timestamps can mislead. Annotate relationships with supporting evidence and alternative explanations.
1. Start with Known Information
โโ> Name, email, username, location
2. Username Enumeration
โโ> Sherlock / Maigret / Blackbird across social platforms
3. Email Investigation
โโ> Holehe (potential registration indicators)
โโ> H8mail (breach data)
โโ> theHarvester (associated domains)
4. Social Media Deep Dive
โโ> Profile analysis
โโ> Connection mapping
โโ> Content timeline review
5. Phone Number (if available)
โโ> PhoneInfoga for carrier/validation
โโ> Social media association
6. Geolocation Analysis
โโ> Photo EXIF data
โโ> Check-ins and tagged locations
โโ> Google Maps / Street View verification
7. Compile Timeline
โโ> Chronological activity mapping
โโ> Pattern identification
8. Report Generation
โโ> Document findings
โโ> Visualize relationships (Maltego)
1. Initial Reconnaissance
โโ> Authoritative RDAP / available WHOIS context
โโ> DNS enumeration
2. Subdomain Discovery
โโ> Amass (comprehensive)
โโ> Subfinder (provider-backed discovery)
โโ> Certificate transparency logs (crt.sh)
3. Live Host Probing
โโ> httpx (tech stack + ASN)
โโ> WhatWeb (technology fingerprint)
4. Email Harvesting
โโ> theHarvester (emails from domain)
โโ> LinkedIn (employee enumeration)
5. Web Application Analysis
โโ> Photon (crawling & endpoint discovery)
โโ> waybackurls (historical data)
โโ> Wayback Machine (page history)
6. Employee Enumeration
โโ> Permitted public/company records within access rules
โโ> Email pattern identification
โโ> Social media presence
7. Infrastructure Mapping
โโ> Shodan / Censys (exposed assets)
โโ> IP ranges and netblocks
โโ> Cloud service identification
8. Breach Data Review
โโ> Have I Been Pwned
โโ> DeHashed / breach databases
โโ> Pastebin monitoring
9. Report & Visualization
โโ> Attack surface map
โโ> Risk assessment
โโ> Maltego relationship diagram
1. IOC (Indicator of Compromise) Collection
โโ> IP addresses, domains, hashes
2. Passive DNS Analysis
โโ> Historical resolution data
โโ> Related infrastructure
3. Malware Analysis Research
โโ> Sandbox reports (ANY.RUN, Hybrid Analysis)
โโ> VirusTotal intelligence
4. Attribution Hypotheses (not established identities)
โโ> Dark web forums
โโ> Paste sites
โโ> Social media monitoring
5. Vulnerability Intelligence
โโ> CVE databases
โโ> Exploit-DB
โโ> GitHub repository searches
6. Infrastructure Correlation
โโ> Shared hosting analysis
โโ> SSL certificate tracking (crt.sh)
โโ> Registration context; privacy services alone do not attribute actors
7. Reporting & Sharing
โโ> IOC feeds
โโ> Threat reports
โโ> MISP/STIX format sharing
1. Triage & Authorization
โโ> Document the complaint
โโ> Verify legal authority to investigate
โโ> Assign case ID (YYYY-NNN-TYPE)
2. Initial Identifier Collection
โโ> Email addresses, phone numbers, domains, URLs
โโ> Crypto wallet addresses
โโ> Social media handles
โโ> Bank account / payment processor info (if applicable)
3. Per-Identifier Investigation (parallel)
โโ> Emails โ holehe, h8mail, HIBP
โโ> Phones โ phoneinfoga, carrier lookup
โโ> Domains โ whois, dig, subfinder + httpx, waybackurls
โโ> IPs โ asn, geolocation, AbuseIPDB
โโ> Usernames โ maigret, sherlock, blackbird
โโ> Crypto โ scam databases, blockchain explorers
4. Infrastructure Correlation
โโ> Shared hosting, SSL certs (crt.sh)
โโ> Common WHOIS data
โโ> Reused images / templates
โโ> Cross-referenced indicators
5. Evidence Preservation
โโ> Capture necessary pages and document omissions
โโ> Capture relevant views, minimizing bystander data
โโ> Hash retained originals and log handling
โโ> Public archive submission only after disclosure review
6. Report Generation
โโ> Executive summary
โโ> Per-identifier findings
โโ> Evidence inventory with hashes
โโ> Abuse contacts compiled
7. Abuse Reporting
โโ> Registrar takedown request
โโ> Hosting provider notification
โโ> Email/social platform reports
โโ> IC3 submission (if applicable)
8. Follow-Up & Closure
โโ> Track response from each report
โโ> Re-verify takedowns
โโ> Update case file
โโ> Archive case
- Preserve necessary original acquisitions and hash them promptly with SHA-256.
- Record collector, source URL/identifier, UTC time, time source, tool/version, options, access context, request failures and omissions.
- Log every transfer, access and transformation; work on copies and hash derived outputs separately.
- Store protected originals and backups with access controls and encryption appropriate to sensitivity.
- Recheck integrity against a trusted manifest. A hash detects byte changes relative to that manifest; it does not prove when, where or by whom content was published.
Figure 4 โ Original conceptual handling model, informed by NIST's Secure Hash Standard and source verification. Hashes support integrity comparisons; provenance and interpretation require additional evidence.
Capture only necessary authorized material. HTML and screenshots are complementary views, not complete replicas of every interaction. Keep the original URL, redirects, capture timestamps, renderer/version and known missing resources with the files. Use UTC file naming:
# Illustrative network capture: requires approved destination and disclosure scope.
stamp=$(date -u +%Y%m%dT%H%M%SZ)
monolith https://example.test -o "evidence_${stamp}.html"
cutycapt --url=https://example.test --out="screenshot_${stamp}.png"
# Local hash manifest; inspect that the intended files exist first.
sha256sum "evidence_${stamp}.html" "screenshot_${stamp}.png" > "hashes_${stamp}.txt"Review output and exit status; preserve partial/failure states separately. Protected storage and custody records must protect the hash manifest too. A screenshot alone does not establish the original publication time.
Preserve a local, access-controlled capture first, and record the requested URL, redirects, UTC capture time, collector/tool version, result, known omissions and SHA-256. Review the content for personal or restricted data, client rules, terms and authorization before any third-party submission. Use a public archive only when its visibility, retention and disclosure risks are acceptable and authorized. Public saves may create permanent, shareable URLs; dynamic, authenticated or blocked content can be incomplete. Screenshots and HTML captures preserve different views, and neither guarantees a complete reproduction. Treat archive availability as corroborating context, not forensic certification or proof of authorship.
Public archive submission is a separate disclosure decision; verify capture completeness and preserve the original local capture and its handling record.
A consistent directory structure for each investigation:
~/OSINT_Cases/
โโโ CASE-ID/
โโโ case_info.md # Metadata, objectives, authorization
โโโ case_notes.md # Investigation notes, timeline
โโโ evidence_log.md # Chain of custody table
โโโ evidence/
โ โโโ screenshots/
โ โโโ archives/ # monolith HTML, wget mirrors
โ โโโ files/ # downloaded artifacts
โ โโโ hashes/ # SHA256 manifests
โโโ reports/
โ โโโ interim/
โ โโโ final/
โ โโโ abuse_reports/
โโโ raw_data/
โโโ email/
โโโ domain/
โโโ ip/
โโโ phone/
โโโ username/
โโโ crypto/
YYYY-NNN-TYPE
Examples:
- 2025-001-PHISHING
- 2025-002-INVESTMENT_FRAUD
- 2025-003-TECH_SUPPORT_SCAM
- 2025-004-ROMANCE_SCAM
The following rows are synthetic layout examples. Truncated strings are not valid SHA-256 values; actual manifests need full 64-character hexadecimal digests and a reference to the protected source record.
| Timestamp (UTC) | Type | Description | SHA256 | Source/Tool |
|---|---|---|---|---|
| 2025-01-15 10:30:00 UTC | Archive | Scam homepage capture | abc123def... | monolith |
| 2025-01-15 10:31:42 UTC | Screenshot | Login page | 9f8e7d6... | cutycapt |
When evidence supports a report, use the responsible provider's published process. Separate observed facts from suspicion and request review rather than promising a takedown. Reports may disclose sources, identities or sensitive content; minimize and approve the information shared.
From your investigation, compile contacts for:
- Domain registrar published abuse channel, checked against authoritative RDAP and the provider's site
- Hosting/content provider verified abuse process; an ASN allocation or CDN address alone does not identify the responsible origin
- Email provider abuse address (Gmail, Outlook, Proton, etc.)
- Upstream ISP (if identifiable separately from hosting)
- Social media platform abuse/trust & safety contacts
- Payment processor (if money is involved - Stripe, PayPal, crypto exchange)
Each report should include:
โ
Observed incident type, clearly separating facts from allegations
โ
Specific URLs, IPs, and domains
โ
Timeline of observed activity (with UTC timestamps)
โ
Evidence excerpts/references in the format the recipient requests; a hash alone is not usable incident content
โ
Your contact information for follow-up
โ
Statement that you are reporting in good faith
| Recipient Type | Channel |
|---|---|
| Domain Registrar | Verified official reporting portal/address; do not guess an abuse mailbox |
| Hosting Provider | Verified provider reporting channel, with service role documented |
| Email Provider | Provider's abuse form (Gmail: https://support.google.com/mail/contact/abuse) |
| Social Media | Platform-specific reporting flow |
| Cloudflare-fronted | https://www.cloudflare.com/abuse/form |
In your case file, record:
- Date/time submitted (UTC)
- Recipient
- Method (email, web form, API)
- Reference/ticket number returned
- Files referenced or attached
- Follow-up date based on the recipient's published process
- Follow published response expectations; 48โ72 hours is not a universal service commitment.
- Use a concise follow-up through the same official channel, referencing the ticket.
- Escalate according to that provider's process; registrar, registry, host and CDN have different powers.
- For CDN-fronted content, submit the relevant URL and supported evidence without assuming the CDN is the origin. No attempt to uncover/bypass an origin is required.
Follow the official IC3 FAQ and current complaint form at https://www.ic3.gov/. Include accurate identifiers, incident chronology, payment details/losses and victim information as requested and permitted.
IC3 does not accept attachments or collect supporting evidence through the complaint form. Retain original records securely; a PDF report/hash-manifest upload is not a required submission step. Save the submitted complaint/confirmation when offered. Filing does not guarantee contact, investigation or recovery.
Verify the official jurisdiction and current route before submitting personal data.
| Location | Reporting route |
|---|---|
| USA | IC3 and FTC ReportFraud according to incident type |
| England, Wales, Northern Ireland | Report Fraud replaced Action Fraud on December 4, 2025 |
| Scotland | Police Scotland; the Report Fraud announcement directs Scottish reports there |
| Canada | Canadian Anti-Fraud Centre |
| Australia | Scamwatch for scam reporting; check incident-specific police/cybercrime channels |
| EU countries | Local/national police. Europol says it does not take public crime reports directly; a CERT is a different incident-response role |
Choose network controls from the threat model and organizational policy. A VPN shifts trust to its operator; Tor protects only applications configured to use it. Neither guarantees anonymity or makes out-of-scope requests acceptable. Do not rotate addresses to evade rate limits or access restrictions. Keep the guest/host patched and separate case data from personal activity.
Use an approved dedicated profile or isolated environment. Review extensions, downloads, scripts and active content according to the task. Changes can break rendering and affect evidence; record them. Tor Browser's publisher guidance warns that external apps and plugins can bypass its protections.
Use only approved accounts and access methods allowed by the platform and engagement. Avoid personal-account contamination. Do not assume invented personas, virtual numbers or burner accounts are permitted or conceal an operator. No account creation, impersonation or contact with people is required here.
There is no universal โVPN + Tor = maximum anonymityโ recipe. Login identity, query strings, document callbacks and reporting contact details can reveal context even when network routing is protected. Decide what each recipient may receive and retain; minimize identifiers and do not upload confidential evidence to arbitrary tools.
โ
Use consistent folder/file naming conventions
โ
Timestamp all collected data
โ
Maintain chain of custody for evidence
โ
Document sources for all information
โ
Use tools like Hunchly or Maltego for case management
โ
Capture necessary views with context and timestamps; minimize irrelevant personal data
โ
Capture locally first; public archive submission requires a separate disclosure decision
โ
Record video for dynamic content
โ
Log all commands and queries used
โ
Maintain detailed investigation notes
โ
Use write-blockers where applicable to physical media acquisition; they do not authenticate an online page
โ
Calculate and verify file hashes
โ
Store multiple copies in different locations
โ
Encrypt sensitive investigation data
โ
Follow proper chain of custody procedures
โ
Cross-reference information from multiple sources
โ
Verify with primary sources when possible
โ
Be aware of misinformation and fake profiles
โ
Check dates and timestamps for relevance
โ
Consider cultural and linguistic context
โ
Document confidence levels for findings
- The CFAA statute and DOJ charging policy concern unauthorized computer access and related conduct; public availability is not blanket legal permission.
- Keep access within authorized scope and do not bypass authentication or access controls.
- DOJ charging policy guides federal prosecutors; it is not immunity from civil claims, other laws or other jurisdictions.
- The GDPR text governs applicable personal-data processing, including some public-source data.
- Territorial scope under Article 3 depends on establishment and specified offering/monitoring activities, not simply every EU resident's data everywhere.
- Assess lawful basis, minimization, retention, security and rights/exceptions in context (including Articles 5, 6 and 17); erasure is not an unconditional rule to delete all evidence.
- Respect website terms of service
- Many sites prohibit scraping or automated collection
- Terms, technical restrictions and law are separate questions. Review the applicable contract/access rules; no universal claim that every ToS breach is a CFAA crime follows.
- Respect Privacy: Don't collect information beyond investigation scope
- Do No Harm: Consider potential consequences of your investigation
- Be Transparent: Understand who you're working for and why
- Legal Compliance: Follow all applicable laws and regulations
- Professional Standards: Maintain objectivity and accuracy
๐ซ Hacking or unauthorized access to systems
๐ซ Social engineering or pretexting
๐ซ Doxxing or harassment
๐ซ Accessing private/protected information
๐ซ Circumventing security measures
๐ซ Impersonation for malicious purposes
๐ซ Sharing intelligence for illegal purposes
โ Cybersecurity threat intelligence โ Law enforcement investigations (with proper authority) โ Corporate due diligence โ Investigative journalism โ Academic research โ Missing persons cases (authorized) โ Fraud prevention โ Background checks (with consent)
๐ซ Stalking or harassment ๐ซ Identity theft ๐ซ Corporate espionage (illegal methods) ๐ซ Blackmail or extortion ๐ซ Unauthorized private investigation ๐ซ Doxxing for retaliation ๐ซ Invasion of privacy without justification
Resource links are starting points, not endorsements or guarantees of live availability, pricing or legal suitability. No course, service or commercial subscription was purchased or evaluated during this review.
- Website: https://inteltechniques.com
- Books: "Open Source Intelligence Techniques" series
- Training: Online courses and workshops
- Podcast: "The Privacy, Security, & OSINT Show"
- Website: https://www.tracelabs.org
- Focus: OSINT for missing persons
- Competitions: CTF-style OSINT challenges
- Community: Active Discord and forums
- SEC487: Open Source Intelligence Gathering and Analysis
- Focus: Professional OSINT techniques
- Certification: GOSI (GIAC Open Source Intelligence)
- Udemy: Various OSINT courses
- Cybrary: Free cybersecurity training including OSINT
- TCM Security: Practical OSINT courses
- TryHackMe: OSINT learning paths and challenges
-
"Open Source Intelligence Techniques" by Michael Bazzell
- Check the publisher's current edition; older tool instructions can age.
-
"OSINT Handbook" by i-intelligence
- Free resource from i-intelligence, a Switzerland-based private OSINT training firm (not a government intelligence agency, despite the name)
- Practical methodologies and tools - current edition at osinthandbook.com
-
"Social Engineering: The Science of Human Hacking" by Christopher Hadnagy
- Relevant for understanding social OSINT
-
"The Art of Invisibility" by Kevin Mitnick
- Privacy and anonymity techniques
- Reddit: r/OSINT, r/SocialEngineering
- Discord: Trace Labs, OSINT Curious, various security servers
- Twitter: #OSINT hashtag, follow practitioners
- Sector035.nl: OSINT articles and weekly newsletter
- OSINT Framework: https://osintframework.com
- TraceLabs CTF: Missing persons OSINT competitions
- Sector035: Regular OSINT exercises and quizzes
- Bellingcat's Online Investigation Toolkit: Tool reviews and guides; inclusion is not endorsement
- Geolocating Images: Various challenge sites
- OSINTQuiz: Twitter-based challenges
- OSINT Exercises (Gralhix): https://gralhix.com/list-of-osint-exercises/
- CTFtime.org: OSINT categories in CTF competitions
- HackTheBox: Some machines include OSINT elements
- TryHackMe: Dedicated OSINT rooms
- Bellingcat: https://www.bellingcat.com
- IntelTechniques by Michael Bazzell: https://inteltechniques.com/blog
- Sector035: https://sector035.nl
- OSINT Curious: https://osintcurio.us
- Aware Online: https://www.aware-online.com
- OSINT Framework: https://osintframework.com
- Awesome OSINT: https://github.com/jivoi/awesome-osint
- Bellingcat resources/toolkit: https://bellingcat.gitbook.io/toolkit/
- InVID Verification Plugin: Video verification
- FotoForensics: Image forensics and analysis
- Jeffrey's Exif Viewer: EXIF data extraction
- TinEye: Reverse image search
- Internet Archive / Wayback Machine: https://archive.org
- Archive.today: https://archive.is
- Perma.cc: https://perma.cc
Apply the version, scope, privacy and evidence qualifications in the full sections above. These examples are separate operations, not a run-all script.
# theHarvester - Email harvesting
theHarvester -d example.test -l 50 -b crtsh,certspotter
# Holehe - Email registration check
holehe research@example.invalid --only-used
# H8mail - Breach hunting
h8mail -t research@example.invalid# Sherlock - Username search
sherlock username
# Maigret - Advanced username OSINT
maigret username
# Blackbird - Additional coverage
python blackbird.py --username username# Amass - inspect installed major version before using its workflow
amass -h
# Subfinder - Fast subdomain discovery
subfinder -d example.test
# Subfinder โ httpx pipeline
subfinder -d example.test -silent | httpx -td -server -title -asn
# theHarvester - Domain emails & subdomains
theHarvester -d example.test -l 50 -b crtsh,certspotter
# crt.sh - Certificate transparency
curl -s "https://crt.sh/?q=%25.example.test&output=json" | jq '.[].name_value' | sort -u# ASN + abuse contact
asn 192.0.2.10
# Provider estimate, not a device/person location; query is disclosed.
curl --fail --silent --show-error "https://ipinfo.io/192.0.2.10/json" | jq
# Reverse DNS
dig -x 192.0.2.10 +short# Photon - Fast web crawler
python photon.py -u https://example.test
# waybackurls - Historical URL discovery
echo example.test | waybackurls
# Wget - Website mirroring
wget -r -l 2 -P output/ https://example.test# Selected-page capture; inspect output and preserve source context
monolith https://example.test -o evidence_$(date +%Y%m%d_%H%M%S).html
# Screenshot
cutycapt --url=https://example.test --out=screenshot.png
# Public archive submission is a separate disclosure decision; see procedure.
# Hash manifest
sha256sum evidence_*.html screenshot_*.png > evidence_hashes.txt# Recon-ng - Framework
recon-ng
workspaces create target
marketplace search
modules search
# SpiderFoot - Auto OSINT
python3 sf.py -hPrimary references are linked beside corrected behavior and diagrams. Tool/provider commands were checked against public documentation and source, not installed or exercised. Interfaces, dependencies, supported sources, rate limits and plans can change independently; retain the selected release/revision with any future record.
This review does not certify runtime compatibility, exhaust every external link, establish legal authority for a particular investigation or guarantee evidentiary admissibility. Account matches, geolocation estimates, reputation labels, certificate/DNS links, metadata and blockchain clusters require corroboration. Repeated mirrors of one underlying record are not independent sources.
This OSINT guide incorporates knowledge, tools, and methodologies from the following individuals and organizations:
- IntelTechniques OSINT resources
- Buscador VM
- Open Source Intelligence Techniques book series
- OSINT VM for search & rescue
- Community-driven OSINT competitions
- Christian Martorella - theHarvester
- Sherlock Project Team - Sherlock
- Steve Micallef - SpiderFoot
- Tim Tomes - Recon-ng
- OWASP Team - Amass
- s0md3v - Photon
- ProjectDiscovery Team - Subfinder, Nuclei, httpx
- Soxoj - Maigret
- Blackbird contributors - project currently hosted at antoniaci/blackbird
- khast3x - H8mail
- megadose - Holehe
- sundowndev - PhoneInfoga
- tomnomnom - waybackurls
- nitefood - asn CLI tool
- Y2Z - Monolith
- akamhy - WaybackPy
- Bellingcat - Open source investigative journalism
- OWASP - Open Web Application Security Project
- Paterva - Maltego development
- Sector035 - OSINT education and resources
- OSINT Framework: Comprehensive tool directory
- Awesome OSINT: Curated list on GitHub
- OSINT Curious: Community project and podcast
โ ๏ธ IMPORTANT: Legal and Ethical Use Only
This OSINT guide is provided for:
โ
Educational purposes
โ
Authorized security research
โ
Legal investigations with proper authority
โ
Ethical intelligence gathering
PROHIBITED USES:
๐ซ Stalking, harassment, or doxxing
๐ซ Unauthorized access to systems or data
๐ซ Violations of privacy laws or regulations
๐ซ Any illegal activities
ALWAYS:
- Obtain proper authorization before conducting investigations
- Respect privacy and data protection laws
- Follow website terms of service
- Act ethically and responsibly
- Consider the impact of your investigations
The authors and contributors of this guide assume no liability
for misuse of the information or tools described herein.
When in doubt, consult with legal counsel.
This OSINT guide is part of the ULTIMATE CYBERSECURITY MASTER GUIDE maintained by Pacific Northwest Computers (PNWC).
To contribute:
- Submit issues or pull requests on GitHub
- Share new tools, techniques, or resources
- Provide feedback on existing content
- Help maintain tool links and accuracy
Repository: https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE
Last Updated: November 17, 2026
Maintained by: Pacific Northwest Computers (PNWC)
Use this knowledge responsibly and ethically.
- README.md - OSINT section index
- OSINT_CHEATSHEET.md - Quick-reference companion
- ../Tradecraft/osint-threat-intel.md - Advanced OSINT and threat intel
- Playbook/README.md - Structured investigation workflows
- ../OPSEC/OPSEC_guide.md - OPSEC practices for OSINT investigators
๐ Source: OSINT/OSINT_GUIDE.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Open Source Intelligence (OSINT)
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics