73trust / 100

Domain Changes

by how.is in Security & trust

x402 APIPassing, checked 3 h ago

Check when a domain appeared in the registry zone file, left it, came back or changed nameservers, from daily gTLD and .com/.net zone files. A sudden nameserver move signals a hijack or sale; a brand-new name signals phishing.

POST
https://how.is/v1/domain/changes
Price
$0.01
per call in USDC
Uptime
81.8%
last 30 days
Response time
281 ms
4.1 s slowest 5%
Last check
Passed
3 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

POST https://how.is/v1/domain/changes

Each call costs $0.01 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.

POST https://how.is/v1/domain/changes
content-type: application/json

{
  "domain": "github.com"
}

Parameters

ParameterTypeRequiredDescription
domainstringYesA registered name directly under a TLD, e.g. example.com (zone files list no subdomains; ccTLDs publish none)

Example response

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

{
  "data": {
    "_shape": "data: in_zone_now, first_seen, first_seen_is_coverage_start, last_seen, current_ns, events[{type: appeared|disappeared|reappeared|ns_changed, dates, from, to, message}], changed_last_30_days, coverage{daily_since, first_zone_file, runs}, ns_runs, note."
  },
  "receipt": {
    "charge_usd": 0.01,
    "rail": "x402",
    "settlement_tx": "0x…",
    "tool": "changes"
  },
  "result": "Domain change history for the requested subject"
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://how.is/v1/domain/changes' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"github.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 - -X POST 'https://how.is/v1/domain/changes' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"github.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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fhow.is%2Fv1%2Fdomain%2Fchanges&method=POST
const res = await pay("https://how.is/v1/domain/changes", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "domain": "github.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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://how.is/v1/domain/changes",
        json={
            "domain": "github.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
3 h agoPassed402260 ms$0.01
9 h agoServed content without asking for payment200332 ms-
14 h agoPassed402391 ms$0.01
19 h agoPassed402376 ms$0.01
25 h agoPassed402340 ms$0.01
Show 10 older checks
33 h agoServed content without asking for payment200369 ms-
43 h agoPassed402304 ms$0.01
2 days agoServed content without asking for payment200253 ms-
3 days agoPassed402281 ms$0.01
3 days agoPassed402285 ms$0.01
3 days agoServed content without asking for payment200433 ms-
4 days agoPassed402382 ms$0.01
4 days agoPassed402335 ms$0.01
4 days agoServed content without asking for payment200357 ms-
5 days agoPassed4024.1 s$0.01