# DNS vs HTTP Consistency Checker

> DNS vs HTTP Consistency Checker is a paid API for AI agents from intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Resolves a domain's DNS A/AAAA records, fetches the site over HTTPS, and checks whether the HTTP response is consistent with DNS — detecting CDN fronting, CNAME chains, dangling DNS, and stale records.

## Facts

- Endpoint: GET https://intel.rallylive.ca/monitor/dns-vs-http
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-vs-http-consistency-checker-984d6eb1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mURKBFtN9mh-awLcRvzSe

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-vs-http-consistency-checker-984d6eb1
```

Example prompt: Check if the DNS records for stripe.com are consistent with what's actually being served over HTTPS — I want to know if it's CDN-fronted, what the CNAME chain looks like, and whether there are any dangling or stale records.

## When to prefer this

Choose this endpoint when you need to cross-validate DNS resolution against live HTTP serving behavior for a domain — especially useful after migrations, when investigating dangling DNS, detecting unexpected CDN fronting, or auditing whether a hostname is actually serving from its resolved origin. Prefer this over a plain DNS lookup when HTTP-layer behavior matters, and over a plain HTTP check when DNS-level routing is also relevant.

## Known failure modes

- Domain does not exist or has no A/AAAA records — DNS resolution fails
- HTTPS connection times out or is refused — HTTP fetch cannot complete
- Domain is reachable via DNS but returns a non-2xx HTTP status — inconsistency flagged
- CDN detection may miss lesser-known CDN providers not in the known fingerprint list
- Payment not received — request rejected with 402 status

## How this service works

DNS vs HTTP consistency: resolves the domain's A/AAAA records, fetches the site over HTTPS, and reports whether the served response looks consistent (status, final host, whether the response is fronted by a CDN like Cloudflare/Fastly/Akamai rather than the resolved origin), plus CNAME chain. Detect dangling DNS, half-migrated hosts and stale records. $0.01 per domain.

## Output

Returns the HTTP response status code, the final host that served the response, whether the site is fronted by a CDN (Cloudflare, Fastly, Akamai, etc.) rather than the resolved origin IP, the CNAME chain, and a consistency verdict indicating whether DNS resolution and HTTP serving are aligned or mismatched.

## 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-vs-http-consistency-checker-984d6eb1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intel.rallylive.ca](https://www.zero.xyz/host/intel.rallylive.ca/llms.txt)