# Lookproof DNS Zone File Linter

> Lookproof DNS Zone File Linter is a paid API for AI agents from api.lookproof.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-31).

Validates a pasted DNS zone file (RFC 1035 master format) for syntax errors, structural issues, and common misconfigurations before loading

## Facts

- Endpoint: POST https://api.lookproof.dev/v1/dns/zone-lint?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lookproof-dns-zone-file-linter-9f20d7e2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DkJ0Ug1IpqMPEL9_EQqQ0

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability lookproof-dns-zone-file-linter-9f20d7e2 -d '<json body>'
```

Example prompt: Can you lint my DNS zone file for example.com and flag any issues before I load it? Here's the zone content: '$TTL 3600\n@ IN SOA ns1.example.com. admin.example.com. 2024010101 3600 900 604800 300\n@ IN NS ns1.example.com.\n@ IN NS ns2.example.com.\nwww IN A 93.184.216.34'

## When to prefer this

Use this endpoint when an agent is editing or generating a DNS zone file and needs to validate it offline before submitting it to a nameserver or DNS provider. Ideal for pre-deployment checks, CI/CD pipelines that manage DNS, or any workflow where a zone file is constructed programmatically and must be verified for RFC 1035 compliance and common misconfigurations. Prefer this over live DNS resolution tools (like the sibling NS-check endpoint) when the zone file hasn't been loaded yet and you need static analysis only.

## Known failure modes

- Zone file exceeds 64 KiB limit — request rejected
- Missing required 'zone' or 'origin' fields — validation error returned
- Malformed origin domain — parsing error
- Zone file encoding issues preventing parsing — unreadable line errors reported
- Payment failure or insufficient USDC balance — x402 payment error

## How this service works

Check SPF, DMARC, DKIM, MTA-STS, DNSSEC and more, with results that explain what was found and why. Free browser checks and a pay-per-request API with x402.

## Output

A structured list of issues found in the zone file, including unreadable/unparseable lines, missing or misplaced SOA and NS records at the apex, CNAME-at-apex or CNAME-alongside-other-data conflicts, duplicate resource records, records with mixed TTLs in the same RRset, out-of-zone names, NS or MX targets lacking associated address records, and SOA timer value warnings. Returns clean output if no issues are found. Runs entirely offline with no external DNS queries.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "zone": {
   "type": "string",
   "title": "Zone",
   "maxLength": 65536,
   "minLength": 1
  },
  "origin": {
   "type": "string",
   "title": "Origin",
   "examples": [
    "example.com",
    "2.0.192.in-addr.arpa"
   ],
   "maxLength": 1024,
   "minLength": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lookproof-dns-zone-file-linter-9f20d7e2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.lookproof.dev](https://www.zero.xyz/host/api.lookproof.dev/llms.txt)