Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Ethereum · Entry 245

ENS lookalike names and normalization: checking what you resolve

AI-assisted research · separate automated verificationCorrections

Theme
Ethereum
Sources
2 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for ENS lookalike names and normalization: checking what you resolve
FactDetailSource
ConsistencyNormalization precedes reliable name hashing and lookup.[1]
UnicodeENSIP-15 is more than converting ASCII capitals to lowercase.[1]
IdentityA syntactically valid name is not an identity certificate.[1][2]
01

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.

02

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.

03

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.

Direct answers

Questions people ask

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.

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.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

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: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Consistency: Normalization precedes reliable name hashing and lookup.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

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

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Identity: A syntactically valid name is not an identity certificate.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. ENS name processingENS Labs

    Normalization establishes consistent valid names, not identity authentication.

    Locator: Normalization; ENSIP-15; namehash · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.506ZOpen source
  2. ENS terminologyENS Labs

    Roles in ENS naming, resolution and management.

    Locator: Owner; controller; resolver; registrant · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.181ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

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/