Back to catalog
Static reviewDevelopment

Skill dossier

conducting-external-reconnaissance-with-osint

Source declaration

Conduct external recon using OSINT techniques to map an organization's external attack surface without touching target systems, gathering DNS records, certificate transparency logs, search results, social media, code repositories, and breach databases into a target profile. Use for the passive info-gathering phase of a pentest, external footprinting, or collecting employee/email intel for a social engineering campaign.

The author's original description, preserved in English. It describes intent, not verified performance.

Conduct external recon using OSINT techniques to map an organization's external attack surface without touching target systems, gathering DNS records, certificate transparency logs, search results, social media, code repositories, and breach databases into a target profile. Use for the passive info-gathering phase of a pentest, external footprinting, or collecting employee/email intel for a social engineering campaign.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Conduct external recon using OSINT techniques to map an organization's external attack surface without touching target systems, gathering DNS records, certificate transparency logs, search results, social media, code repositories, and breach databases into a target profile. Use for the passive info-gathering phase of a pentest, external footprinting, or collecting employee/email intel for a social engineering campaign. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L46]
  • Step 1: Domain and DNS Enumeration [Source statement; provisional, not tested. Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L48]
  • Step 2: Infrastructure and Service Discovery [Source statement; provisional, not tested. Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L61]
  • Step 3: Email and Personnel Intelligence [Source statement; provisional, not tested. Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L71]
  • Step 4: Credential and Data Leak Analysis [Source statement; provisional, not tested. Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L82]
  • Step 5: Technology Stack Profiling [Source statement; provisional, not tested. Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L98]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L1-L25]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/conducting-external-reconnaissance-with-osint/LICENSEOther11 KB
skills/conducting-external-reconnaissance-with-osint/references/api-reference.mdReference1.8 KB
skills/conducting-external-reconnaissance-with-osint/scripts/agent.pyScript9.1 KB
skills/conducting-external-reconnaissance-with-osint/SKILL.mdInstruction12.1 KB

SKILL.md frontmatter

