Name-Safety Checker (IDN / Homograph / Registrability)

API ↗

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.

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.