# DNS MX Record Change Watch via DNSPod

> DNS MX Record Change Watch via DNSPod is a paid API for AI agents from dns.intel.rallylive.ca, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-21).

Monitors MX DNS records for a domain using DNSPod (doh.pub) and returns current values plus a change diff compared to the last check, stored for 90 days.

## Facts

- Endpoint: GET https://dns.intel.rallylive.ca/watch/dns/mx/via/dnspod?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-mx-record-change-watch-via-dnspod-b012554a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N50qFPtCNw88zjsFv9RrI

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-record-change-watch-via-dnspod-b012554a
```

Example prompt: Watch the MX records for example.com using DNSPod and tell me if anything has changed since the last check — show me what changed and what it used to be.

## When to prefer this

Choose this endpoint when you need change-detection semantics on top of raw MX record lookups — specifically when you want to know not just what the current MX records are, but whether they have changed since you last checked. Prefer it over a plain MX lookup when building scheduled monitors, alerting pipelines, or audit trails for email infrastructure changes. Use it over generic DNS watchers when you specifically want DNSPod (doh.pub) as the resolver, which may give different results than Cloudflare or Google DNS due to DNSPod's own caching and network vantage point.

## Known failure modes

- Domain not found or NXDOMAIN — returns current DNS response code with empty records
- First call for a domain has no previous state to compare against — changed may be false or undefined
- DNSPod resolver unavailable — check may fail or return stale data
- Domain argument missing or malformed — request returns an error
- Stored comparison data expired after 90 days — treated as first-time check

## How this service works

Change watch for dns mx via dnspod: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

## Output

Returns the current MX records as resolved by DNSPod, a boolean 'changed' flag indicating whether the records differ from the previous call for the same domain, a list of fields that changed with their before and after values, and a timestamp of when the record was last seen. Previous results are retained for 90 days for comparison.

## 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-record-change-watch-via-dnspod-b012554a/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)