> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify Tracking Domain

> Check the tracking domain's DNS and HTTPS now

Check your company tracking domain's CNAME record and HTTPS certificate now,
instead of waiting for the automatic checks. Sequenzy keeps checking on its
own, and a short DNS outage never changes a verified domain: it has to fail
for at least 30 minutes before links move to the shared tracking domain.

Requires the `companies:manage` scope and owner or admin access.

## Request

```bash theme={null}
curl -X POST "https://api.sequenzy.com/api/v1/tracking-domain/verify" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response fields

<ResponseField name="verified" type="boolean">
  Whether the CNAME and the HTTPS certificate work.
</ResponseField>

<ResponseField name="message" type="string">
  The result or the next step, for example that the certificate is still being
  issued.
</ResponseField>

<ResponseField name="trackingDomain" type="object">
  The tracking domain after the check. See [Get Tracking Domain](./get) for its
  fields.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "verified": false,
    "message": "DNS is correct. Cloudflare is still issuing the SSL certificate.",
    "trackingDomain": {
      "domain": "links.example.com",
      "status": "pending",
      "active": false,
      "everVerified": false,
      "sslStatus": "pending_validation",
      "verifiedAt": null,
      "lastCheckedAt": "2026-09-28T12:05:00Z",
      "error": null,
      "cnameRecord": {
        "type": "CNAME",
        "name": "links.example.com",
        "value": "links1.sequenzydns.com"
      }
    }
  }
  ```

  ```json 404 theme={null}
  {
    "error": "Add a tracking domain first."
  }
  ```

  ```json 503 theme={null}
  {
    "error": "Cloudflare API request failed."
  }
  ```
</ResponseExample>