API documentation

Digizap exposes 15 measurement endpoints publicly — exactly the ones the tools on this site use themselves. Free, no key, no account. The machine-readable OpenAPI 3.1 specification lives at /openapi.json; import it into Swagger Editor, Postman or your own code.

Common rules

• GET and HEAD only; every answer is JSON.
• No key, no account. Each endpoint does have its own maximum of requests per window per visitor (address) — the exact number stands per endpoint below; beyond that the API answers 429 with a retry-after header.
• Some answers are reused: a full scan stays in the cache for up to 15 minutes, the crawl rules (robots and sitemap) for up to 10, response headers for up to 5 — a repeated question may come back fast.
• Endpoints that reach a target themselves — over HTTP or a mail-port probe — share the quiet on our server: at most four measurements at once, at most two questions per twenty seconds on the same target, and at most fourteen seconds of work per request. The pure resolver endpoints (dns, dns-compare, email, mail security, spf) carry their own, shorter timeouts.
• Targets on private or reserved addresses (localhost, 127.x, 10.x, 192.168.x, …) are refused before anything is measured.
• We send no CORS headers: scripts from another browser domain are blocked by the browser itself. Do the work from your own server, or simply use the tools on this site.
• Errors always come as { ok: false, error }, where possible with a failure object naming the cause (DNS failure, timeout, refused address, …).
• We log API calls without arguments — never a target URL.
• Every measurement departs from our own server.

OpenAPI specification

The specification (0.2.0) lives at /openapi.json and is written in English — OpenAPI's standard language. The page and the API answers are Dutch by default; ?lang=en makes them English.

Endpoints