ToolAtlas
FavoritesRecent

HTTP status & MIME

Processed in this browser

Text limit: 2000000 characters

This tool never uploads your input.

CDN said 415, or you forgot what belongs on .woff2. Reference only. Not Search Console, not a monitor.

On-call paste: HTTP 415 after a font deploy. This page is a cheat sheet. It does not GET your URL.

Drafting robots.txt is a different job. Parsing Mozilla/5.0… is User-Agent. Subnet math is IPv4.

Ticket language, not a monitor

415 on an upload, 401 vs 403 on an API — a lookup, not a probe of your host. We do not fetch, scan, or promise IANA’s full MIME registry. nginx and the app can return the same code with different bodies; production logs win.

How to use it

  1. Search the code or file extension.
  2. Read the usual meaning.
  3. Confirm against the RFC or your framework — stacks invent semantics.

Honest limits

Not an uptime check. Not a complete IANA registry dump. Not legal advice about logging bodies.

FAQ

Do you ping my site?

No. Type the code or extension you already saw in DevTools.

401 vs 403?

401 is ‘authenticate.’ 403 is ‘I know who you are and still no.’ Implementations blur this; read your server.

What MIME is a WOFF2?

Usually font/woff2. A wrong type is a classic 415 on picky CDNs.

Is 418 real?

It is a joke status some stacks still implement. Do not build a product on it.

User-Agent issues?

Parse the string on the User-Agent page. This page is status/MIME.

Related tools