Score custom domain readiness API

Compare the supplied TXT name and token, the CNAME target, and a certificate flag. Readiness drops when the token is missing from the expected name, the CNAME does not match the target, or the certificate flag is false. The hijacking index rises when a CNAME points elsewhere, the token sits on another name, or the certificate does not cover the domain. No DNS lookup is performed.

The Score custom domain readiness operation is part of the Domain Infrastructure Consistency Audit API on BRAINIAC.software. Compare the supplied TXT name and token, the CNAME target, and a certificate flag. Readiness drops when the token is missing from the expected name, the CNAME does not match the target, or the certificate flag is false. The hijacking index rises when a CNAME points elsewhere, the token sits on another name, or the certificate does not cover the domain. No DNS lookup is performed. It is exposed as POST /api/v1/domain-security/onboarding-readiness and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied DNS, certificate, and routing snapshots processed locally Caller-supplied custom-domain onboarding records processed locally Limitations: The records in the request are compared with each other. DNS, TLS, WHOIS, and BGP are not queried. Missing evidence is incomplete. It is not a confirmed inconsistency. An address or ASN change is not by itself malicious. A CDN or proxy address is expected only when the request supplies its host, range, ASN, or provider. A platform hostname is unassigned only when the request says so. A dangling DNS name is not proof of a takeover. infrastructure-health grades the supplied records, certificate names, expiry, and cipher names. A CNAME is dangling only when its target has no A or AAAA in the same snapshot. onboarding-readiness compares the supplied token, CNAME target, and certificate flag. A mismatched CNAME raises the hijacking index and is not proof of a takeover. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Audit domain infrastructure consistency, Grade domain snapshot health, Audit custom domain onboarding. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/domain-security/onboarding-readiness

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/domain-security/onboarding-readiness" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "domain": "shop.example.com",
  "token": "platform-verify-token-shop",
  "txt_name": "_verify.shop.example.com",
  "cname_target": "sites.platform.test",
  "certificate_covers_domain": false,
  "records": [
    {
      "type": "TXT",
      "name": "shop.example.com",
      "value": "platform-verify-token-shop"
    },
    {
      "type": "CNAME",
      "name": "shop.example.com",
      "value": "other.platform.test"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Domain Infrastructure Consistency Audit APIFull docsHow it works