What does the DMARC Parser API return?

Every answer carries the record that was parsed, parsed_tags (each tag name mapped to its value exactly as published), validation_errors (one message per problem) and success, which is true only when the record parsed and every tag is valid. The domain endpoint adds the domain you sent, the _dmarc name it looked up and dns_lookup: true. Values are not normalized or filled in with defaults: a record without sp simply has no sp in parsed_tags.

Which tags are validated?

The record must start with v=DMARC1 and carry a p tag. p and sp must be none, quarantine or reject; adkim and aspf must be r or s; pct must be an integer from 0 to 100; ri must be a non-negative integer; fo must be a colon-separated list of 0, 1, d and s; and every comma-separated rua and ruf entry must be a mailto: address or an http(s) URL. Any other tag, such as rf or np, is returned as published without being checked.

What happens when a domain has no DMARC record?

The lookup still succeeds as an HTTP request: you get HTTP 200 with success: false, the domain and _dmarc name that were checked, and the error "No DMARC record found for this domain". That covers domains that publish nothing at _dmarc, TXT records there that don't start with v=DMARC1, and domains that don't exist. It costs 5 credits like any other lookup.

Can I check a DMARC record before I publish it?

Yes. POST the record to /v1/text, as JSON ({"dmarc_record": "v=DMARC1; ..."}), as a text/plain body or as a multipart form field. No DNS lookup is made, so you can validate a draft for a domain or subdomain that doesn't have one yet, and fix every reported problem before it goes live.

Is an invalid record an error response?

No. A record with mistakes is a normal HTTP 200 answer with success: false and the problems listed in validation_errors, so you can show them to your users. When the record doesn't start with v=DMARC1, has a tag without "=", or has no p tag, parsing stops there: parsed_tags is empty and validation_errors holds that one problem. Only requests the API can't work with, such as a missing domain or record, are HTTP 400.

How much does a call cost?

Each lookup or parse costs 5 credits, whether the record is valid, invalid or missing. Requests rejected before any work is done (HTTP 400, 401, 403, 413 and 429) and failed DNS lookups (HTTP 502 or 504) are not billed, and the X-Credits-Charged response header shows what each call cost. On the free plan's 1,000 monthly credits that is 200 calls a month.

No. Every call to /v1/domain queries live DNS, so a record you just changed is picked up as soon as the change has reached DNS resolvers, subject to the record's TTL. If the DNS lookup fails, the API retries once and then answers HTTP 502 (504 on a timeout), which is not billed, so you can simply try again.

Parse and look up DMARC policies

DMARC Parser API

The DMARC Parser API turns a DMARC record into structured JSON and tells you what is wrong with it. Send a domain and the API looks up its _dmarc TXT record in live DNS first, or send the record text to check it before it goes live.

Built for email security teams, deliverability tools and agencies that need to see, at scale, which domains enforce DMARC, where their reports go, and which records carry mistakes that receivers will ignore.

Get a free API key Read the docs

Free tier included, no credit card required. One key works across every API.

Free calls / month: 200
Endpoints: 2
Tags checked: 10
Record limit: 8,192 chars

Get your free API key

200 free calls on the free plan

Key features

Domain lookup: finds the v=DMARC1 TXT record at _dmarc.{domain} in live DNS and parses it
Record parsing: send the record as JSON, plain text or a form field to check it before publishing
Every tag returned: p, sp, adkim, aspf, pct, rua, ruf, fo, ri and any other tag, exactly as published
Validation: policies, alignment modes, pct and ri ranges and fo options are checked, with one message per problem
Report address checks: each rua and ruf entry must be a mailto: address or an http(s) URL
Clear outcomes: success is true only for a valid record; a missing record is reported, not an error

Built for

DMARC enforcement audits across many domains
Pre-publish checks in DNS management tools
Email deliverability and security dashboards
Onboarding checks for email-sending platforms
Agency monitoring of client domains
Phishing and spoofing exposure reviews
Vendor and supplier security assessments
Compliance evidence for sender requirements

