httpx-probe

Probe URL lists for live HTTP/HTTPS services and collect fingerprints, titles, headers, and TLS metadata.

1.6k|234|Updated Dec 7, 2019
One-click install
npx skills add https://github.com/wgpsec/AboutSecurity --skill httpx-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: httpx-probe
Source: https://github.com/wgpsec/AboutSecurity/tree/main/skills/tool/httpx-probe
Command: npx skills add https://github.com/wgpsec/AboutSecurity --skill httpx-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly find which URLs host live HTTP/HTTPS services and extract actionable metadata so you can prioritize web targets for scanning and analysis without manual validation.

Core Features & Use Cases

  • High-throughput probing: scan large URL lists or pipe outputs from subdomain and port scanners to quickly detect live endpoints.
  • Fingerprinting & metadata: collect status codes, page titles, server headers, technology stacks (tech-detect), IP/CNAME/ASN, CDN/WAF indicators, and TLS info.
  • Pipeline integration: use as a bridge between discovery tools (subfinder, naabu) and scanners (nuclei, katana), and produce JSON outputs for downstream processing.
  • Advanced filtering & extraction: filter by status codes, regex matches, response length, CDN, or custom extractors, and optionally capture screenshots for triage.

Quick Start

Run httpx against your URL list to discover live HTTP services and output status codes, titles, and technology fingerprints in JSON.

Frequently Asked Questions about httpx-probe

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

FAQPage Schema
How do I detect live HTTP services and extract web fingerprints from a large URL list?

To detect live HTTP services and extract web fingerprints, probe large URL lists concurrently to collect status codes, page titles, server headers, and technology stacks. This high-throughput process filters alive endpoints and outputs JSON for downstream scanning pipelines.

Can I pipe subdomain and port scan outputs directly for HTTP discovery?

Yes, you can pipe outputs from subdomain and port scanners directly for HTTP discovery. The tool acts as a bridge in vulnerability scanning pipelines, reading bulk URLs to rapidly identify live endpoints and extract actionable metadata without manual validation.

What metadata can I collect during web technology fingerprinting?

During web technology fingerprinting, you can collect status codes, page titles, server headers, technology stacks, IP, CNAME, ASN, CDN, WAF indicators, and TLS information. You can also apply advanced filtering by regex matches, response length, or custom extractors.

Does bulk HTTP probing support capturing screenshots for endpoint triage?

Yes, bulk HTTP probing supports capturing screenshots for endpoint triage. Alongside detecting live HTTP/HTTPS services and gathering TLS metadata, you can optionally enable screenshot capture to visually prioritize high-value web targets during analysis.

What is the best way to filter alive endpoints by CDN and status codes?

The best way to filter alive endpoints by CDN and status codes is using advanced extraction options during high-throughput probing. You can filter results based on specific status codes, CDN presence, WAF indicators, regex matches, or response length to identify high-value targets.

How does TLS grabbing work during concurrent HTTP discovery?

TLS grabbing works during concurrent HTTP discovery by extracting TLS certificate information alongside standard HTTP responses. When probing URLs for live HTTP/HTTPS services, the tool concurrently collects TLS metadata and server headers to identify the underlying technology stack.