# dns-mx-via-cleanbrowsing-watch

> dns-mx-via-cleanbrowsing-watch 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 via CleanBrowsing DNS and returns whether they changed since the last check, with before/after diffs.

## Facts

- Endpoint: GET https://dns.intel.rallylive.ca/watch/dns/mx/via/cleanbrowsing?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-via-cleanbrowsing-watch-95de6390
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-gbghEEE5eHTOg9B_8glH

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-cleanbrowsing-watch-95de6390
```

Example prompt: Keep an eye on the MX records for example.com using CleanBrowsing DNS and tell me if anything has changed since the last time you checked.

## When to prefer this

Choose this endpoint when you need to detect changes in MX (mail exchange) records specifically as seen through CleanBrowsing's security-filtered DNS resolver, particularly useful for security-sensitive monitoring where you want a filtered DNS perspective. Prefer this over generic DNS lookup endpoints when you need change detection with diff output rather than just a current snapshot, and when scheduling periodic checks to alert on email infrastructure tampering.

## Known failure modes

- Domain not previously queried — no baseline to compare against, changed field may be null or false
- CleanBrowsing DNS upstream failure — may return error or empty record set
- Invalid or non-existent domain — NXDOMAIN response with no MX records
- Rate limiting or payment failure — request rejected before check runs
- 90-day history expiry — baseline lost, comparison resets

## How this service works

Change watch for dns mx via cleanbrowsing: 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 answered by CleanBrowsing DNS, a boolean indicating whether the records changed since the previous call for the same domain, the specific fields that changed with before/after values, and a timestamp of when the records were 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-via-cleanbrowsing-watch-95de6390/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)