Articles · Protocol

What's new in Protocol tools

Header parsers, curl helpers, fetch utilities, and network reference pages expanded in recent batches. Start from your symptom—headers, IPs, or status codes—and jump to the matching tool.

Protocol tools help when you are staring at curl output, response headers, or network reference tables. Recent batches added header parsers, curl helpers, and HTTP fetch utilities beside the long-standing status-code and MIME reference pages.

curl, fetch, and command translation

  • cURL parser — break a copied curl command into method, URL, headers, and body fields.
  • curl to HTTPie — rewrite a curl one-liner into http-style syntax for quick retries.
  • HTTP fetch — send a GET/HEAD from the browser and inspect status and headers (respect CORS).

Parse response and request headers

IP, DNS, and reference tables

Status codes, MIME, SemVer, and site meta

For the full debugging map including CIDR and SQL format, see protocol tools for web debugging.

Common use cases

  • Paste a curl command into the parser before translating it to HTTPie or fetch.
  • Split Forwarded or Retry-After values from a 502 trace without opening Wireshark.
  • Look up MIME types or status codes while reading API docs in another tab.

Common mistakes to avoid

  • Expecting HTTP fetch to bypass CORS

    Browser fetch tools only reach URLs your page is allowed to call—use them for allowed endpoints or pasted responses.

  • Treating SSL expiry hint as live monitoring

    Certificate parse pages read pasted PEM text—they do not poll your production hosts.

FAQ

Where do check-digit tools like IMEI or IBAN live?

Many identifier checksum pages appear under Protocol in the catalog; UUID and telecom format checks also have Identity tab entries—search by the acronym you have.

Can agents prefill header parsers?

Single-field parsers often accept q for the raw header line; multi-field network tools may open without URL prefill.