ssrf

Detect and remediate SSRF vulnerabilities in outbound HTTP requests.

20|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/thejefflarson/soundcheck --skill ssrf-thejefflarson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssrf
Source: https://github.com/thejefflarson/soundcheck/tree/main/.claude/skills/ssrf
Command: npx skills add https://github.com/thejefflarson/soundcheck --skill ssrf-thejefflarson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protects against Server-Side Request Forgery by preventing outbound requests to internal services, cloud metadata endpoints, or arbitrary hosts supplied by users.

Core Features & Use Cases

  • URL scheme restrictions and allowlisting to ensure only approved protocols are used.
  • Host allowlisting with DNS resolution checks to block access to private or internal networks.
  • Redirect control to prevent or revalidate redirects that could bypass the allowlist.
  • Integrations for server-side code paths such as webhooks and URL-preview features in multiple runtimes.

Quick Start

Validate every user-supplied URL against an allowlist and block private or metadata endpoints before performing the outbound request.

Frequently Asked Questions about ssrf

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

FAQPage Schema
How do I prevent SSRF vulnerabilities in server-side outbound HTTP requests?

Preventing SSRF vulnerabilities involves validating every user-supplied URL against a host allowlist and blocking private or metadata endpoints before performing the outbound request.

Does this SSRF protection approach work with Python, Go, and Java server-side applications?

Yes, this SSRF protection approach works with server-side applications performing dynamic URL calls, webhook handlers, and URL preview features across runtimes such as Python, Go, and Java.

How do I stop outbound requests from reaching cloud metadata endpoints via redirects?

To stop outbound requests from reaching cloud metadata endpoints via redirects, enforce redirect controls that prevent or revalidate redirects against your allowlist to prevent access bypass.

What is the best way to secure webhook handlers against Server-Side Request Forgery?

Securing webhook handlers against Server-Side Request Forgery requires applying URL scheme restrictions, host allowlisting with DNS resolution checks, and redirect controls to validate user input.

Why does DNS resolution checking matter when allowlisting URLs for outbound requests?

DNS resolution checking matters for allowlisting URLs because it blocks access to private or internal networks by verifying the resolved IP address before the outbound request is executed.

What limitations exist when relying on URL scheme restrictions for SSRF prevention?

Limitations of URL scheme restrictions for SSRF prevention include bypass risks from unvalidated redirects, requiring additional host allowlists and DNS checks to block internal network access.