SSRF Payloads by Target
Copy-paste SSRF payloads grouped by what you’re trying to reach. Each hub explains when it applies, gives a one-line note per payload, and ends with the defense. For authorized testing and CTF only.
Need variations for a specific target or filter? Use the generator.
Copy-paste SSRF payloads for cloud instance metadata: AWS 169.254.169.254 (IMDSv1/v2), GCP metadata.google.internal, Azure, DigitalOcean, Alibaba, Oracle, OpenStack and Kubernetes — with the required headers and the defenses.
View payloadsSSRF payloads for the AWS instance metadata service (IMDS) at 169.254.169.254: IMDSv1 credential paths, the IMDSv2 token dance, and encoded IP forms that bypass deny-list filters.
View payloadsSSRF payloads for the Google Cloud metadata server at metadata.google.internal / 169.254.169.254 — service-account tokens, project data and the mandatory Metadata-Flavor: Google header.
View payloadsSSRF payloads for the Azure Instance Metadata Service at 169.254.169.254 — managed-identity tokens, instance data, and the required Metadata: true header plus api-version parameter.
View payloadsEvery spelling of localhost for SSRF: 127.0.0.1 shorthands, decimal/octal/hex/dotless encodings, IPv6 loopback and IPv4-mapped forms, and wildcard-DNS loopback — to beat deny-lists that string-match 127.0.0.1.
View payloadsAllow-list bypass SSRF payloads using @ userinfo, # fragments, backslashes, extra slashes, tabs and Unicode — exploiting the gap between the validator's URL parser and the HTTP client's.
View payloadsProtocol-smuggling SSRF payloads: gopher:// to Redis/Memcached/SMTP, dict:// banner grabs, file:// local read, plus ftp/ldap/tftp/php wrappers — for reaching internal non-HTTP services.
View payloadsSSRF payloads that attack DNS resolution: wildcard-DNS hosts (nip.io, sslip.io) that resolve to an internal IP, and DNS-rebinding records that flip to 127.0.0.1 after the validation check (TOCTOU).
View payloads