# Health

GET /healthz checks IronDome endpoint availability without checking an email. See response examples and connection warmup guidance.

```http
GET /healthz
```

## Request

No API key is required. Use the API origin:

```sh
curl 'https://api.irondome.dev/healthz'
```


## Response

HTTP `200`:

```json
{"status":"ok"}
```

Health requests do not consume email checks. This endpoint checks availability; it does not check an email or validate an API key.

Reuse your HTTP client. You do not need a health request before every email check.

## Signup preparation

You can send one health request using your backend's shared client while a customer fills the signup form. Retain that client for the later email check instead of closing it after health returns.

Warmup prepares transport state only. It does not authenticate a key, initialize the protected detector, or guarantee that a later request reaches the same backend instance or Fastly machine. A browser health request uses the browser's connection and does not prepare your backend's pool.

See [performance and warmup](/docs/guides/performance) for pooling settings and runtime limitations.