# dns-https-via-opendns

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

Retrieves HTTPS DNS records for a domain using OpenDNS as the resolver via DNS-over-HTTPS, returning records, TTL, response code, DNSSEC validation status, and answer latency.

## Facts

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

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-opendns-0d2c9789
```

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

## When to prefer this

Choose this endpoint when you specifically need to see how OpenDNS resolves HTTPS records, such as comparing resolver behavior across providers, detecting OpenDNS-specific filtering or blocking, diagnosing DNS propagation lag as seen by OpenDNS users, or verifying DNSSEC validation support. Use sibling endpoints for other resolvers (e.g. AliDNS, Google, Cloudflare, CleanBrowsing) when you need cross-resolver comparison.

## Known failure modes

- Domain does not exist — response code NXDOMAIN returned
- OpenDNS resolver fails to answer — response code SERVFAIL returned
- Missing or malformed domain input parameter — 4xx error
- OpenDNS filtering causes unexpected NXDOMAIN for existing domains
- Network timeout from upstream resolver results in no response or error
- DNSSEC validation failure may cause SERVFAIL even for existing domains

## How this service works

HTTPS records for a domain as answered by OpenDNS (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 OpenDNS, including the record set, TTL, response code (NOERROR, NXDOMAIN, or SERVFAIL), 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-https-via-opendns-0d2c9789/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)