Service Status

The scanner, the public API, and the MCP server are operational.

For a live, machine-readable health check, query the health endpoint at /api/health. It returns a small JSON payload you can poll programmatically.

Retry guidance

If you are an agent or a script and a request does not succeed, recover gracefully:

• On 429 Too Many Requests: back off and retry. Honor the Retry-After and RateLimit-Reset headers to know how long to wait before trying again. Do not retry in a tight loop.
• On 422 Unprocessable Entity: the domain could not be resolved (a DNS failure such as NXDOMAIN). This is not a transient error - retrying will not help. Report to the user that the domain does not resolve rather than retrying.
• On 5xx: treat as transient. Wait briefly, then retry with exponential backoff.

The rate limit is 10 domains per hour per IP. Every response includes RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers so you can pace requests and avoid hitting the limit in the first place.