Domain 1Recon & ReportingCORE

OSINT Techniques

Comprehensive guide to Open Source Intelligence (OSINT) techniques, tools, workflows, and methodologies for penetration testing and the OSCP exam.

Domain: Domain 1: Reconnaissance & Reporting•Updated: 2026-09-01
#osint#open-source-intelligence#passive-recon#research

OSINT Techniques

Table of Contents

  1. What is OSINT?
  2. OSINT Source Categories
  3. OSINT Workflow
  4. Key OSINT Principles
  5. OSINT Automation Tools
  6. Legal Boundaries of OSINT
  7. OSINT for OSCP
  8. Building an OSINT Checklist
  9. Attack Chain Position
  10. OSCP Exam Tips

What is OSINT?

Definition

OSINT (Open Source Intelligence) is the process of collecting, analyzing, and converting publicly available information into actionable intelligence. The term originated in military and intelligence communities but has become a cornerstone of cybersecurity and penetration testing.

Official Definition (US Government): “Intelligence produced from publicly available information that is collected from open sources, readily accessible to the general public, and does not require any special access clearances.”

Scope of OSINT

OSINT encompasses any information that is:

  • Publicly available: Accessible without special permissions or credentials
  • Legally obtainable: Can be collected without violating laws or terms of service
  • From open sources: Published, broadcast, or otherwise made available to the public

OSINT in Cybersecurity

In the context of penetration testing and cybersecurity, OSINT is used to:

Purpose Description
Target Profiling Build a comprehensive profile of the target organization
Attack Surface Mapping Identify all publicly exposed assets and services
Credential Discovery Find exposed usernames, emails, and passwords
Technology Identification Determine the technologies and platforms in use
Infrastructure Discovery Map out the target’s network and cloud infrastructure
Employee Profiling Identify key personnel and their digital footprints
Vulnerability Research Find known vulnerabilities affecting the target’s technology stack

OSINT vs Other Intelligence Types

Intelligence Type Source Accessibility Example
OSINT Open/public sources Anyone can access News articles, public records
HUMINT Human sources Requires human contact Interviews, informants
SIGINT Signals intelligence Requires technical capability Intercepted communications
GEOINT Geospatial intelligence Requires satellite/aerial data Satellite imagery
CYBINT Cyber intelligence Requires network access Dark web monitoring

OSINT Source Categories

Understanding the categories of OSINT sources helps you systematically cover all potential information channels.

1. Search Engines

Search engines are the most fundamental OSINT tool. They index billions of web pages and can reveal information that is not immediately obvious.

Google Dorking (Advanced Search Operators)

Google Dorking uses advanced search operators to find specific types of information:

Operator Description Example
site: Search within a specific site site:target.com
filetype: Search for specific file types site:target.com filetype:pdf
inurl: Search for URLs containing text site:target.com inurl:admin
intitle: Search for page titles site:target.com intitle:"index of"
intext: Search for text in page body site:target.com intext:"password"
ext: Search for file extensions site:target.com ext:php
cache: View cached version cache:target.com
related: Find similar sites related:target.com
- Exclude terms site:target.com -www
* Wildcard site:target.com "employee * directory"

Common Google Dorks for Reconnaissance

# Find exposed directories
site:target.com intitle:"index of"

# Find configuration files
site:target.com ext:conf OR ext:cfg OR ext:ini OR ext:env

# Find backup files
site:target.com ext:bak OR ext:old OR ext:backup OR ext:sql

# Find login pages
site:target.com inurl:login OR inurl:admin OR inurl:dashboard

# Find exposed documents
site:target.com filetype:pdf OR filetype:doc OR filetype:docx OR filetype:xlsx

# Find error messages
site:target.com intext:"error" OR intext:"warning" OR intext:"fatal"

# Find subdomains
site:*.target.com

# Find employee information
site:target.com "employee" OR "staff" OR "team"

# Find API endpoints
site:target.com inurl:api

# Find git repositories
site:target.com inurl:.git

# Find sensitive data
site:target.com intext:"confidential" OR intext:"internal" OR intext:"secret"

Other Search Engines

