Skip to content
ecdsa.com

REST API v1 · free · no keys · CORS enabled

Free Signature API

The checks behind the ecdsa.com tools, callable from scripts, CI and AI agents: verify ECDSA signatures, convert DER ⇄ raw, decode and verify ES256/ES384/ES512 JWTs, decode X.509 certificates, grade a domain’s TLS signature health. Plain JSON over HTTPS — https://ecdsa.com/api/v1

curl -s https://ecdsa.com/api/v1

Machine-readable spec: /api/v1/openapi.json (OpenAPI 3.1)

What the API does

Every operation is a pure function of its input: send JSON, get JSON. Each has a reference page with its fields, a runnable example and its error codes.

AI agents and IDE assistants call the same operations through the MCP server. Full API reference

Your first call in 30 seconds

Paste one of these into a terminal or a browser console. The sample is real: the signature verifies against the key.

curl
curl -sS 'https://ecdsa.com/api/v1/verify' \
  -H 'content-type: application/json' \
  -d '{
  "publicKey": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE4+8TCP3Hop/Acb8L7reksO9flyt1\nsUhvEqUs7a45RVDRDtAIZdTnOJcAhTCQvdzUBO4KUyxSRcZm6ro+2RGfSQ==\n-----END PUBLIC KEY-----",
  "message": "The quick brown fox jumps over the lazy dog",
  "signature": "3045022100df542bb71e0e3019086f1b1ba51f1aa0ec5e6afca05c3f5a7f4f02f5b7c39d24022030c59f1ac6d8c6893fb2a5ac8dfd9388d31ebd3382510dcfb7f28f9182eb1131"
}'
JavaScript (fetch)
const response = await fetch("https://ecdsa.com/api/v1/verify", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "publicKey": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE4+8TCP3Hop/Acb8L7reksO9flyt1\nsUhvEqUs7a45RVDRDtAIZdTnOJcAhTCQvdzUBO4KUyxSRcZm6ro+2RGfSQ==\n-----END PUBLIC KEY-----",
    "message": "The quick brown fox jumps over the lazy dog",
    "signature": "3045022100df542bb71e0e3019086f1b1ba51f1aa0ec5e6afca05c3f5a7f4f02f5b7c39d24022030c59f1ac6d8c6893fb2a5ac8dfd9388d31ebd3382510dcfb7f28f9182eb1131"
  }),
});
console.log(response.status, await response.json());
Response 200
{
  "valid": true,
  "curve": "P-256",
  "curvesTried": [
    "P-256"
  ],
  "keySource": "pem-spki",
  "signatureFormat": "der",
  "details": {
    "r": "df542bb71e0e3019086f1b1ba51f1aa0ec5e6afca05c3f5a7f4f02f5b7c39d24",
    "s": "30c59f1ac6d8c6893fb2a5ac8dfd9388d31ebd3382510dcfb7f28f9182eb1131",
    "highS": false
  },
  "notes": []
}

This is the API’s answer to exactly this request.

Next: every field and option of this operation in the API reference, and what each error means in the error table.

The basics

Free, no keys

No signup, no tokens, no quotas to manage. Send a request, get JSON back. Optional API keys with higher limits will come with ecdsa.com accounts.

60 requests/min per IP

Generous for scripts and CI. The domain-health operation adds a budget of 10 per minute, because it scans outward.

CORS open

Access-Control-Allow-Origin: * on every response — call the API straight from a browser, a doc page or a serverless function.

Never send private keys

Requests containing a PEM PRIVATE KEY block, an OpenSSH, SSH2 or PuTTY private key, or a JWK with “d” are rejected with private_key_rejected. For anything secret, use the local browser tools — they never transmit your input.

Nothing logged

Request bodies are parsed in memory and never written to logs.

Rate limits

60 requests per minute per IP across the whole API, plus 10 per minute for /v1/health/{domain}, which opens outbound TLS connections.

Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; exceeding a limit returns 429 with a Retry-After header.

Real scans of a domain also draw on budgets shared by everyone: one host is scanned at most 6 times per 10 minutes, and all scans together at most 300 times per minute, so the API cannot be used to flood a server. Answers from the one-hour cache spend nothing; a scan beyond a budget is answered with 429 rate_limited and Retry-After.

With an API key, calls are limited per key instead — 120 per minute on the free tier, 600 on the pro tier — and draw on the daily and monthly quotas of the account. Keys arrive with ecdsa.com accounts and cannot be created yet; until then every call is anonymous.

More calls and monitoring are planned: see pricing and join the waitlist.

Treat the documented numbers as the intended budget, not a hard ceiling: back off politely on 429 and cache on your side — domain-health results are already cached for an hour.

Errors

Every error is JSON with a machine-readable code and a human-readable message that says exactly what was wrong with the input — the same explanations the browser tools show. Error responses link here in their docs field.

CodeHTTPMeaning
invalid_json400The body is not valid JSON or not a JSON object; or the input nests arrays and objects more than 64 levels deep (JSON documents inside string fields count too), or is too complex to inspect for private keys.
missing_field400A required field is absent or empty.
invalid_input400A field could not be parsed — the message explains exactly why.
private_key_rejected400The request contains private-key material (a PEM PRIVATE KEY block, an OpenSSH, SSH2 or PuTTY private key, or a JWK with "d"). Never send private keys anywhere.
unsupported_algorithm400The token's algorithm is not one this operation verifies.
invalid_domain400Not a public DNS hostname (IP addresses, single-label names and paths are refused).
scan_dns_error400The domain does not resolve in public DNS.
scan_private_address400The domain resolves (at least partly) to a private or reserved address.
webhook_url_refused400The webhook URL cannot receive deliveries: it is not https on port 443, its host is not a public DNS name, or the name does not resolve or resolves (at least partly) to a private or reserved address.
unauthorized401The Authorization or X-API-Key header is malformed, the API key is not valid (wrong checksum, unknown, revoked or expired), or the operation needs a key.
forbidden_scope403The API key is valid but lacks a scope this operation requires; the message names it.
webhook_limit_reached403The account already has as many webhook endpoints as its plan allows.
not_found404No operation exists at this path.
webhook_not_found404The API key's account has no webhook endpoint with this id.
method_not_allowed405The path exists but does not accept this HTTP method; see the Allow header.
payload_too_large413The body exceeds 100 KB.
rate_limited429Too many requests — see Retry-After.
quota_exceeded429A daily or monthly quota of the API key's account is used up. X-Quota-Reset (and Retry-After) say when it starts over; retrying earlier cannot succeed.
internal_error500Unexpected server error.
scan_unreachable502The domain refused or dropped the connection on port 443.
scan_tls_error502The TLS handshake failed or presented no usable certificate.
service_unavailable503API keys cannot be verified right now (the key store is unreachable); retry shortly.
webhooks_unavailable503Webhooks are switched off on this server: it has no signing keys configured.
scan_timeout504The scan did not finish in time.
timeout504The operation did not finish within its time budget.

What to do about each code, and which ones the SDKs retry

Explore

Changelog

Latest release: v1.1.0, October 22, 2026. The API is versioned in the path; breaking changes would ship as /api/v2 — v1 responses may gain fields but will not lose or change them.

Full changelog