# ENS lookalike names and normalization: checking what you resolve

ENS name normalization turns allowed input into a consistent form and rejects disallowed sequences before name processing. ENSIP-15 handles rules beyond simple lowercasing, including Unicode constraints. Normalization helps applications agree on the name being looked up; it does not prove the name owner is the person or organization you intend to pay.

Evidence: [ENS name processing](https://docs.ens.domains/resolution/names/)

Canonical: https://degreesofsatoshi.com/encyclopedia/ens-name-normalization/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Consistency:** Normalization precedes reliable name hashing and lookup. ([ENS name processing](https://docs.ens.domains/resolution/names/))
- **Unicode:** ENSIP-15 is more than converting ASCII capitals to lowercase. ([ENS name processing](https://docs.ens.domains/resolution/names/))
- **Identity:** A syntactically valid name is not an identity certificate. ([ENS name processing](https://docs.ens.domains/resolution/names/); [ENS terminology](https://docs.ens.domains/terminology/))

## Use an ENS-aware implementation

Names are human-facing Unicode strings, while contracts and resolvers work with processed identifiers. Different text representations must be handled consistently where the specification treats them as equivalent; invalid combinations should be rejected.

A custom “lowercase and hash” function can miss these rules. Use a library that implements the applicable ENS normalization standard instead of inventing a simplified parser.

Evidence: [ENS name processing](https://docs.ens.domains/resolution/names/)

## Case normalization is the easy example

For a simple ASCII illustration, Example.EtH normalizes to example.eth. That familiar case should not be mistaken for the full algorithm: Unicode characters and permitted combinations require the broader rules.

When a wallet rejects a pasted name, do not silently remove unknown characters until something resolves. Confirm the intended name through a trusted source.

Evidence: [ENS name processing](https://docs.ens.domains/resolution/names/)

## Validation and recognition answer different questions

A normalized name can still be the wrong legitimate name for your intended recipient. Technical validation checks the naming rules, not the sender’s relationship with an organization.

Compare the full name and the resolved destination in the payment context. ENS spelling rules complement address and identity checks rather than replacing them.

Evidence: [ENS name processing](https://docs.ens.domains/resolution/names/); [ENS terminology](https://docs.ens.domains/terminology/)

## Questions

### Is every visually similar Unicode name the same ENS name?

No. Normalization has specific allowed mappings and rejection rules. Visual similarity alone does not establish that two strings identify the same name.

Evidence: [ENS name processing](https://docs.ens.domains/resolution/names/)

### Can normalization confirm that a name belongs to a company?

No. It checks how a name is represented and whether the input is permitted. Organizational identity requires a separate reliable association.

Evidence: [ENS name processing](https://docs.ens.domains/resolution/names/); [ENS terminology](https://docs.ens.domains/terminology/)

## Claims and scope

### ens-name-normalization-quick-answer

ENS name normalization turns allowed input into a consistent form and rejects disallowed sequences before name processing. ENSIP-15 handles rules beyond simple lowercasing, including Unicode constraints. Normalization helps applications agree on the name being looked up; it does not prove the name owner is the person or organization you intend to pay.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### ens-name-normalization-fact-consistency

Consistency: Normalization precedes reliable name hashing and lookup.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### ens-name-normalization-fact-unicode

Unicode: ENSIP-15 is more than converting ASCII capitals to lowercase.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### ens-name-normalization-fact-identity

Identity: A syntactically valid name is not an identity certificate.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [ENS name processing](https://docs.ens.domains/resolution/names/) — ENS Labs. Normalization establishes consistent valid names, not identity authentication. Locator: Normalization; ENSIP-15; namehash. Retrieved: 2026-10-02T18:55:25.506Z.
- [ENS terminology](https://docs.ens.domains/terminology/) — ENS Labs. Roles in ENS naming, resolution and management. Locator: Owner; controller; resolver; registrant. Retrieved: 2026-10-02T18:55:25.181Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “ENS lookalike names and normalization: checking what you resolve.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ens-name-normalization/