Beauty & Personal Care · x402 · early usage

Validate a domain's DNSSEC configuration over DNS-over-HTTPS: DS records at the parent…

Validate a domain's DNSSEC configuration over DNS-over-HTTPS: DS records at the parent zone, DNSKEY records at the domain, RRSIG signatures, NSEC/NSEC3, plus the validating resolver's AD bit — returns a full chain-of-trust assessment and readiness score so ag…

by netintel.dev · discovered, not yet claimed by its owner · updated 2026-10-08

30d calls1

30d payers1

MethodGET

Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Tags: dnssec · dnssec validation · ds records · dnskey · rrsig signatures · bazaar

Call contract

Method: GET
Input: query parameters
Output: json
Last paid call: 2026-10-08

Input example from Bazaar metadata

{
  "domain": "example.com"
}

Output example

{
  "chain_of_trust": "complete",
  "components": {
    "dnskey_record": {
      "count": 4,
      "key_types": [
        "ZSK",
        "KSK",
        "ZSK",
        "ZSK"
      ],
      "present": true
    },
    "ds_record": {
      "algorithms": [
        "ECDSAP256SHA256"
      ],
      "count": 1,
      "present": true
    },
    "nsec_or_nsec3": {
      "present": true,
      "type": "NSEC"
    },
    "rrsig_record": {
      "present": true,
      "signatures_found": 1
    }
  },
  "dnssec_enabled": true,
  "domain": "example.com",
  "findings": [],
  "grade": "A",
  "resolver_validated": true,
  "score": 100,
  "tld_ds_present": true
}

Use with an agent

Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
Inspect. Fetch /resources/29602.json for the price and payment options.
Pay. Call GET https://netintel.dev/dnssec/validate. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, Solana, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price: $0.03 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base, Solana
Demand: 1 calls · 1 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.03	0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df	300s
exact	Solana solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp	USDC	$0.03	8FVeybWnB4dYrxTuPK7WzFZNAiEcFVaDLFnKpRwVGr5s	300s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "30000",
    "amountUsd": 0.03,
    "maxTimeoutSeconds": 300
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "payTo": "8FVeybWnB4dYrxTuPK7WzFZNAiEcFVaDLFnKpRwVGr5s",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "30000",
    "amountUsd": 0.03,
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "properties": {
        "chain_of_trust": {
          "type": "string"
        },
        "components": {
          "type": "object"
        },
        "dnssec_enabled": {
          "type": "boolean"
        },
        "domain": {
          "type": "string"
        },
        "findings": {
          "type": "array"
        },
        "grade": {
          "type": "string"
        },
        "resolver_validated": {
          "description": "Validating resolver's AD bit — chain verified upstream",
          "type": "boolean"
        },
        "score": {
          "type": "number"
        },
        "tld_ds_present": {
          "type": "boolean"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

Example shape — generated from the schema, not a captured live response

{
  "example": {
    "chain_of_trust": "string",
    "components": {},
    "dnssec_enabled": true,
    "domain": "string",
    "findings": [
      "value"
    ],
    "grade": "string",
    "resolver_validated": true,
    "score": 0,
    "tld_ds_present": true
  },
  "type": "string"
}

Examples

curl

curl -X GET 'https://netintel.dev/dnssec/validate'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATURE

JavaScript

const res = await fetch("https://netintel.dev/dnssec/validate", {
  "method": "GET"
});
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

Python

import httpx
res = httpx.request("GET", "https://netintel.dev/dnssec/validate")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider: netintel.dev
Endpoint: https://netintel.dev/dnssec/validate
Machine-readable: /resources/29602.json