# dns-txt-via-cleanbrowsing

> dns-txt-via-cleanbrowsing is a paid API for AI agents from dns.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Retrieves DNS TXT records for a domain as answered by the CleanBrowsing security-filter resolver via DNS over HTTPS, returning records, TTL, response code, DNSSEC validation status, and answer time.

## Facts

- Endpoint: GET https://dns.intel.rallylive.ca/dns/txt/via/cleanbrowsing?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-txt-via-cleanbrowsing-0fcc1a81
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3va-LIrh11jL4PEY7zkMj

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 dns-txt-via-cleanbrowsing-0fcc1a81
```

Example prompt: What TXT records does CleanBrowsing's security-filter DNS return for example.com — include the TTL, response code, whether DNSSEC was validated, and how fast it answered?

## When to prefer this

Choose this endpoint when you specifically need to see what the CleanBrowsing security-filter DNS resolver answers for TXT records — particularly useful when comparing resolver outputs to detect filtering, propagation lag, or split-horizon behavior, or when validating SPF/DKIM/DMARC records from a security-focused resolver's perspective. Prefer it over generic DNS lookup tools when DNSSEC validation status and per-resolver answer timing matter.

## Known failure modes

- Domain does not exist — response code NXDOMAIN returned with no records
- Domain exists but has no TXT records — NOERROR with empty record set
- CleanBrowsing filters or blocks the domain — may return NXDOMAIN or modified response instead of true answer
- DNS resolution failure at CleanBrowsing — SERVFAIL response code
- Invalid or malformed domain name input — request rejected
- Network timeout reaching CleanBrowsing resolver — service error

## How this service works

TXT records for a domain as answered by CleanBrowsing (security filter) (DNS over HTTPS): the records, TTL, response code (NOERROR/NXDOMAIN/SERVFAIL), whether the resolver validated DNSSEC, and the resolver's answer time. Compare resolvers to spot propagation lag, filtering or split-horizon answers. $0.01 per lookup.

## Output

A structured response containing the TXT record values for the queried domain, their TTL, the DNS response code (NOERROR, NXDOMAIN, or SERVFAIL), a boolean indicating whether CleanBrowsing validated DNSSEC, and the resolver's answer latency in milliseconds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dns-txt-via-cleanbrowsing-0fcc1a81/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dns.intel.rallylive.ca](https://www.zero.xyz/host/dns.intel.rallylive.ca/llms.txt)