Headers
by SiteCheck in Security & trust
Security headers of a URL's final response: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options (or CSP frame-ancestors), X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy and Cross-Origin-Resource-Policy, each with present, value, ok and advice. Also cookies missing Secure, HttpOnly or SameSite (names only), version leaks in Server or X-Powered-By, and a grade from A to F.
https://api.sitecheck-api.workers.dev/api/headers- Price
- $0.001
- per call in USDC
- Uptime
- 90.0%
- last 30 days
- Response time
- 669 ms
- 1.9 s slowest 5%
- Last check
- Failed
- 40 min ago, next any minute now
Reliability
Latest check failed 40 min ago: Timed out
How to call it
GET https://api.sitecheck-api.workers.dev/api/headers
Each call costs $0.001 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://api.sitecheck-api.workers.dev/api/headers?url=example.comParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Page URL or domain, e.g. example.com |
Example response
The provider's example. We can't check it without paying.
Example response, 40 lines
{
"checkedAt": "2026-10-13T09:00:00.000Z",
"cookies": {
"count": 1,
"withoutFlags": [
{
"missing": [
"Secure",
"SameSite"
],
"name": "session"
}
]
},
"finalUrl": "https://example.com/",
"grade": "D",
"headers": {
"contentSecurityPolicy": {
"advice": "add a Content-Security-Policy with default-src",
"ok": false,
"present": false,
"value": null
},
"strictTransportSecurity": {
"advice": "ok",
"ok": true,
"present": true,
"value": "max-age=31536000"
}
},
"leaks": [
{
"header": "server",
"value": "nginx/1.25.3"
}
],
"score": 4,
"status": 200,
"url": "https://example.com/"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.sitecheck-api.workers.dev/api/headers?url=example.com'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.sitecheck-api.workers.dev/api/headers?url=example.com' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.sitecheck-api.workers.dev%2Fapi%2Fheaders
const res = await pay("https://api.sitecheck-api.workers.dev/api/headers?url=example.com");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.sitecheck-api.workers.dev/api/headers?url=example.com")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 40 min ago | Timed out | - | - | - |
| 5 h ago | Passed | 402 | 802 ms | $0.001 |
| 9 h ago | Passed | 402 | 669 ms | $0.001 |
| 14 h ago | Passed | 402 | 141 ms | $0.001 |
| 18 h ago | Passed | 402 | 542 ms | $0.001 |
Show 5 older checks
| 22 h ago | Passed | 402 | 976 ms | $0.001 |
| 26 h ago | Passed | 402 | 107 ms | $0.001 |
| 30 h ago | Passed | 402 | 210 ms | $0.001 |
| 34 h ago | Passed | 402 | 1.9 s | $0.001 |
| 44 h ago | Passed | 402 | 915 ms | $0.001 |