Security headers check API
Follows the redirect chains from http:// and https:// (at most five hops each, public hosts on ports 80 and 443 only) and reads HSTS, Content-Security-Policy, X-Content-Type-Options, frame protection, Referrer-Policy and cookie flags of the final HTTPS response. Page bodies are not read.
GET https://api.lookproof.dev/v1/http/security-headers
Updated 2026-10-09
Examples use the Base (eip155:8453) network.
Input
Query parameters.
| Name | Type | Required | Limits | Description |
|---|---|---|---|---|
domain | string | Yes | 1–1024 characters | The domain to check, for example example.com. |
Example request
curl -i 'https://api.lookproof.dev/v1/http/security-headers?domain=example.com'import asyncio
import os
from eth_account import Account
from x402 import x402Client
from x402.http.clients import x402HttpxClient
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact import register_exact_evm_client
async def main() -> None:
signer = EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"]))
client = register_exact_evm_client(x402Client(), signer, networks="eip155:8453")
async with x402HttpxClient(client) as http:
response = await http.get('https://api.lookproof.dev/v1/http/security-headers', params={'domain': 'example.com'})
response.raise_for_status()
print(response.json())
asyncio.run(main())
import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm";
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY);
const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, {
schemes: [{ network: "eip155:8453", client: new ExactEvmScheme(account) }],
});
const response = await fetchWithPayment("https://api.lookproof.dev/v1/http/security-headers?domain=example.com");
console.log(await response.json());
curl: unpaid request — returns 402 with the price (PAYMENT-REQUIRED). The Python and JavaScript clients pay it and send the request again. Only ordinary wallets (EOA) can pay; smart-contract wallets get a 402 without charge. See payments.
Example response
{
"checked_at": "2026-10-24T12:00:00Z",
"data": {
"domain": "example.com",
"from_http": {
"error": null,
"final_status": 200,
"final_url": "https://example.com/",
"hops": [
{
"location": "https://example.com/",
"status": 301,
"url": "http://example.com/"
},
{
"location": null,
"status": 200,
"url": "https://example.com/"
}
],
"start_url": "http://example.com/"
},
"from_https": {
"error": null,
"final_status": 200,
"final_url": "https://example.com/",
"hops": [
{
"location": null,
"status": 200,
"url": "https://example.com/"
}
],
"start_url": "https://example.com/"
},
"headers": {
"content_security_policy": "default-src 'self'; frame-ancestors 'none'",
"content_security_policy_report_only": null,
"cookies": [
{
"http_only": true,
"name": "session",
"same_site": "lax",
"secure": true
}
],
"cross_origin_opener_policy": "same-origin",
"permissions_policy": "camera=(), microphone=()",
"referrer_policy": "strict-origin-when-cross-origin",
"strict_transport_security": {
"include_subdomains": true,
"max_age": 63072000,
"preload": true,
"raw": "max-age=63072000; includeSubDomains; preload",
"valid": true
},
"x_content_type_options": "nosniff",
"x_frame_options": null
}
},
"endpoint": "http.security_headers",
"findings": [],
"meta": {
"cache_hit": false,
"duration_ms": 42,
"fresh_until": "2026-10-24T12:05:00Z",
"observed_at": "2026-10-24T12:00:00Z",
"resolver": null,
"source": "dns"
},
"request_id": "req_aaaaaaaaaaaaaaaaaaaaaaaaaa",
"schema_version": "1.0",
"status": "ok"
}
Response fields
| Field | Meaning |
|---|---|
request_id | Unique id of this request. Quote it when you contact support. |
endpoint | The endpoint id, for example mail.spf. |
schema_version | Version of the response format, currently 1.0. |
checked_at | When the check ran (ISO 8601, UTC). |
status | ok, info, warning or error from the worst finding, or unknown when the check was incomplete. unknown is not an error in the domain. |
data | The check's own data. Its fields are listed below. |
findings | What was found: code, severity, message, explanation and evidence. |
meta | Duration, cache use, resolver and how long the result stays fresh. |
Fields in data
| Field | Type |
|---|---|
domain | string |
from_http | RedirectChain |
from_https | RedirectChain |
headers | SecurityHeaders or null |
Status codes
| Status | Code | Meaning | Do you pay? |
|---|---|---|---|
| 200 | — | The result is delivered, also when it has negative findings. | Yes: charged once per payment; redelivery of the same payment is free |
| 402 | — | Payment is required, or the attached payment was refused. The body states the price. | No |
| 400 | bad_request | The request is malformed. | No |
| 409 | payment_in_progress, payment_bound_to_other_request | This payment is already being processed, or it is bound to a different request. No new payment is taken. | No |
| 422 | invalid_input | The input failed validation on a request that carries a payment; nothing is charged. Without a payment, invalid input gets a 402 whose error field names the problem. | No |
| 429 | rate_limited | Too many requests from this IP address or payer. | No |
| 502 | check_failed | The check could not be completed. | No |
| 503 | busy, unavailable, payments_unavailable | The service is busy or temporarily unavailable. | No |
| 504 | deadline_exceeded | The check ran out of time. | No |
Errors use the common error body. See errors.
Findings this endpoint can return
HTTP (2)
- Warning
HTTP_NO_HTTPS_REDIRECTPlain HTTP is not redirected to HTTPS. - Info
HTTP_UNAVAILABLEThe site does not answer over plain HTTP.
Cookies (1)
- Warning
COOKIE_NOT_SECUREThe HTTPS site sets a cookie without the Secure attribute.
Content Security Policy (2)
- Info
CSP_MISSINGThe HTTPS site sends no Content-Security-Policy header. - Info
CSP_UNSAFE_INLINEThe Content Security Policy allows inline or eval'd scripts.
Frame protection (1)
- Info
FRAME_PROTECTION_MISSINGThe HTTPS site does not restrict who may frame it.
HSTS (3)
- Warning
HSTS_MISSINGThe HTTPS site sends no valid Strict-Transport-Security header. - Info
HSTS_NOT_PRELOAD_READYThe domain does not meet the HSTS preload requirements. - Info
HSTS_SHORT_MAX_AGEThe HSTS max-age is shorter than one year.
HTTPS (1)
- Error
HTTPS_UNAVAILABLEThe site could not be loaded over HTTPS.
Redirects (2)
- Warning
REDIRECT_LIMITThe site redirects more than five times in a row. - Info
REDIRECT_OFFSITEThe site redirects to another domain.
Referrer-Policy (1)
- Info
REFERRER_POLICY_MISSINGThe HTTPS site sends no Referrer-Policy header.
X-Content-Type-Options (1)
- Info
XCTO_MISSINGThe HTTPS site sends no X-Content-Type-Options: nosniff header.