Search Engine URL Special Features
Google https://www.google.com Largest index, advanced operators
Bing https://www.bing.com Different indexing, sometimes unique results
DuckDuckGo https://duckduckgo.com Privacy-focused, no filter bubble
Yahoo https://search.yahoo.com Legacy index, sometimes different results
Yandex https://yandex.com Strong in Eastern Europe, unique indexing
Baidu https://www.baidu.com Strong in China, Chinese-language content

2. Social Media

Social media platforms are rich sources of information about organizations and individuals.

LinkedIn

LinkedIn is one of the most valuable OSINT sources for organizational intelligence:

What you can find:

  • Employee names and positions
  • Organizational structure
  • Technology stack (from job descriptions and profiles)
  • Company size and growth
  • Recent hires and departures
  • Skills and certifications of employees

OSINT techniques:

# Search for employees
"target company" AND ("developer" OR "engineer" OR "admin")

# Search for technology mentions
"target company" AND ("AWS" OR "Azure" OR "GCP")

# Search for job postings
"target company" jobs

# Search for former employees
"target company" past employee

Twitter / X

What you can find:

  • Company announcements
  • Employee opinions and complaints
  • Technology discussions
  • Incident reports
  • Internal tool mentions

OSINT techniques:

# Search for company mentions
from:targetcompany

# Search for employee mentions
from:@employee_handle

# Search for technology mentions
"target company" AND ("AWS" OR "Docker" OR "Kubernetes")

# Search for incident reports
"target company" AND ("outage" OR "incident" OR "breach")

GitHub and GitLab

Code repositories are goldmines for OSINT:

What you can find:

  • Source code and configurations
  • API keys and credentials (accidentally committed)
  • Infrastructure as Code (revealing architecture)
  • Internal tool names and project codenames
  • Technology stack details
  • Development practices and workflows

OSINT techniques:

# Search GitHub for organization
# https://github.com/orgs/target/repositories

# Search for credentials
site:github.com "target.com" "password"
site:github.com "target.com" "api_key"
site:github.com "target.com" "secret"

# Search for configuration files
site:github.com "target.com" filetype:env
site:github.com "target.com" filetype:yaml
site:github.com "target.com" filetype:json

# Search for internal tools
site:github.com "target.com" "internal"
site:github.com "target.com" "private"

Other Social Platforms

Platform Value for OSINT What to Look For
Facebook Company pages, employee profiles Organization info, employee names
Instagram Visual content, location data Office locations, events, technology
YouTube Video content, tutorials Internal tools, training materials
Reddit Forums, discussions Employee opinions, technical details
Stack Overflow Q&A, code snippets Technology stack, internal issues
TikTok Short-form video Office culture, technology mentions

3. Public Records

Government and public records provide structured, verified information.

Business Registration Records

What you can find:

  • Company registration details
  • Registered address
  • Directors and officers
  • Shareholder information
  • Filing history
  • Financial statements (for public companies)

Sources:

  • Secretary of State business registries (US)
  • Companies House (UK)
  • Local business registration databases

Domain Registration Records

See WHOIS and Domain Research for detailed coverage.

Government Filings

What you can find:

  • SEC filings (10-K, 10-Q, 8-K)
  • Patent applications
  • Trademark registrations
  • Regulatory compliance documents
  • Litigation records

Sources:

4. DNS Records

DNS records reveal infrastructure details and relationships.

Key DNS record types for OSINT:

Record Type Purpose OSINT Value
A IPv4 address Server locations, hosting providers
AAAA IPv6 address IPv6 infrastructure
CNAME Alias Service relationships, CDN usage
MX Mail server Email infrastructure, hosting
NS Name server DNS hosting, infrastructure
TXT Text records SPF, DKIM, verification tokens
SOA Start of Authority DNS admin contact, serial numbers
SRV Service location Internal service discovery
PTR Reverse DNS Server identification

Commands:

# Query all DNS records
dig target.com ANY

# Query specific record types
dig target.com A
dig target.com MX
dig target.com TXT
dig target.com NS

# Reverse DNS lookup
dig -x 10.10.10.1

# Zone transfer attempt
dig axfr target.com @ns1.target.com

5. Code Repositories

Beyond GitHub and GitLab, other code hosting platforms can reveal information.

