# dns-https-via-cleanbrowsing

> dns-https-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).

Resolves HTTPS DNS records for a domain using CleanBrowsing's security-filtering DNS over HTTPS resolver, returning records, TTL, response code, DNSSEC validation status, and answer time.

## Facts

- Endpoint: GET https://dns.intel.rallylive.ca/dns/https/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-https-via-cleanbrowsing-46c38d28
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i2nAYm3jaINsShkq_LPP4

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-https-via-cleanbrowsing-46c38d28
```

Example prompt: Can you look up the HTTPS DNS records for example.com using CleanBrowsing's security filter resolver and tell me what records it returns, the TTL, the response code, whether DNSSEC was validated, and how fast it answered?

## When to prefer this

Choose this endpoint when you specifically need to see how CleanBrowsing's security-filtering resolver answers HTTPS DNS queries — for example, to detect whether CleanBrowsing blocks or filters a domain, to audit DNSSEC validation behavior on a security-focused resolver, or to compare propagation lag and split-horizon differences between CleanBrowsing and other resolvers like Cloudflare or AdGuard. Not suitable for general-purpose DNS lookups where resolver identity is irrelevant.

## Known failure modes

- SERVFAIL response if CleanBrowsing cannot resolve the domain
- NXDOMAIN if the domain does not exist or is blocked by CleanBrowsing's security filter
- No HTTPS record returned if the domain has no HTTPS RR configured
- Network timeout if the CleanBrowsing DoH endpoint is unreachable
- Empty record set if the domain exists but has no HTTPS-type DNS records

## How this service works

HTTPS 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

Returns the HTTPS DNS records for the queried domain as answered by CleanBrowsing's security-filtering DoH resolver, including the record data, TTL, DNS response code (NOERROR, NXDOMAIN, or SERVFAIL), a flag indicating whether DNSSEC was validated, 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-https-via-cleanbrowsing-46c38d28/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)