---
title: "Re-check sending DNS"
method: POST
path: "/v1/account/domains/sending/verify"
tags: ["Account"]
---

# Re-check sending DNS

`POST /v1/account/domains/sending/verify`

## Request

- Base URL: `https://api.briefgate.dev`
- URL: `https://api.briefgate.dev/v1/account/domains/sending/verify`
- Auth: HTTP bearer

Ask the email provider to re-check the DNS records right now. Returns the per-record status so a typo can be found without leaving the API. The same check also runs automatically every 10 minutes for up to 7 days after the domain was added, so this route is for checking sooner, not required to make verification happen.

## Response `200`

Verification result

- object
  - `domain` string
  - `verified` boolean
  - `status` string
  - `dns_records` object[]
    - `type` string: DNS record type, e.g. 'TXT', 'MX', 'CNAME'.
    - `name` string
    - `value` string
    - `ttl` unknown
    - `priority` integer: Set on MX records only.
    - `record` 'SPF' | 'DKIM': Sending domain only — which mechanism this record serves.
    - `status` 'not_started' | 'pending' | 'verified' | 'failed' | 'temporary_failure': Per-record verification state. The portal domain's synthesized record only ever reports 'pending' or 'verified'.

## Other responses

- `400`: Invalid request — malformed body or query parameters
- `401`: Missing or invalid API key
- `402`: The account's plan does not include this — `plan_required` — or a quota is exhausted
- `404`: Resource not found

---

[API](https://skmtc.dev/briefgate/apis/briefgate-api.md) · [All operations](https://skmtc.dev/briefgate/apis/briefgate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/briefgate/apis/briefgate-api/revisions/b21afed4748b?raw)