# dns-hinfo-via-cleanbrowsing

> dns-hinfo-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-22).

Fetches HINFO DNS records for a domain as answered by the CleanBrowsing security-filtering DNS 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/hinfo/via/cleanbrowsing?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-hinfo-via-cleanbrowsing-c3ccccd9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_74kK5AMgPwWzF6G7VK5xC

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-hinfo-via-cleanbrowsing-c3ccccd9
```

Example prompt: Can you look up the HINFO DNS records for example.com using the CleanBrowsing resolver and tell me the records returned, TTL, response code, whether DNSSEC was validated, and how fast it answered?

## When to prefer this

Choose this endpoint when you specifically need to know what CleanBrowsing's security-filtering DNS resolver returns for HINFO records — particularly when comparing resolver answers for split-horizon detection, checking if CleanBrowsing is filtering a domain, auditing DNS propagation through security resolvers, or validating DNSSEC status from a security-conscious resolver's perspective. Prefer it over generic DNS tools when the security-filter lens is relevant.

## Known failure modes

- Domain not found — NXDOMAIN response code returned
- CleanBrowsing security filter blocks the domain — returns SERVFAIL or empty answer instead of actual HINFO records
- No HINFO records exist for the domain — empty record set with NOERROR
- Resolver timeout — SERVFAIL with elevated answer time
- Invalid domain name format — request rejected before query is made
- Network unavailability of CleanBrowsing resolver — endpoint may return an error

## How this service works

HINFO 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 HINFO DNS records for the queried domain as answered by CleanBrowsing's security-filtering resolver, including: the record data, TTL, DNS response code (NOERROR, NXDOMAIN, SERVFAIL, etc.), whether the resolver performed DNSSEC validation, 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-hinfo-via-cleanbrowsing-c3ccccd9/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)