Which URLs can I test?

Any public http:// or https:// host. Private networks, localhost, link-local and cloud-metadata addresses are refused to prevent server-side request forgery, and redirects to such addresses are blocked too. Each request is limited to 10 seconds and 1 MB of response body.

How do I send JSON or form data?

Pick the JSON tab to get live validation with the error line, or the Form tab to enter key/value pairs that are URL-encoded for you. The matching Content-Type header is added automatically unless you set your own.

Can I paste a cURL command from browser devtools?

Yes. Open Import cURL, paste the command and the method, URL, headers and body are filled in. -X, -H, -d, --data-raw, --data-urlencode, --json, -u, -A, -b, -I and -G are understood; file uploads and multipart forms are not.

What do the timing bars mean?

DNS is the lookup, Connect the TCP handshake, TLS the certificate exchange, Wait the time to first byte after the request was sent, and Download the time to read the body. When redirects are followed the waterfall shows the first hop plus the total across hops.

HTTP Request Tester

A Postman-lite for quick checks. Build a request with any method, custom headers, a raw, JSON or form body and a timeout, then send it through the FizzKit relay so CORS never blocks you. The response shows the status line with a plain-English explanation, every header, the redirect chain hop by hop, a DNS / connect / TLS / TTFB / download waterfall and the body pretty-printed (JSON, XML, HTML) or rendered in a sandboxed preview. Import a cURL command, copy the request as cURL, fetch, Python or Node, keep a history of your last 20 sends and save named requests for later.

Fetches URLs via the FizzKit relay — nothing is stored

Send with ⌘ Enter (Ctrl Enter). Requests go through the FizzKit relay, never straight from your browser.

Timeoutms

Headers

Body

GET requests are sent without a body.

Copy as

Send a request to see the response here

Requests are made by the FizzKit relay, not your browser, so CORS never gets in the way and you see the real status line, every header and the redirect chain with timing. The relay only reaches public hosts: private, loopback, link-local and cloud-metadata targets are blocked. Each request is capped at 10 s and 1 MB of body; nothing is stored.

History (0)

The last 20 requests you send will appear here.

Saved requests (0)

Name the current request and save it to reuse later.

Request Bin

Get a unique URL that captures every webhook or HTTP request and shows it live — headers, body, query, raw wire format.

HTTP Status Codes

Searchable reference for every HTTP status code.

JSON Formatter

Beautify, minify, sort, query and repair JSON with a tree view and copy-as code export.

URL Parser & Query Editor

Break any URL into parts, edit query params live, unwrap nested redirect URLs, decode ad macros, build UTMs and follow redirects.

MIME Type Lookup

Find the right Content-Type for any extension, check what a URL actually serves, and identify files by magic bytes.

How to use HTTP Request Tester

1Choose a method, enter the URL and add any headers — the JSON, Form and Bearer auth presets fill the common ones.
2Write a body in the Raw, JSON or Form tab (or paste a cURL command under Import cURL) and press Send or ⌘ Enter.
3Read the status explanation, redirect chain, timing waterfall and headers, then switch the body view between Pretty, Raw and a sandboxed Preview.
4Copy the request as cURL, fetch, Python or Node, or save it by name to reuse it later; the last 20 sends stay in History.

About HTTP Request Tester

HTTP Request Tester is part of FizzKit — a collection of focused developer and ad-tech tools. This tool uses the FizzKit relay to fetch public URLs on your behalf (so browser CORS rules do not get in the way); fetched content is returned to your browser and not stored.

Frequently asked questions

Browsers enforce CORS and hide most response headers, so a direct fetch would fail against most APIs. The FizzKit relay performs the request server-side and returns the real status line, all headers, the redirect chain and connection timing. Nothing is stored after the response is returned.

Related tools