Security & Trust

IDN and homograph analysis API

Analyse an internationalized domain name with one request. Get the Unicode and punycode forms, per-label scripts, lookalike characters, a confusable skeleton and a risk level.

View documentation Try the free tool Explore all APIs

Endpoints Active

GET /v1/idn

Example request

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/idn?domain=xn--80ak6aa92e.com"

Example response 200 OK

{
  "unicode": "аррӏе.com",
  "ascii": "xn--80ak6aa92e.com",
  "is_idn": true,
  "valid": true,
  "skeleton": "apple.com",
  "risk": { "level": "high", "reasons": ["idn_label", "whole_script_confusable"] }
}

Example request GET /v1/idn

Key Features 4

Frequently asked questions 4

HTTP status codes 200 / 400 / 401 / 402 / 429

Category Security & Trust

Endpoints 1

Key Features 4

Frequently asked questions 4

Used by people at these companies

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose domain intelligence to AI agents and internal assistant workflows.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

domain

Response fields

Example response

unicodeasciiis_idnvalidskeletonriskrisk.levelrisk.reasons

Status coverage

HTTP status codes

200400401402429

Endpoints

GET /v1/idn

Credits: 1Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign up for free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

UTS 46 conversion

Converts Unicode and punycode both ways and checks label and name length limits.

Script and character checks

Lists the scripts in each label, flags mixed-script labels outside the allowed CJK combinations and detects invisible characters.

Confusable skeleton

Maps lookalike Cyrillic, Greek, Armenian and fullwidth characters to their Latin look, so you can compare a name with the brand it imitates.

No network calls

The analysis runs entirely on DomScan, so results are instant and identical for the same input.

Example request

GET /v1/idn?domain=xn--80ak6aa92e.com bash

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/idn?domain=xn--80ak6aa92e.com"

Example response

200 OK json

{
  "unicode": "аррӏе.com",
  "ascii": "xn--80ak6aa92e.com",
  "is_idn": true,
  "valid": true,
  "skeleton": "apple.com",
  "risk": { "level": "high", "reasons": ["idn_label", "whole_script_confusable"] }
}

Frequently asked questions

When is the risk high?

When a label mixes Latin with Cyrillic, Greek or Armenian, when a non-Latin label reads entirely as Latin letters, or when it contains invisible characters.

Is the full Unicode confusables list used?

No. A curated subset of the most common lookalikes is used, and every response says so, so a low risk result is not proof of safety.

Can I send punycode?

Yes. Send either form and both are returned, along with whether each label is an IDN.

How many credits does it cost?

One credit per request.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Analyse a domain

Start free View documentation Try the free tool