MCP · for your agent

Hand the DMARC Parser API to your agent

Connect Claude, Cursor or any MCP client once, then ask in plain words. Your agent finds this API, reads its docs and makes the call: 5 credits per call, the same as REST, from your team's balance.

Connect your agent

Check a domain's DMARC policy

“Is DMARC enforced on example.com yet? Tell me the policy, the alignment modes and where aggregate reports go.”

list_apis · get_api_docsfree

api_request POST /dmarc-parser/v1/domain 5 cr

The published record's tags (p, sp, adkim, aspf, pct, rua) parsed, with any validation errors.

Validate a record before publishing

“Here's the DMARC record I'm about to publish for billing.example.com. Is it valid, and what will it enforce?”

list_apis · get_api_docsfree

api_request POST /dmarc-parser/v1/text 5 cr

Each tag parsed and checked, with mistakes like a bad pct or rua URI flagged before it goes live.

Audit DMARC across client domains

“We manage 8 client domains. Look up each one's DMARC record and list the ones still on p=none.”

list_apis · get_api_docsfree

api_request POST /dmarc-parser/v1/domain 5 cr

Each domain's DMARC policy side by side, with the ones on p=none or with no record flagged.

$ claude mcp add --transport http apicodex https://mcp.apicodex.io

Illustrative asks; the calls and prices are real. Claude, Cursor, VS Code and Windsurf setup: mcp.apicodex.io

Try it

Build the request for your data

Edit the parameters below and see the exact request and curl command you'd send. No key required to preview.

POST /dmarc-parser/v1/domain

Open in Playground

Request · HTTP

POST /dmarc-parser/v1/domain HTTP/1.1
Host: api.apicodex.io
Content-Type: application/json
X-Api-Key: YOUR_API_KEY

{
  "domain": "example.com"
}

Response · JSON 200 OK

{
  "success": true,
  "parsed_at": "2026-10-11T09:14:22.381Z",
  "dmarc_record": "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:[email protected]",
  "parsed_tags": {
    "v": "DMARC1",
    "p": "reject",
    "sp": "reject",
    "adkim": "s",
    "aspf": "s",
    "rua": "mailto:[email protected]"
  },
  "validation_errors": [],
  "domain": "example.com",
  "dmarc_domain": "_dmarc.example.com",
  "dns_lookup": true
}

Run it with your key

Documentation

DMARC Parser API Documentation

The DMARC Parser API has two endpoints: POST /v1/domain looks up and parses a domain's published DMARC record, and POST /v1/text parses a record you send. Both return the record, its tags and a list of validation errors; success is true only when the record is valid.

Base URL

url

https://api.apicodex.io/dmarc-parser

Authentication

Authenticate every request with your API key: send it in an X-Api-Key header, or pass it as an ?apikey= query parameter.

headers

{
"X-Api-Key": "YOUR_API_KEY"
}

Request and response

Illustrative values. Confirm current endpoint behavior, quotas, and data freshness in the API documentation before production use.

request · http

POST /dmarc-parser/v1/domain HTTP/1.1
Host: api.apicodex.io
Content-Type: application/json
X-Api-Key: YOUR_API_KEY

{
  "domain": "example.com"
}

response · json

{
  "success": true,
  "parsed_at": "2026-10-11T09:14:22.381Z",
  "dmarc_record": "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:[email protected]",
  "parsed_tags": {
    "v": "DMARC1",
    "p": "reject",
    "sp": "reject",
    "adkim": "s",
    "aspf": "s",
    "rua": "mailto:[email protected]"
  },
  "validation_errors": [],
  "domain": "example.com",
  "dmarc_domain": "_dmarc.example.com",
  "dns_lookup": true
}

Code examples

cURL

# Look up and parse a domain's DMARC record
curl --request POST \
  --url 'https://api.apicodex.io/dmarc-parser/v1/domain' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{"domain": "example.com"}'

