# Name-Safety Checker (IDN / Homograph / Registrability)

> Name-Safety Checker (IDN / Homograph / Registrability) is a paid API for AI agents from s5.oddments.ai, paid per call via x402, $0.03/call, status down (last checked 2026-10-13).

Analyzes domain labels or names for Unicode normalization, homograph/confusable attacks, IDNA2008 validity, punycode encoding, and per-TLD syntax compliance — computed offline from public Unicode and IANA tables.

## Facts

- Endpoint: POST https://s5.oddments.ai/v1/check?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: down
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/name-safety-checker-idn-homograph-registrability-9fd6bcda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kYQ79w4U8CiOtqdBxhQd5

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 name-safety-checker-idn-homograph-registrability-9fd6bcda -d '<json body>'
```

Example prompt: Can you check whether 'аpple.com' is safe to use — specifically whether it contains any confusable or homograph characters that could make it a phishing risk, and give me its punycode encoding and a breakdown of any suspicious Unicode codepoints?

## When to prefer this

Choose this endpoint when you need a comprehensive, offline, standards-grounded analysis of a domain label's Unicode safety — especially for detecting IDN homograph attacks, validating IDNA2008 compliance, computing UTS#39 skeletons, or auditing brand names before registration. It is distinctly more thorough than simple regex hostname validators or WHOIS-based tools because it covers confusable character detection, mixed-script analysis, per-TLD syntax rule enforcement, and produces a signed receipt. Prefer it over DNS/RDAP availability checkers when your goal is safety and distinguishability analysis, not availability lookup.

## Known failure modes

- Label exceeds 63 octets — IDNA length check fails with specific error
- Label fails IDNA2008 normalization — returns error in idna.error field
- Invalid or unsupported TLD submitted — may return no per-TLD registry data
- Malformed UTF-8 or non-Unicode input — request parsing error
- Network or service unavailability — HTTP 5xx response
- Payment not provided or invalid x402 header — payment required error (402)

## How this service works

Check whether a candidate name or domain label is VALID, SAFELY DISTINGUISHABLE from look-alikes, and legal under a TLD's syntax rules -- computed offline from public Unicode and IANA tables. Returns: Unicode normalization (NFC/NFD/NFKC/NFKD and whether NFKC folding changes the label), a per-character breakdown with codepoint, name, script and general category, UTS #39 single-script/mixed-script analysis, HOMOGRAPH AND CONFUSABLE DETECTION against the Unicode confusables table with the offending characters named as witnesses, the UTS #39 skeleton and any ASCII string the label visually imitates, a same-script confusable neighbourhood of near-identical variants an attacker could register against you, IDNA2008 validity, punycode A-label encoding with a decode round-trip, and per-TLD checks: presence in the IANA root zone, 1-63 octet label length, LDH, leading/trailing hyphen, the reserved hyphen-3-4 rule with its xn-- carve-out, all-numeric labels, 255-octet FQDN length, and RFC 2606/6761 reserved names. EVERY RESPONSE REPORTS THE VERSION AND DATE OF EVERY TABLE CONSULTED -- Unicode UCD version, Scripts.txt version, confusables revision and date, IANA TLD list version and date -- because reference-data currency is the whole point: confusable tables and the root zone change, and a sealed sandbox cannot refresh them. Every response also carries an Ed25519-signed reproducibility receipt (input hash, output hash, table versions, timestamp). Free preview at /v1/preview: one name, same response shape, same signed receipt, no payment. THIS SERVICE DOES NOT TELL YOU WHETHER A NAME IS AVAILABLE OR REGISTERED. It performs no RDAP, WHOIS, DNS or registry lookup of any kind. It tells you whether a name is VALID, whether it is SAFELY DISTINGUISHABLE from look-alikes, and whether it satisfies the syntax and reserved-label rules of the TLD you name -- all computed offline from public Unicode and IANA tables. A name can pass every check here and already be registered. WHAT ELSE THIS DOES NOT DO, stated up front: (1) No registry, DNS, RDAP or WHOIS query is made at any point, so nothing here reflects who owns what. (2) It applies no trademark, brand or legal analysis -- a name can be technically safe and still infringe. (3) Confusability is judged against the Unicode confusables table, which is a published approximation of human visual confusion, not a rendering test in your font. (4) The same-script neighbourhood is capped and is a sample of nearby variants, never an exhaustive enumeration. (5) Registry-specific policies (per-TLD allowed script sets, premium or blocked lists, local presence rules) are NOT encoded -- only the syntax and reserved-label rules named above. (6) The signature proves origin and integrity, not correctness. (7) Answers are only as current as the table versions reported in every response.

Operated by Oddments. Paid per call in USDC on Base via x402.

## Output

Returns a JSON object containing per-label results (one per TLD checked), each with: a safe/unsafe verdict, per-check pass/fail breakdown with IDs and reasons, Unicode normalization details, per-character codepoint/script/category breakdown, UTS#39 skeleton and ASCII lookalike string, detected confusable characters with named witnesses, a confusable neighbourhood of near-identical variants, IDNA2008 validity, punycode A-label and round-trip decode, and a summary count of violated/satisfied checks. Also includes reference_data showing Unicode version, IANA source, and confusables table date. Responses are signed with an Ed25519 receipt.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "anyOf": [
      {
       "required": [
        "name"
       ]
      },
      {
       "required": [
        "names"
       ]
      }
     ],
     "title": "NameCheckRequest",
     "properties": {
      "tld": {
       "type": "string",
       "description": "optional TLD, e.g. 'com' or 'xn--p1ai'. Supplying it enables the IANA-root, FQDN-length and reserved-label checks."
      },
      "name": {
       "type": "string",
       "description": "a single candidate label; shorthand for names:[name]"
      },
      "names": {
       "type": "array",
       "items": {
        "type": "string",
        "maxLength": 63
       },
       "maxItems": 50,
       "minItems": 1,
       "description": "candidate labels. A LABEL, not a full domain -- 'example', not 'example.com'."
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "NameCheckResponse",
     "properties": {
      "receipt": {
       "type": "object",
       "description": "Ed25519 reproducibility receipt: 'input_sha256', 'output_sha256' (this body with 'receipt' removed), 'issued_at', engine table versions, 'key_id' and 'signature_b64'. Proves origin and integrity, not correctness."
      },
      "results": {
       "type": "array",
       "items": {
        "type": "object",
        "properties": {
         "idna": {
          "type": "object",
          "description": "IDNA2008 result: 'valid', 'a_label' (the punycode A-label), 'round_trip' (that A-label decoded back) and 'error'. On an encoding failure 'valid' is false, 'error' carries the reason and the other two stay null; 'valid' is null if the idna library was unavailable."
         },
         "input": {
          "type": "string",
          "description": "The candidate la
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "receipt": {
   "algorithm": "Ed25519",
   "input_sha256": "sha256 of your canonicalized request",
   "output_sha256": "sha256 of this response with 'receipt' removed",
   "signature_b64": "Ed25519 signature over the canonical signed_fields",
   "receipt_version": "oddments-receipt/1"
  },
  "results": [
   {
    "tld": "com",
    "idna": {
     "error": null,
     "valid": true,
     "a_label": "xn--pple-43d",
     "round_trip": "аpple"
    },
    "input": "аpple",
    "checks": [
     {
      "id": "confusable:ascii_homograph",
      "status": "violated",
      "observed": "skeleton 'apple' reduces to ASCII 'apple', which is NOT this label",
      "required": "the label does not visually imitate a different ASCII string",
      "skeleton": "apple",
      "ascii_lookalike": "apple"
     },
     {
      "…": "14 further rows, one per check"
     }
    ],
    "scripts": [
     "Cyrillic",
     "Latin"
    ],
    "summary": {
     "violated": 3,
     "warnings": 0,
     "satisfied": 12,
     "checks_total": 15,
     "failed_check_ids": [
      "script:single_script",
      "confusable:no_confusable_characters",
      "confusable:ascii_homograph"
     ]
    },
    "verdict": "unsafe",
    "skeleton": "apple",
    "mixed_script": true,
    "verdict_meaning": "'safe' means every VALIDITY and DISTINGUISHABILITY check passed. It does NOT mean the name is available -- see availability_disclaimer.",
    "confusable_characters": [
     {
      "char": "а",
      "name": "CYRILLIC SMALL LETTER A",
      "script": "Cyrillic",
      "codepoint": "U+0430",
      "ascii_target": true,
      "confusable_with": "a",
      "target_codepoints": "U+0061"
     }
    ],
    "confusable_neighbourhood": [
     {
      "with": "U+0061",
      "script": "Latin",
      "variant": "аpple",
      "position": 0,
      "replaced": "U+0430",
      "with_name": "LATIN SMALL LETTER A"
     }
    ]
   },
   {
    "input": "my-name",
    "summary": {
     "violated": 0,
     "failed_check_ids": []
    },
    "verdict": "safe"
   },
   {
    "input": "раypal",
    "verdict": "unsafe",
    "skeleton": "paypal"
   }
  ],
  "reference_data": {
   "iana_source": "data.iana.org/TLD/tlds-alpha-by-domain.txt",
   "idna_library": "python idna (IDNA2008/UTS46)",
   "iana_tld_count": 1438,
   "scripts_source": "/usr/share/unicode/Scripts.txt",
   "unicode_source": "python unicodedata (UCD 15.0.0)",
   "unicode_version": "15.0.0",
   "confusables_date": "2025-07-22, 05
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/name-safety-checker-idn-homograph-registrability-9fd6bcda/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from s5.oddments.ai](https://www.zero.xyz/host/s5.oddments.ai/llms.txt)
