httpx_probe

Parses httpx JSON output to document live HTTP/HTTPS endpoints and their characteristics.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ProwlrBot/prowlrbot --skill httpx-probe-prowlrbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: httpx_probe
Source: https://github.com/ProwlrBot/prowlrbot/tree/main/src/prowlrbot/ext/skills/httpx_probe
Command: npx skills add https://github.com/ProwlrBot/prowlrbot --skill httpx-probe-prowlrbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identify live HTTP/HTTPS endpoints and surface structured details (status codes, server headers, detected technologies) to speed up inventory, monitoring, and security assessments.

Core Features & Use Cases

  • Probes targets via httpx to collect status, title, content length, server, and detected technologies.
  • Auto-flags interesting findings such as admin panels, default pages, and exposed services.
  • Use Case: security audits, uptime monitoring, and asset discovery across multiple endpoints.

Quick Start

Provide a list of targets to probe and receive a structured report with results and auto-generated findings.

Frequently Asked Questions about httpx_probe

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

FAQPage Schema
How do I identify live HTTP endpoints and document their web server technologies?

Automated HTTP probing identifies live HTTP/HTTPS endpoints and extracts characteristics like status codes, titles, web servers, and detected technologies to produce structured findings for asset monitoring and security audits.

Can I automate HTTP probing for asset discovery across internal and external networks?

Automated HTTP probing supports asset discovery across internal networks and external endpoints by parsing httpx JSON output to extract url, status_code, web_server, and response_time fields into structured reports.

What is the best way to parse httpx JSON output for security findings and endpoint discovery?

Parsing httpx JSON output for endpoint discovery involves extracting url, status_code, title, content_length, web_server, technologies, content_type, and response_time fields to auto-generate structured security findings.

Does httpx probing auto-flag exposed services and admin panels during security audits?

HTTP probing auto-flags interesting findings such as admin panels, default pages, and exposed services during security audits to speed up infrastructure inventory and surface structured details for assessments.

What fields are extracted when probing HTTP endpoints for uptime monitoring?

Probing HTTP endpoints for uptime monitoring extracts url, status_code, title, content_length, web_server, technologies, content_type, and response_time fields from httpx JSON output to support monitoring and documentation.

Do I need httpx installed to extract status codes and technologies from live endpoints?

You need httpx to probe targets and generate JSON output, which is then parsed to extract status codes, server headers, and detected technologies into structured findings for asset discovery and monitoring.