recon-archive-urls

Collect and categorize historical URLs from public web archives for security reconnaissance.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill recon-archive-urls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recon-archive-urls
Source: https://github.com/salmanabdurrahman/pi-pentest-agent/tree/main/skills/recon-archive-urls
Command: npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill recon-archive-urls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of discovering hidden or retired web endpoints that are no longer linked on a live site but remain indexed in public web archives, allowing for comprehensive attack surface mapping without ever touching the target server.

Core Features & Use Cases

  • Historical Endpoint Discovery: Aggregates data from the Wayback Machine, Common Crawl, and URLScan to find forgotten admin panels, dev environments, and legacy API versions.
  • Automated Scope Triage: Automatically filters discovered URLs against defined scope rules to ensure compliance and focus on relevant targets.
  • Vulnerability Surface Mapping: Categorizes URLs by type (e.g., auth, config, backup) to prioritize high-value targets for subsequent active enumeration.

Quick Start

Use the recon-archive-urls skill to collect and categorize all historical endpoints for the target domain while applying the current scope file.

Frequently Asked Questions about recon-archive-urls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find hidden web endpoints using the Wayback Machine for pentesting?

Historical endpoint discovery aggregates archived URLs from public web archives like the Wayback Machine to find retired admin panels and legacy APIs without touching the live target server. This passive reconnaissance maps the target's historical web presence to identify potential attack vectors.

What is passive URL discovery and when do I need it for attack surface mapping?

Passive URL discovery collects historical web data from public archives to identify forgotten endpoints without sending requests to the target server. You need it during the reconnaissance phase of security assessments when mapping a target's attack surface to remain undetected.

Can I filter discovered historical URLs against a defined scope during reconnaissance?

Yes, automated scope triage filters discovered historical URLs against defined scope rules to ensure compliance and focus on relevant targets. This local scope validation logic processes archive data before any active enumeration begins.

How do I categorize historical URLs to prioritize high-value targets for active enumeration?

Vulnerability surface mapping categorizes discovered historical URLs by type, such as auth, config, or backup endpoints. This categorization prioritizes high-value targets like forgotten dev environments and legacy API versions for subsequent active enumeration.

Does recon-archive-urls collect data from Common Crawl and URLScan in addition to the Wayback Machine?

Yes, historical endpoint discovery aggregates data from the Wayback Machine, Common Crawl, and URLScan. This multi-archive approach ensures comprehensive attack surface mapping by capturing forgotten endpoints indexed across different public web archive platforms.

What are the limitations of using public web archives for passive endpoint discovery?

Passive endpoint discovery relies on public web archives, meaning it can only find URLs that were previously indexed and cannot discover endpoints that were never crawled. Discovered URLs also require local scope validation before active enumeration to ensure assessment compliance.