77trust / 100

Dnssec Validate

by NetIntel in Developer tools

x402 APIPassing, checked 4 h ago

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 agents can verify DNS integrity before trusting resolution results.

GET
https://netintel.dev/dnssec/validate
Price
$0.03
per call in USDC
Uptime
100%
last 30 days
Response time
323 ms
575 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://netintel.dev/dnssec/validate

Each call costs $0.03 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://netintel.dev/dnssec/validate?domain=example.com

Parameters

ParameterTypeRequiredDescription
domainstringYesDomain name to validate DNSSEC for (e.g. example.com)

Example response

The provider's example. We can't check it without paying.

Example response, 37 lines
{
  "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
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.03.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://netintel.dev/dnssec/validate?domain=example.com'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://netintel.dev/dnssec/validate?domain=example.com' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnetintel.dev%2Fdnssec%2Fvalidate
const res = await pay("https://netintel.dev/dnssec/validate?domain=example.com");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://netintel.dev/dnssec/validate?domain=example.com")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402467 ms$0.03
9 h agoPassed402360 ms$0.03
13 h agoPassed402396 ms$0.03
17 h agoPassed402337 ms$0.03
21 h agoPassed402298 ms$0.03
Show 10 older checks
26 h agoPassed402323 ms$0.03
30 h agoPassed402418 ms$0.03
34 h agoPassed402291 ms$0.03
38 h agoPassed402605 ms$0.03
43 h agoPassed402351 ms$0.03
47 h agoPassed402364 ms$0.03
2 days agoPassed402355 ms$0.03
2 days agoPassed402293 ms$0.03
2 days agoPassed402439 ms$0.03
3 days agoPassed402181 ms$0.03