CAA Record Parser API
CAA Record Parser analyzes DNS CAA records that specify which Certificate Authorities are authorized to issue certificates for a domain.
The CAA Record Parser API provides reliable and fast access to caa record parser data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use CAA Record Parser, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/caaparserCode Examples
Here are examples of how to call the CAA Record Parser API in different programming languages:
curl -X POST \
"https://api.apiverve.com/v1/caaparser" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
}'const response = await fetch('https://api.apiverve.com/v1/caaparser', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
}
response = requests.post('https://api.apiverve.com/v1/caaparser', headers=headers, json=payload)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const postData = JSON.stringify({
"record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
});
const req = https.request('https://api.apiverve.com/v1/caaparser', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.write(postData);
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/caaparser');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
'record': 'example.com. 3600 IN CAA 0 issue \'letsencrypt.org\''
}));
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"record": "example.com. 3600 IN CAA 0 issue "letsencrypt.org""
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/caaparser", bytes.NewBuffer(jsonPayload))
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/caaparser')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
payload = {
"record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
}
request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
request.body = payload.to_json
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var jsonContent = @"{
""record"": ""example.com. 3600 IN CAA 0 issue \""letsencrypt.org\""""
}";
var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.apiverve.com/v1/caaparser", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The CAA Record Parser API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the CAA Record Parser API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the CAA Record Parser API:
Parse CAA Record
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
record | string | required | The CAA record string to parse | - |
Response
The CAA Record Parser API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"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
}
}<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<raw_record>example.com. 3600 IN CAA 0 issue "letsencrypt.org"</raw_record>
<parsed>
<domain>example.com</domain>
<ttl>3600</ttl>
<class>IN</class>
<flags>0</flags>
<tag>issue</tag>
<value>letsencrypt.org</value>
</parsed>
<ca_info>
<name>Let's Encrypt</name>
<type>Free</type>
<wildcard_support>true</wildcard_support>
</ca_info>
<interpretation>
<meaning>Only letsencrypt.org is authorized to issue certificates</meaning>
<restriction>Restricted to specific CA</restriction>
<critical>false</critical>
<critical_explanation>Non-critical - CA may proceed if not understood</critical_explanation>
</interpretation>
<tag_description>Authorizes a CA to issue certificates (any type)</tag_description>
<is_valid>true</is_valid>
</data>
</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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
raw_record | string | The original CAA record string provided for parsing | |
parsed | object | - | |
â”” domain | string | Domain name extracted from the CAA record | |
â”” ttl | number | Time-to-live value in seconds for the CAA record | |
â”” class | string | DNS class designation, typically IN for internet | |
â”” flags | number | CAA record flags value indicating record criticality | |
â”” tag | string | CAA tag type such as issue, issuewild, or iodef | |
â”” value | string | Value associated with the CAA tag | |
ca_infoPremium | object | Information about the recognized Certificate Authority | |
â”” name | string | Recognized Certificate Authority name if identified | |
â”” type | string | Certificate Authority type classification such as Free or Commercial | |
â”” wildcard_support | boolean | Indicates if the CA supports wildcard certificate issuance | |
interpretationPremium | object | Detailed interpretation and security analysis of CAA record | |
â”” meaning | string | Human-readable explanation of what the CAA record authorizes | |
â”” restriction | string | Description of access restrictions imposed by this CAA record | |
â”” critical | boolean | Indicates if the critical flag is set on the CAA record | |
â”” critical_explanation | string | Explanation of critical flag behavior and implications | |
tag_descriptionPremium | string | Description of the CAA tag purpose and behavior | |
is_valid | boolean | Validation status indicating if the CAA record is properly formatted |
Headers
Required and optional headers for CAA Record Parser API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access CAA Record Parser through GraphQL to combine it with other API calls in a single request. Query only the caa record parser data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
caaparser(
input: {
record: "example.com. 3600 IN CAA 0 issue "letsencrypt.org""
}
) {
raw_record
parsed {
domain
ttl
class
flags
tag
value
}
ca_info {
name
type
wildcard_support
}
interpretation {
meaning
restriction
critical
critical_explanation
}
tag_description
is_valid
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The CAA Record Parser API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call CAA Record Parser directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call CAA Record Parser directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
CAA Record Parser API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all CAA Record Parser users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each CAA Record Parser response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, CAA Record Parser returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for CAA Record Parser:
- Monitor the rate limit headers to track your CAA Record Parser usage (Free plan only)
- Cache caa record parser responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle CAA Record Parser performance
Note: CAA Record Parser rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using CAA Record Parser on Free tier.
Error Codes
The CAA Record Parser API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate CAA Record Parser with SDKs
Get started quickly with official CAA Record Parser SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate CAA Record Parser with No-Code API Tools
Connect the CAA Record Parser API to your favorite automation platform without writing code. Build workflows that leverage caa record parser data across thousands of apps.





All platforms use your same API key to access CAA Record Parser. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for CAA Record Parser?
How many credits does CAA Record Parser cost?
Each successful CAA Record Parser API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful caa record parser lookups.
Can I use CAA Record Parser in production?
The free plan is for testing and development only. For production use of CAA Record Parser, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use CAA Record Parser from a browser?
What happens if I exceed my CAA Record Parser credit limit?
When you reach your monthly credit limit, CAA Record Parser API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.