# Search for specific code patterns
"target.com" language:python
"target.com" language:javascript
"target.com" language:bash

# Search for specific files
"target.com" filename:config
"target.com" filename:docker-compose
"target.com" filename:Makefile

# Search for specific content
"target.com" "AWS_ACCESS_KEY"
"target.com" "DATABASE_URL"
"target.com" "SECRET_KEY"

Other Code Platforms

Platform URL Notes
GitHub https://github.com Largest code hosting platform
GitLab https://gitlab.com Self-hosted and cloud options
Bitbucket https://bitbucket.org Atlassian ecosystem
SourceForge https://sourceforge.net Legacy open source hosting
Gitea https://gitea.com Lightweight self-hosted option

6. Forums and Blogs

Technical forums and blogs often contain detailed information about organizations and their technology.

Technical Forums

What to look for:

  • Help requests mentioning the target
  • Discussions about target’s products
  • Employee participation in forums
  • Technical details shared in troubleshooting

Common forums:

  • Stack Overflow
  • Reddit (r/netsec, r/cybersecurity, etc.)
  • Hacker News
  • Security-focused forums (Full Disclosure, Bugtraq)
  • Vendor-specific forums

Blogs

What to look for:

  • Technical blog posts from the target
  • Employee personal blogs
  • Conference presentations
  • Write-ups and case studies

Search techniques:

# Search for target blogs
site:target.com/blog
site:target.com/news
site:target.com/tech

# Search for employee blogs
"target company" blog
"target company" "technical blog"

# Search for conference presentations
"target company" site:slideshare.net
"target company" site:speakerdeck.com

7. Job Postings

Job postings are an underutilized but valuable OSINT source.

What you can find:

  • Technology stack (from required skills)
  • Organizational structure (from department mentions)
  • Growth areas and strategic direction
  • Internal tool names and project codenames
  • Security practices and requirements
  • Cloud provider preferences
  • Development methodologies

Search techniques:

# Search for job postings
site:target.com/careers
site:target.com/jobs
site:linkedin.com/jobs "target company"
site:indeed.com "target company"

# Search for specific technologies
"target company" AND ("AWS" OR "Azure" OR "GCP") site:linkedin.com/jobs
"target company" AND ("Kubernetes" OR "Docker") site:linkedin.com/jobs

8. News and Media

News articles and media coverage provide historical and current information.

What you can find:

  • Company history and milestones
  • Security incidents and breaches
  • Technology acquisitions and partnerships
  • Executive changes
  • Financial performance
  • Regulatory issues

Sources:

  • News aggregators (Google News, Bing News)
  • Industry-specific publications
  • Press release databases
  • Business journals

Search techniques:

# Search for news
"target company" site:news.google.com
"target company" breach
"target company" security incident
"target company" data leak

# Search for press releases
"target company" "press release"
"target company" "announces"

OSINT Workflow

A structured workflow ensures comprehensive and efficient OSINT collection.

flowchart TD
    A[Define Objective] --> B[Identify Target]
    B --> C[Gather Initial Intel]
    
    C --> C1[Domain Research]
    C --> C2[WHOIS Lookup]
    C --> C3[DNS Enumeration]
    
    C1 --> D[Search Engine Recon]
    C2 --> D
    C3 --> D
    
    D --> D1[Google Dorking]
    D --> D2[Bing Search]
    D --> D3[DuckDuckGo]
    
    D1 --> E[Social Media Analysis]
    D2 --> E
    D3 --> E
    
    E --> E1[LinkedIn]
    E --> E2[GitHub]
    E --> E3[Twitter/X]
    E --> E4[Other Platforms]
    
    E1 --> F[Public Records]
    E2 --> F
    E3 --> F
    E4 --> F
    
    F --> F1[Business Records]
    F --> F2[Government Filings]
    F --> F3[Patent/Trademark]
    
    F1 --> G[Code Repository Analysis]
    F2 --> G
    F3 --> G
    
    G --> H[Forum and Blog Research]
    H --> I[News and Media Review]
    I --> J[Job Posting Analysis]
    
    J --> K[Correlate Findings]
    K --> L{Actionable Intel?}
    
    L -->|Yes| M[Document and Report]
    L -->|No| N[Expand Search Scope]
    
    N --> D
    M --> O[Transition to Next Phase]

