# dns-mx-via-dnspod

> dns-mx-via-dnspod 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 MX records for a domain using DNSPod (doh.pub) DNS-over-HTTPS, returning records, TTL, response code, DNSSEC validation status, and answer latency.

## Facts

- Endpoint: GET https://dns.intel.rallylive.ca/dns/mx/via/dnspod?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-mx-via-dnspod-f4eaf744
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__IjskRa33CnPsYedcrYnx

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-mx-via-dnspod-f4eaf744
```

Example prompt: What MX records does DNSPod return for gmail.com, and does it validate DNSSEC? Also tell me the TTL and how long the resolver took to answer.

## When to prefer this

Choose this endpoint when you specifically need MX record resolution via the DNSPod (doh.pub) resolver — particularly useful for checking how Chinese or Asia-Pacific DNS infrastructure sees a domain, comparing results against other resolvers like Cloudflare or Google to detect propagation lag, geo-filtering, or split-horizon DNS setups. Prefer it when DNSSEC validation status from DNSPod is specifically needed, or when diagnosing email routing issues in regions where DNSPod is commonly used.

## Known failure modes

- Domain does not exist — returns NXDOMAIN response code with no records
- Resolver error or upstream failure — returns SERVFAIL response code
- Domain has no MX records — NOERROR with empty answer section
- Query timeout from DNSPod resolver — may return elevated latency or error
- Invalid domain name format in query — may return error or unexpected result

## How this service works

MX records for a domain as answered by DNSPod (doh.pub) (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 MX records (priority and mail exchanger hostname) for the queried domain as seen by the DNSPod (doh.pub) resolver, along with TTL, DNS response code (NOERROR, NXDOMAIN, or SERVFAIL), a boolean 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-mx-via-dnspod-f4eaf744/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)