MIME Type Lookup & HTTP Content-Type Reference

Q: What is the difference between a file extension and a MIME type?

A file extension (like .png or .json) is an operating system convention used to hint at file formats on disk. A MIME (Multipurpose Internet Mail Extensions) type is a standardized header transmitted over network protocols (like HTTP) that explicitly tells clients and browsers how to decode and render the received byte stream.

Q: What is the default fallback MIME type for unknown binary files?

The standard fallback media type is application/octet-stream. It indicates arbitrary binary data, prompting web browsers to trigger a file download rather than attempting inline parsing or script execution.

Q: Why is the X-Content-Type-Options header critical?

The header 'X-Content-Type-Options: nosniff' prevents browsers from heuristically guessing (MIME sniffing) the payload format. This stops executable scripts disguised as harmless images or text files from running in the user's origin context.

Q: Does this tool transmit my queries to external servers?

No. The lookup dictionary evaluates purely in-browser using JavaScript. Your search strings are not submitted to any backend servers.

🔍 Search File Extension or Media Type

Enter Extension (e.g. .webp) or Media Type (e.g. application/json)

Standard IANA Content-Type:

application/json

Category: Application / Structured JSON Data

Associated Extensions: .json

Server Snippets

HTTP Response Header:

Content-Type: application/json; charset=UTF-8

Nginx Configuration (mime.types):

types { application/json json; }

1. What is a MIME Type and How Does Content Negotiation Work?

A MIME (Multipurpose Internet Mail Extensions) type—defined as a Media Type under IANA specifications (RFC 6838)—is a standardized two-part string designating the architecture, encoding, and data format of files transmitted over web protocols.

During an HTTP transaction, the server dispatches the Content-Type response header. For example:

HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
X-Content-Type-Options: nosniff

Web clients rely directly on this payload signature rather than the local filename suffix to determine whether to construct an interactive DOM, execute JavaScript routines, or prompt file storage.

2. Standard IANA Top-Level Media Types

Primary Type	Designated Purpose	Common Web Examples
`application/`	Structured document models or binary byte sequences	`application/json`, `application/pdf`, `application/wasm`
`text/`	Human-readable plaintext formats and source files	`text/html`, `text/css`, `text/javascript`, `text/csv`
`image/`	Raster bitmaps and vector graphic files	`image/avif`, `image/webp`, `image/png`, `image/svg+xml`
`audio/`	Audio tracks and multimedia sound channels	`audio/mpeg` (MP3), `audio/wav`, `audio/ogg`
`video/`	Video streams and container files	`video/mp4`, `video/webm`, `video/quicktime`
`font/`	Web typography formats	`font/woff2`, `font/woff`, `font/ttf`

3. Security Guidelines: MIME Sniffing & XSS Risks

Mishandling MIME declarations introduces distinct browser security vulnerabilities:

MIME Confusion / Sniffing Attacks: If an endpoint serves untrusted user uploads without sending X-Content-Type-Options: nosniff, older and non-strict clients may disregard the header, evaluate an uploaded image as an HTML/SVG payload, and execute stored cross-site scripting (XSS).
CORB & ORB (Opaque Response Blocking): Modern engines block cross-origin requests for resources labeled as text/html or application/json unless explicit CORS permission is present, guarding against speculative execution memory leaks (e.g. Spectre).
Deprecated JavaScript Identifiers: RFC 9239 designates text/javascript as the canonical MIME type for JavaScript assets. Historic types like application/x-javascript are legacy and should be retired in modern configurations.

4. Tool Limitations & Practical Bounds

Static Database: This reference queries an offline snapshot of standard IANA media registrations. Proprietary, internal, or vendor-specific experimental formats (prefixed with x- or vnd.) outside standard web engineering may yield fallback definitions.
No File Byte-Sniffing: This tool maps strings based on extensions and media names; it does not read magic bytes from raw binary files uploaded from disk.
Manual Verification: Always verify configuration directives against your specific web server documentation (e.g. Nginx, Caddy, or Apache HTTPd) before deploying changes to critical infrastructure.

5. Client-Side Execution & Privacy Transparency

All database queries and lookups on this page run in-memory within your browser using JavaScript. No search strings, queries, or lookup parameters are submitted to external APIs or logged on our infrastructure.

Note: Standard website analytics (Google Analytics) and third-party advertising cookies (Google AdSense) operate across the site for usage aggregation and monetization in accordance with our Privacy Policy.

6. Explore Related Developer Utilities

7. Frequently Asked Questions

What is the difference between a file extension and a MIME type?

A file extension is an operating system convention for disk storage (e.g. data.json). A MIME type is a standardized network header (e.g. Content-Type: application/json) that instructs web clients how to parse and render payloads.

What is the default fallback MIME type for unknown binary files?

The standard fallback is application/octet-stream. It informs clients that the payload is arbitrary binary data, triggering a download prompt rather than rendering inside the browser.

Why is the X-Content-Type-Options header critical?

Setting X-Content-Type-Options: nosniff forces modern browsers to respect the declared Content-Type, mitigating attacks where malicious scripts are disguised as benign assets like images or text.

Does this tool transmit my queries to external servers?

No. All dictionary searches evaluate locally in your web browser session using client-side JavaScript.

MIME Type Lookup & Content-Type Finder