Look up any HTTP status code with its meaning, RFC reference and when to use it.
Web & HTTP Tools
HTTP is simple until something goes wrong — a mysterious 4xx, a CORS error in the console, a redirect that loops, a header that never arrives. This category collects the tools that make the protocol visible: references for every status code and MIME type, parsers for headers, URLs, query strings and user agents, and live testers for CORS and redirects.
It also covers the developer workflow around APIs: turning a request into a cURL command (or a cURL command into code), and reading, formatting and validating OpenAPI and Swagger documents.
Tools in this category
Parse raw HTTP request/response headers into a structured table with explanations.
Compose HTTP headers with presets for caching, CORS, security and content negotiation.
Parse User-Agent strings into browser, version, engine, OS, device type and bot detection.
Break a URL into protocol, host, port, path, query parameters, fragment and credentials.
Parse and build query strings, including repeated keys and bracket-array notation.
Test CORS configuration: send preflight and simple requests from a given origin and inspect the Access-Control-* headers.
Trace redirect chains (301/302/307/308) and see every hop, status and final URL.
Validate Content-Type headers and check that a response body actually matches its declared media type.
Find the MIME type for a file extension, or the extensions for a MIME type.
Validate and analyze IPv4 / IPv6 addresses and CIDR ranges: class, scope, private/public, binary and range size.
Build request headers for REST APIs (auth, content negotiation, tracing) and export to cURL, fetch, axios or HTTP.
Build correctly encoded query strings for API calls with pagination, filtering and sorting parameters.
Compose JSON request bodies from a visual field editor and validate them before sending.
Generate ready-to-run REST API request code in cURL, JavaScript fetch, axios, Python requests, Java, C#, Go and PHP.
Build cURL commands from method, URL, headers, body and auth options.
Parse a cURL command into method, URL, headers and body, then convert it to fetch, axios, Python or a structured request.
Render an OpenAPI 3.x / Swagger 2.0 spec (JSON or YAML) as browsable endpoint documentation.
Validate OpenAPI 3.x and Swagger 2.0 documents for structural errors and best-practice issues.
Format OpenAPI specs, convert between JSON and YAML, and sort paths and schemas.
Format and validate Swagger 2.0 JSON documents.