# Validate a record before you publish it
curl --request POST \
  --url 'https://api.apicodex.io/dmarc-parser/v1/text' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{"dmarc_record": "v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]"}'

JavaScript/Node.js

const res = await fetch('https://api.apicodex.io/dmarc-parser/v1/domain', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({ domain: 'example.com' })
});

const result = await res.json();

if (result.success) {
  console.log(`Policy: p=${result.parsed_tags.p}`);
} else {
  // No record published, or the record has problems
  console.log(result.error ?? result.validation_errors);
}

Python

import requests

headers = {"X-Api-Key": "YOUR_API_KEY"}

# Look up and parse a domain's DMARC record
lookup = requests.post(
    "https://api.apicodex.io/dmarc-parser/v1/domain",
    headers=headers,
    json={"domain": "example.com"},
)
print(lookup.json())

# Validate a record before you publish it
check = requests.post(
    "https://api.apicodex.io/dmarc-parser/v1/text",
    headers=headers,
    json={"dmarc_record": "v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]"},
)
result = check.json()
print(result["success"], result["validation_errors"])

Endpoints

POST /v1/domain

Look up the TXT record at _dmarc.{domain} and parse the first one starting with v=DMARC1. JSON body {"domain": "example.com"}. A domain with no DMARC record answers success: false with "No DMARC record found for this domain".

curl -X POST "https://api.apicodex.io/dmarc-parser/v1/domain" -H "X-Api-Key: YOUR_API_KEY" -H "Content-Type: application/json" -d '{"domain": "example.com"}'

POST /v1/text

Parse a record you supply (up to 8,192 characters): JSON {"dmarc_record": "..."} (or "text"), a text/plain body, or a multipart form field. No DNS lookup.

curl -X POST "https://api.apicodex.io/dmarc-parser/v1/text" -H "X-Api-Key: YOUR_API_KEY" -H "Content-Type: text/plain" --data 'v=DMARC1; p=none; rua=mailto:[email protected]'

Response Fields

Required parameters

success True only when the record parsed and every tag passed validation.
dmarc_record The record that was parsed, trimmed.
parsed_tags Each tag mapped to its value as a string, exactly as published (pct is "100", rua is the comma-separated list). Empty when parsing stopped early.
validation_errors One message per problem found; empty for a valid record.

Optional parameters

domain / dmarc_domain On /v1/domain: the domain you sent and the _dmarc name that was looked up.
dns_lookup On /v1/domain: always true.
error On /v1/domain when the domain publishes no DMARC record.

Pricing

DMARC Parser API Pricing

This API costs 5 credits per request. Credits are shared across every API on your plan.

Estimate your monthly cost

Drag the slider to match your expected request volume. We'll recommend the cheapest plan that covers it.

Requests per month 10,000

Recommended plan

Starter

$29.99 /month

Credits used

Credits included

Cost per 1K requests

Choose Starter

Free

1,000 credits · ~200 requests/mo · 2 rps

All APIs included
No credit card required
Full documentation and examples
MCP server for your AI agents
Up to 5 active API keys

Start for free

Starter

Popular

$29.99 /month

50,000 credits · ~10,000 requests/mo · 10 rps

All APIs included
Email support
Usage dashboard and analytics
MCP server for your AI agents
Up to 5 active API keys

Start with Starter

Pro

$99.99 /month

250,000 credits · ~50,000 requests/mo · 25 rps

All APIs included
Priority support
MCP server for your AI agents
Up to 5 active API keys

Start with Pro

FAQ

DMARC Parser API

Key features

Built for

Hand the DMARC Parser API to your agent

Check a domain's DMARC policy

Validate a record before publishing

Audit DMARC across client domains

Build the request for your data

DMARC Parser API Documentation

Base URL

Authentication

Request and response

Code examples

Endpoints

POST /v1/domain

POST /v1/text

Response Fields

Required parameters

Optional parameters

DMARC Parser API Pricing

Free

Starter

Pro

Need a different plan?

Frequently asked questions

Related APIs