Workflow Phases Explained

Phase 1: Define Objective

Before starting OSINT collection, clearly define:

  • What information are you looking for?
  • What is the scope of the target?
  • What are the legal and ethical boundaries?
  • What is the timeline for completion?

Phase 2: Identify Target

Gather basic target information:

  • Domain names
  • IP addresses
  • Organization name
  • Key personnel
  • Known services and applications

Phase 3: Gather Initial Intel

Start with structured, technical sources:

  • WHOIS records
  • DNS records
  • Domain registration information
  • Certificate transparency logs

Phase 4: Search Engine Recon

Use search engines to discover publicly available information:

  • Google dorking for sensitive files
  • Search for subdomains and related domains
  • Look for exposed directories and files
  • Find employee information

Phase 5: Social Media Analysis

Analyze social media platforms for:

  • Employee profiles and connections
  • Company announcements and updates
  • Technology mentions and discussions
  • Internal tool references

Phase 6: Public Records

Search public records for:

  • Business registration details
  • Government filings
  • Patent and trademark information
  • Litigation records

Phase 7: Code Repository Analysis

Analyze code repositories for:

  • Source code and configurations
  • Accidentally committed credentials
  • Infrastructure as Code
  • Internal tool names

Phase 8: Forum and Blog Research

Search forums and blogs for:

  • Technical discussions
  • Help requests
  • Employee participation
  • Technical details

Phase 9: News and Media Review

Review news and media for:

  • Company history
  • Security incidents
  • Technology changes
  • Executive changes

Phase 10: Job Posting Analysis

Analyze job postings for:

  • Technology stack
  • Organizational structure
  • Growth areas
  • Internal projects

Phase 11: Correlate Findings

Combine all collected information to:

  • Identify patterns and relationships
  • Build a comprehensive target profile
  • Identify potential attack vectors
  • Prioritize findings by value

Phase 12: Document and Report

Document all findings:

  • Record sources and timestamps
  • Organize by category
  • Highlight actionable intelligence
  • Prepare for next phase

Key OSINT Principles

1. Start Broad, Then Narrow

Begin with broad searches to understand the target’s landscape, then narrow down to specific areas of interest.

flowchart LR
    A[Broad Search] --> B[Identify Areas of Interest]
    B --> C[Focused Search]
    C --> D[Deep Dive]
    D --> E[Actionable Intel]

2. Verify Information

Always verify OSINT findings from multiple sources:

Verification Method Description
Cross-referencing Check multiple sources for the same information
Temporal analysis Check if information is current or outdated
Source credibility Assess the reliability of the source
Logical consistency Check if information makes sense in context

3. Document Sources

Always record the source of each piece of information:

## Finding: Exposed API Key

