X-Content-Type-Options
Declared by 35 providers across 3734 published specification files in the APIs.io network.
Spelled 2 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
X-Content-Type-Optionsx-content-type-options
The registry
| Status | permanent |
|---|---|
| Reference | Fetch |
Providers declaring it (35)
aib-group-uk aldermore bank-of-ireland-uk bank-of-scotland barclays co-operative-bank coventry-building-society coveo dow-jones extreme-networks first-direct gb-bank halifax interchecks leeds-building-society listrak lloyds-banking-group metro-bank mettle monument-bank nationwide-building-society open-banking-uk paragon-bank principality-building-society recognise-bank salesforce santander-uk secure-trust-bank shawbrook-bank shyft skipton-building-society starling-bank tsb-bank virgin-money-uk weatherbys-bank
Explore
All headers Security Policy Guidance on headers.apievangelist.com
Work with this as data
Every header here is available over the APIs.io API and to AI agents over MCP. HTTP Headers is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.