{
  "name": "conducting-external-reconnaissance-with-osint",
  "description": "Conduct external recon using OSINT techniques to map an organization's external attack surface without touching target systems, gathering DNS records, certificate transparency logs, search results, social media, code repositories, and breach databases into a target profile. Use for the passive info-gathering phase of a pentest, external footprinting, or collecting employee/email intel for a social engineering campaign.",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "OSINT",
    "reconnaissance",
    "attack-surface",
    "footprinting",
    "passive-recon"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1592",
    "T1589",
    "T1590"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Domain and DNS Enumeration

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  4. 04
    Action

    Root domain identification: Start with the primary domain and identify all related domains through reverse WHOIS lookups on registrant name, email, and organization using `whoxy.com` or `domaintools.com`

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  5. 05
    Action

    Subdomain enumeration: Run multiple tools for comprehensive coverage:

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  6. 06
    Action

    `amass enum -passive -d target.com -o amasssubs.txt` for passive subdomain discovery from 40+ data sources

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

Inspect all extracted workflow candidates (53 candidate steps)
  1. 07
    Action

    `subfinder -d target.com -all -o subfindersubs.txt` for fast passive enumeration

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  2. 08
    Output

    `crt.sh` certificate transparency log queries: `curl -s "https://crt.sh/?q=%25.target.com&output=json" | jq -r '.[].namevalue' | sort -u`

    Source-described output candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  3. 09
    Action

    DNS record analysis: Query for all record types: `dig target.com ANY`, check for SPF, DKIM, DMARC records that reveal email infrastructure, and enumerate MX records to identify email providers

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  4. 10
    Action

    Zone transfer attempt: `dig axfr @ns1.target.com target.com` to check for misconfigured DNS servers

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  5. 11
    Action

    Consolidate results: Merge, deduplicate, and resolve all discovered subdomains to IP addresses. Map IP addresses to ASN and hosting providers.

    Source-described action candidate under “Step 1: Domain and DNS Enumeration”; not verified execution.

  6. 12
    Action

    Step 2: Infrastructure and Service Discovery

    Source-described action candidate under “Step 2: Infrastructure and Service Discovery”; not verified execution.

  7. 13
    Action

    Shodan: `shodan search "ssl.cert.subject.cn:target.com"` to find all internet-facing services with TLS certificates for the target domain. Also search by organization name and IP ranges.

    Source-described action candidate under “Step 2: Infrastructure and Service Discovery”; not verified execution.

  8. 14
    Action

    Censys: Search for target's IP ranges and TLS certificates to identify services, technologies, and potential vulnerabilities indexed from internet-wide scanning

    Source-described action candidate under “Step 2: Infrastructure and Service Discovery”; not verified execution.

  9. 15
    Action

    Cloud asset discovery: Check for S3 buckets (`target-com`, `target-backup`, `target-dev`), Azure Blob storage (`target.blob.core.windows.net`), and GCP storage using tools like `cloudenum`

    Source-described action candidate under “Step 2: Infrastructure and Service Discovery”; not verified execution.

  10. 16
    Action

    WAF and CDN identification: Use `wafw00f target.com` to identify web application firewalls and CDN providers that may mask the origin server IP

    Source-described action candidate under “Step 2: Infrastructure and Service Discovery”; not verified execution.

  11. 17
    Action

    Historical data: Use Wayback Machine (`web.archive.org`) to find removed pages, old application versions, and forgotten endpoints

    Source-described action candidate under “Step 2: Infrastructure and Service Discovery”; not verified execution.

  12. 18
    Action

    Step 3: Email and Personnel Intelligence

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  13. 19
    Action

    Email harvesting: `theHarvester -d target.com -b all -f harvestresults.html` to collect emails from search engines, LinkedIn, and data sources

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  14. 20
    Action

    Email format identification: Use `hunter.io` to determine the email format (first.last, flast, firstl) and verify deliverability

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  15. 21
    Action

    LinkedIn reconnaissance: Identify employees by department, particularly IT administrators, security team members, and executives. Note technologies mentioned in job postings and employee profiles.

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  16. 22
    Action

    Organizational chart: Build an org chart from LinkedIn data to understand reporting structures, identify key personnel, and map departments

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  17. 23
    Action

    Social media analysis: Review employee social media profiles for information about internal tools, technologies, office locations, badge photos, and security practices

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  18. 24
    Action

    Job postings: Analyze current and historical job postings on the company career page and job boards for technology stack details, tools, and infrastructure information

    Source-described action candidate under “Step 3: Email and Personnel Intelligence”; not verified execution.

  19. 25
    Action

    Step 4: Credential and Data Leak Analysis

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  20. 26
    Action

    Breach databases: Check `haveibeenpwned.com` API for breached email addresses associated with the target domain

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  21. 27
    Action

    Paste sites: Search Pastebin, GitHub Gists, and similar paste sites for leaked credentials, configuration files, or internal documents

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  22. 28
    Action

    Code repositories: Search GitHub, GitLab, and Bitbucket for:

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  23. 29
    Action

    `org:target "password"`, `org:target "apikey"`, `org:target "secret"`

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  24. 30
    Action

    Use `trufflehog` or `gitleaks` for automated secret scanning across the target's public repositories

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  25. 31
    Action

    Document metadata: Download publicly available documents (PDF, DOCX, XLSX) from the target website and extract metadata using `exiftool` to reveal internal usernames, software versions, printer names, and file paths

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  26. 32
    Action

    Google dorking: Use targeted search operators:

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  27. 33
    Action

    `site:target.com filetype:pdf` for public documents

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  28. 34
    Action

    `site:target.com inurl:admin` for admin panels

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  29. 35
    Action

    `site:target.com "index of /"` for directory listings

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  30. 36
    Action

    `site:pastebin.com "target.com"` for paste site mentions

    Source-described action candidate under “Step 4: Credential and Data Leak Analysis”; not verified execution.

  31. 37
    Action

    Step 5: Technology Stack Profiling

    Source-described action candidate under “Step 5: Technology Stack Profiling”; not verified execution.

  32. 38
    Action

    Web technology fingerprinting: Use `whatweb target.com` or Wappalyzer browser extension to identify CMS, frameworks, JavaScript libraries, analytics, and server software

    Source-described action candidate under “Step 5: Technology Stack Profiling”; not verified execution.

  33. 39
    Action

    SSL/TLS analysis: `sslyze target.com` or `testssl.sh target.com` to identify cipher suites, protocol versions, certificate details, and cryptographic weaknesses

    Source-described action candidate under “Step 5: Technology Stack Profiling”; not verified execution.

  34. 40
    Action

    JavaScript analysis: Download and review JavaScript files for framework identifiers, API endpoints, internal hostnames, and version strings

    Source-described action candidate under “Step 5: Technology Stack Profiling”; not verified execution.

  35. 41
    Action

    DNS-based service identification: Review TXT records for service providers (e.g., `v=spf1 include:spf.google.com` indicates Google Workspace, `MS=msXXXXXX` indicates Microsoft 365)

    Source-described action candidate under “Step 5: Technology Stack Profiling”; not verified execution.

  36. 42
    Action

    Mobile app analysis: Download the target's mobile applications from app stores and analyze with `apktool` (Android) or `frida` for hardcoded URLs, API endpoints, and embedded credentials

    Source-described action candidate under “Step 5: Technology Stack Profiling”; not verified execution.

  37. 43
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  38. 44
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  39. 45
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  40. 46
    Action

    Enumerate 147 subdomains via Amass and crt.sh, including staging.techcorp.io, jenkins.techcorp.io, and vpn.techcorp.io

    Source-described action candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  41. 47
    Action

    Shodan reveals a forgotten Elasticsearch instance on port 9200 with no authentication exposed to the internet

    Source-described action candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  42. 48
    Action

    theHarvester collects 89 employee email addresses, revealing the format [email protected]

    Source-described action candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  43. 49
    Action

    GitHub search discovers a former developer's public repository containing a `.env` file with AWS access keys

    Source-described action candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  44. 50
    Action

    LinkedIn analysis reveals the company uses Okta for SSO, Jira for project management, and AWS for hosting

    Source-described action candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  45. 51
    Action

    Google dorking finds a directory listing on docs.techcorp.io exposing internal architecture diagrams

    Source-described action candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  46. 52
    Output

    Compile all intelligence into a reconnaissance report that feeds directly into the threat modeling and attack planning phases

    Source-described output candidate under “Scenario: Pre-Engagement Reconnaissance for a Red Team Exercise”; not verified execution.

  47. 53
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

24 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

18 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 18 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

5 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/conducting-external-reconnaissance-with-osint/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/conducting-external-reconnaissance-with-osint/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/conducting-external-reconnaissance-with-osint
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.