- **Source**: GitHub repository (https://github.com/target/repo)
- **Date Found**: 2026-09-01
- **Verification**: Cross-referenced with company documentation
- **Confidence**: High
- **Actionable**: Yes - can be used for API access

OSINT must stay within legal boundaries:

  • Only access publicly available information
  • Do not bypass authentication
  • Do not violate terms of service
  • Do not collect personal data beyond what is publicly available
  • Follow applicable privacy laws (GDPR, CCPA, etc.)

5. Automate Where Possible

Use automation tools to scale OSINT collection:

Task Manual Automated
WHOIS lookup whois target.com SpiderFoot, Recon-ng
DNS enumeration dig target.com Sublist3r, Amass
Social media search Manual browsing Maltego, SpiderFoot
Search engine dorking Manual queries Custom scripts
Code repository search Manual browsing TruffleHog, GitLeaks

6. Think Like the Target

Consider what information the target would want to keep private and where it might be exposed:

  • What would an employee accidentally expose?
  • What would a developer accidentally commit?
  • What would a sysadmin leave configured publicly?
  • What would a marketing team publish?

OSINT Automation Tools

SpiderFoot

SpiderFoot is an open-source OSINT automation tool that integrates with numerous data sources.

Installation

# Clone the repository
git clone https://github.com/smicallef/spiderfoot.git
cd spiderfoot

# Install dependencies
pip install -r requirements.txt

# Run SpiderFoot
python sf.py

Usage

# Start the web interface
python sf.py --listen 0.0.0.0:5001

# Command line usage
python sf.py --target target.com --modules all --socket 5001

# Export results
python sf.py --target target.com --modules all --export json

Key Features

Feature Description
Multi-source Integrates with 100+ data sources
Automated Runs scans automatically
Exportable Results in JSON, CSV, HTML, PDF
Modular Enable/disable specific modules
API REST API for integration

Maltego

Maltego is a commercial OSINT and data visualization tool.

Key Features

Feature Description
Visual Graph Entity relationship visualization
Transforms Pre-built data collection modules
Entity Types Domains, IPs, emails, people, etc.
Integration Connects to multiple data sources
Reporting Built-in reporting capabilities

Common Transforms

Transform Purpose
Domain -> DNS Records Extract DNS records from domain
Domain -> WHOIS Get WHOIS information
Email -> Social Media Find social media accounts
IP -> Geolocation Get IP location data
Person -> Email Find email addresses

Recon-ng

Recon-ng is a full-featured web reconnaissance framework.

Installation

# Clone the repository
git clone https://github.com/lanmaster53/recon-ng.git
cd recon-ng

# Install dependencies
pip install -r requirements.txt

# Run Recon-ng
./recon-ng

Usage

# Start Recon-ng
./recon-ng

# Set target
set domain target.com

# Run modules
modules load gathering/domain_search
modules load gathering/emails_leak
modules run

# View results
show records

# Export results
marketplace install export_json
export json

Key Modules

Module Purpose
gathering/domain_search Search for domain information
gathering/emails_leak Find leaked email addresses
gathering/social_media Search social media platforms
discovery/subdomain_enum Enumerate subdomains
exploitation/web_vulns Check for web vulnerabilities

Other OSINT Tools

Tool Purpose Type
theHarvester Email, subdomain, and name harvesting CLI
Sublist3r Subdomain enumeration CLI
Amass Attack surface mapping CLI
Shodan Internet-connected device search Web/CLI
Censys Internet asset search Web/CLI
Hunter.io Email finder Web
Have I Been Pwned Breach checking Web
Wayback Machine Historical web content Web
TruffleHog Credential scanning in code CLI
GitLeaks Secret detection in git repos CLI

Activity Legal Status Notes
Accessing public websites Legal No authentication required
WHOIS lookups Legal Public registration data
DNS queries Legal Public DNS records
Search engine queries Legal Publicly indexed content
Social media public profiles Legal Publicly visible content only
Public record searches Legal Government-published data
News article reading Legal Published content
Activity Legal Status Notes
Bypassing authentication Illegal Violates CFAA and ToS
Accessing private data Illegal Unauthorized access
Scraping with ToS violation Potentially illegal Check terms of service
Impersonation Illegal Fraud and identity theft
Harassment Illegal Stalking and harassment laws
Data misuse Potentially illegal GDPR, privacy laws

Privacy Laws

Law Jurisdiction Key Requirements
GDPR EU Consent, right to be forgotten, data minimization
CCPA California Consumer rights, opt-out, disclosure
CFAA US No unauthorized access
PIPEDA Canada Consent, accountability, limiting collection
Privacy Act Australia Privacy principles, data handling

Ethical Guidelines

  1. Minimize data collection: Collect only what is necessary
  2. Respect privacy: Do not collect personal data beyond public availability
  3. Be transparent: When possible, be transparent about data collection
  4. Secure collected data: Protect any information you collect
  5. Delete when done: Remove collected data when no longer needed

OSINT for OSCP

OSCP-Specific OSINT Considerations

The OSCP exam has a unique environment that affects how OSINT is applied:

Factor Impact on OSINT
Isolated lab External OSINT tools may not reach exam machines
Controlled targets Machines are designed with discoverable information
Time pressure OSINT must be efficient and focused
No external access Cannot use external OSINT services during exam
Internal DNS DNS enumeration is more valuable than external OSINT

What OSINT Works in OSCP

Technique Effectiveness Notes
DNS enumeration High Internal DNS reveals infrastructure
WHOIS Low Exam domains are controlled
Search engine recon Low Exam machines not indexed
Social media None No social media for exam machines
Code repositories Low May be relevant for web apps
Web application recon High Web apps contain clues
Banner grabbing High Service banners reveal versions
Directory enumeration High Web directories reveal files

OSCP OSINT Strategy

1. Focus on Internal Sources

Since external OSINT is limited, focus on information available from the exam machines themselves:

# DNS enumeration
dig target.local ANY
nslookup target.local

# Web application reconnaissance
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt

# Banner grabbing
nmap -sV -sC target.local

2. Look for Clues in Web Applications

Web applications often contain OSINT-style clues:

  • Source code comments
  • Error messages
  • About pages
  • Contact information
  • Employee names
  • Technology stack information

3. Check for Exposed Files

# Common exposed files
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt -x .txt,.pdf,.doc,.docx,.xls,.xlsx,.bak,.old,.sql,.conf,.cfg,.ini,.env

# Check for backup files
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt -x .bak,.old,.backup,.sql,.zip,.tar,.gz

4. Analyze DNS Records

# Query all record types
dig target.local ANY

# Check for subdomains
dig ns target.local
dig mx target.local

# Zone transfer attempt
dig axfr target.local @ns1.target.local

Building an OSINT Checklist

A comprehensive OSINT checklist ensures you don’t miss important sources.

Pre-Engagement Checklist

  • Define scope and objectives
  • Identify target domains and IPs
  • Confirm legal authorization
  • Set up documentation framework
  • Prepare OSINT tools

Domain Research Checklist

  • WHOIS lookup
  • DNS record enumeration
  • Subdomain discovery
  • Certificate transparency logs
  • Domain age assessment
  • Registrar information
  • Name server details
  • MX record analysis
  • TXT record analysis (SPF, DKIM)
  • Zone transfer attempt

Search Engine Checklist

  • Google dorking for sensitive files
  • Google dorking for subdomains
  • Google dorking for employee info
  • Bing search for unique results
  • DuckDuckGo for privacy-focused search
  • Search for exposed directories
  • Search for configuration files
  • Search for backup files
  • Search for login pages
  • Search for API endpoints

Social Media Checklist

  • LinkedIn company page
  • LinkedIn employee profiles
  • Twitter/X company account
  • Twitter/X employee accounts
  • GitHub organization
  • GitHub repositories
  • GitLab projects
  • Facebook company page
  • Instagram company account
  • YouTube channel
  • Reddit mentions
  • Stack Overflow activity

Public Records Checklist

  • Business registration
  • SEC filings (if public)
  • Patent applications
  • Trademark registrations
  • Litigation records
  • Government contracts
  • Regulatory filings

Code Repository Checklist

  • GitHub organization search
  • GitHub repository search
  • GitLab project search
  • Bitbucket repository search
  • Search for credentials
  • Search for configuration files
  • Search for internal tools
  • Search for infrastructure code
  • Check for exposed secrets
  • Analyze commit history

Forum and Blog Checklist

  • Company blog
  • Technical blog
  • Employee personal blogs
  • Stack Overflow questions
  • Reddit discussions
  • Hacker News mentions
  • Security forum discussions
  • Vendor forum participation

News and Media Checklist

  • News articles
  • Press releases
  • Industry publications
  • Conference presentations
  • Podcast mentions
  • Video content

Job Posting Checklist

  • Company career page
  • LinkedIn job postings
  • Indeed job postings
  • Glassdoor reviews
  • Technology stack analysis
  • Organizational structure analysis

Correlation and Analysis Checklist

  • Cross-reference findings
  • Identify patterns
  • Build target profile
  • Identify attack vectors
  • Prioritize findings
  • Document actionable intelligence
  • Prepare for next phase

Attack Chain Position

OSINT is part of the Reconnaissance phase of the kill chain.

flowchart LR
    A[OSINT Collection] --> B[Passive Recon]
    B --> C[Active Recon]
    C --> D[Scanning]
    D --> E[Enumeration]
    E --> F[Vulnerability Analysis]
    F --> G[Exploitation]
    
    style A fill:#4ecdc4,stroke:#333,stroke-width:2px

OSINT in the Kill Chain

Kill Chain Phase OSINT Activities
Reconnaissance All OSINT collection and analysis
Weaponization N/A
Delivery N/A
Exploitation N/A
Installation N/A
Command & Control N/A
Actions on Objectives N/A

How OSINT Feeds the Attack

  1. Target Identification: OSINT identifies potential targets and their value
  2. Attack Surface Mapping: OSINT maps the target’s digital footprint
  3. Credential Discovery: OSINT finds exposed credentials and usernames
  4. Technology Identification: OSINT reveals the target’s technology stack
  5. Vulnerability Research: OSINT provides context for vulnerability research
  6. Social Engineering: OSINT provides information for social engineering attacks

OSCP Exam Tips

Critical OSINT Advice for OSCP

1. Focus on What Works in the Exam

External OSINT tools are limited in the exam environment. Focus on:

# DNS enumeration (works in exam)
dig target.local ANY
nslookup target.local

# Web application recon (works in exam)
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt

# Banner grabbing (works in exam)
nmap -sV -sC target.local

2. Look for Web Application Clues

Web applications are the most common source of OSINT-style information in OSCP:

# Check for common files
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt -x .txt,.pdf,.doc,.docx,.xls,.xlsx,.bak,.old,.sql,.conf,.cfg,.ini,.env

# Check for backup files
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt -x .bak,.old,.backup,.sql,.zip,.tar,.gz

# Check for hidden directories
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/big.txt -t 50

3. Analyze DNS Records

DNS records often reveal internal infrastructure:

# Query all record types
dig target.local ANY

# Check for subdomains
dig ns target.local
dig mx target.local

# Zone transfer attempt
dig axfr target.local @ns1.target.local

4. Check for Exposed Information

# Check for robots.txt
curl http://target.local/robots.txt

# Check for sitemap.xml
curl http://target.local/sitemap.xml

# Check for .git directory
curl http://target.local/.git/HEAD

# Check for .env file
curl http://target.local/.env

5. Document Everything

## OSINT Findings

### DNS Records
- A: target.local -> 10.10.10.1
- MX: mail.target.local
- TXT: v=spf1 include:target.local ~all

### Web Application
- Directory listing enabled at /backup/
- robots.txt reveals /admin/ directory
- .git directory exposed

### Service Banners
- Apache/2.4.6 (Ubuntu)
- OpenSSH 7.4
- MySQL 5.7.30

Common OSINT Mistakes in OSCP

  1. Spending too much time on external OSINT: External tools may not work in the exam environment
  2. Ignoring DNS records: DNS often reveals internal infrastructure
  3. Not checking web applications: Web apps contain the most OSINT-style clues
  4. Not documenting findings: You will need your notes for the report
  5. Missing exposed files: Always check for backup files, configuration files, and sensitive documents

Quick OSINT Commands for OSCP

# 1. DNS enumeration
dig target.local ANY
nslookup target.local

# 2. Web application recon
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt -t 50

# 3. Check for exposed files
curl http://target.local/robots.txt
curl http://target.local/.git/HEAD
curl http://target.local/.env

# 4. Banner grabbing
nmap -sV -sC target.local

# 5. Check for common directories
gobuster dir -u http://target.local -w /usr/share/wordlists/dirb/common.txt -x .txt,.pdf,.doc,.docx,.xls,.xlsx,.bak,.old,.sql,.conf,.cfg,.ini,.env

Summary

OSINT is a powerful tool for gathering intelligence about targets. Key takeaways:

  1. Start with structured sources: WHOIS, DNS, and search engines provide foundational information
  2. Use multiple sources: Cross-reference findings from different sources for verification
  3. Automate where possible: Tools like SpiderFoot, Maltego, and Recon-ng scale OSINT collection
  4. Stay within legal boundaries: Only access publicly available information
  5. Document everything: Record sources, timestamps, and findings
  6. Think like the target: Consider what information might be accidentally exposed
  7. For OSCP: Focus on internal sources, DNS records, and web application clues

Mastering OSINT techniques will significantly improve your reconnaissance capabilities and overall penetration testing effectiveness.


References and Further Reading


Last Updated: 2026-09-01 Chapter 03: Information Gathering - Topic 02: OSINT Techniques