---
title: "Inspect existing DMARC record"
method: POST
path: "/api/v1/check-dmarc"
tags: ["Tools"]
---

# Inspect existing DMARC record

`POST /api/v1/check-dmarc`

## Request

- Base URL: `https://api.dmarc-examiner.com`
- URL: `https://api.dmarc-examiner.com/api/v1/check-dmarc`
- Auth: API key in header `X-API-Key`

Free utility — looks up the DMARC record at `_dmarc.{domain}` for any
domain. Useful for due diligence before onboarding a new domain.
The domain does not need to belong to the organization.

## Request body

- CheckDmarcRequest
  - `domain` string, required

## Response `200`

DMARC inspection result

- DmarcCheckResult
  - `domain` string, required
  - `has_existing_dmarc` boolean, required
  - `existing_record` string, nullable, required: Raw DMARC record string, if present.
  - `existing_policy` 'none' | 'quarantine' | 'reject' | 'null', nullable, required
  - `existing_rua` string[], required: Email addresses parsed from the `rua=` tag.
  - `existing_ruf` string[], required: Email addresses parsed from the `ruf=` tag.

## Other responses

- `400`: Request payload, body field, or query parameter is missing, malformed, outside documented bounds, or fails type/enum validation. Two body shapes can occur: - **Body validation errors** (e.g. missing `name`, wrong type) come from the controller and have the form `{"message": "..."}`. - **Query parameter errors** (e.g. `limit` out of range, `auth_failure` off-enum, `domain_id` not a UUID) flow through the API exception subscriber and add an `error: "bad_request"` machine-readable code: `{"error": "bad_request", "message": "Query parameter \"limit\" must be between 1 and 100, got 999"}`.
- `401`: Authentication failed. Two shapes are possible depending on cause: - **Invalid or revoked key** — body is `{"message": "..."}` only. - **Missing `X-API-Key` header** — body adds an `error: "unauthorized"` machine-readable code. Clients should treat both as the same outcome and read `message` for display.
- `403`: The organization's current plan does not include the feature required by this endpoint (e.g. `apiAccess`, `forensicReports`, `advancedAlerts`). Distinct from `PlanLimitExceeded` (HTTP 402), which signals a *quota* exhausted on a feature the plan does include. If a customer downgrades to Free, all `/api/v1/*` requests will start returning this response.
- `429`: Rate limit exceeded.

---

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