CAA Record Parser API POST

CAA Record Parser analyzes DNS CAA records that specify which Certificate Authorities are authorized to issue certificates for a domain.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/caaparser

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // CAA Record Parser response payload
  }
}

About the CAA Record Parser API

Includes a database of known Certificate Authorities like Let's Encrypt, DigiCert, and others, with automatic identification and policy interpretation.

What people use it for

Security Analysis: Parse CAA records for security analysis and threat detection to identify unauthorized certificate authorities
Policy Validation: Validate certificate issuance policies by parsing CAA records to ensure only authorized CAs can issue certificates
DNS Security Tools: Build DNS security tools that monitor and analyze CAA records for compliance and security posture assessment
Certificate Auditing: Audit domain certificate authorization settings to maintain control over which CAs can issue certificates for your domains

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use CAA Record Parser

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the CAA Record Parser API.

Read the docs →

What does the CAA Record Parser API do?

CAA Record Parser analyzes DNS CAA records that specify which Certificate Authorities are authorized to issue certificates for a domain.

How do I authenticate CAA Record Parser API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the CAA Record Parser API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the CAA Record Parser API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the CAA Record Parser API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the CAA Record Parser API use?

POST over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — POST /v1/caaparser

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`record`Required	string	`example.com. 3600 IN CAA 0 issue "letsencrypt.org"`	The CAA record string to parse

Example request

curl -X POST "https://api.apiverve.com/v1/caaparser" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"record":"example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — POST /v1/caaparser

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\"",
    "parsed": {
      "domain": "example.com",
      "ttl": 3600,
      "class": "IN",
      "flags": 0,
      "tag": "issue",
      "value": "letsencrypt.org"
    },
    "ca_info": {
      "name": "Let's Encrypt",
      "type": "Free",
      "wildcard_support": true
    },
    "interpretation": {
      "meaning": "Only letsencrypt.org is authorized to issue certificates",
      "restriction": "Restricted to specific CA",
      "critical": false,
      "critical_explanation": "Non-critical - CA may proceed if not understood"
    },
    "tag_description": "Authorizes a CA to issue certificates (any type)",
    "is_valid": true
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`raw_record`	string	`"example.com. 3600 IN CAA 0 issue "letsencrypt.org""`	The original CAA record string provided for parsing
`parsed`	object	`{...}`
`domain`	string	`"example.com"`	Domain name extracted from the CAA record
`ttl`	number	`3600`	Time-to-live value in seconds for the CAA record
`class`	string	`"IN"`	DNS class designation, typically IN for internet
`flags`	number	`0`	CAA record flags value indicating record criticality
`tag`	string	`"issue"`	CAA tag type such as issue, issuewild, or iodef
`value`	string	`"letsencrypt.org"`	Value associated with the CAA tag
`ca_info`Premium	object	`{...}`	Information about the recognized Certificate Authority
`name`Premium	string	`"Let's Encrypt"`	Recognized Certificate Authority name if identified
`type`Premium	string	`"Free"`	Certificate Authority type classification such as Free or Commercial
`wildcard_support`Premium	boolean	`true`	Indicates if the CA supports wildcard certificate issuance
`interpretation`Premium	object	`{...}`	Detailed interpretation and security analysis of CAA record
`meaning`Premium	string	`"Only letsencrypt.org is authorized to issue certificates"`	Human-readable explanation of what the CAA record authorizes
`restriction`Premium	string	`"Restricted to specific CA"`	Description of access restrictions imposed by this CAA record
`critical`Premium	boolean	`false`	Indicates if the critical flag is set on the CAA record
`critical_explanation`Premium	string	`"Non-critical - CA may proceed if not understood"`	Explanation of critical flag behavior and implications
`tag_description`Premium	string	`"Authorizes a CA to issue certificates (any type)"`	Description of the CAA tag purpose and behavior
`is_valid`	boolean	`true`	Validation status indicating if the CAA record is properly formatted

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	CAA Record Parser calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/caaparser

No SDK to install — this is a plain HTTPS call to /v1/caaparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/caaparser" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/caaparser-apiSource, issues and the examples this page is built from.ReferenceCAA Record Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/caaparsernpm APIVerve.API.CAARecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/caaparser

Install the Node.js SDK, then call the CAA Record Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/caaparser

Node.js

const res = await fetch("https://api.apiverve.com/v1/caaparser", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/caaparserThe published Node.js client, versioned and signed.GitHubapiverve/caaparser-apiSource, issues and the examples this page is built from.ReferenceCAA Record Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.CAARecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/caaparser

No SDK to install — this is a plain HTTPS call to /v1/caaparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/caaparser",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/caaparsernpm APIVerve.API.CAARecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/caaparser

Install the C# / .NET SDK, then call the CAA Record Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.CAARecordParser

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/caaparser");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.CAARecordParserThe published C# / .NET client, versioned and signed.GitHubapiverve/caaparser-apiSource, issues and the examples this page is built from.ReferenceCAA Record Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/caaparsernpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/caaparser

No SDK to install — this is a plain HTTPS call to /v1/caaparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/caaparser", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/caaparsernpm APIVerve.API.CAARecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/caaparser

No SDK to install — this is a plain HTTPS call to /v1/caaparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/caaparser");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/caaparsernpm APIVerve.API.CAARecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/caaparser

No SDK to install — this is a plain HTTPS call to /v1/caaparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/caaparser")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/caaparsernpm APIVerve.API.CAARecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

API Rate Limiting Done Right: A Complete GuideLearn how to design rate limits that protect your API while maintaining good developer experience.Read

Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

CAA Record Parser API POST

Try it — live request, no key required

About the CAA Record Parser API

What people use it for

Ways to call it

Other ways to use CAA Record Parser

Questions.

Request parameters — POST /v1/caaparser

Required

Authentication

Response — POST /v1/caaparser

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/caaparser

Resources

Also published for

Call it from Node.js — POST /v1/caaparser

Resources

Also published for

Call it from Python — POST /v1/caaparser

Resources

Also published for

Call it from C# / .NET — POST /v1/caaparser

Resources

Also published for

Call it from Go — POST /v1/caaparser

Resources

Also published for

Call it from PHP — POST /v1/caaparser

Resources

Also published for

Call it from Ruby — POST /v1/caaparser

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — CAA Record Parser API

Reference Data

Related articles

Ready to build with CAA Record Parser? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog