FREENAME · API RESOLUTION

From a readable name to Web3 records.

web3domain.it includes a Cloudflare Pages Function that forwards requests to Freename’s public resolver, allowing the frontend to read records without exposing secrets.

EXPLAINED WITH EXAMPLES

From a readable name to Web3 records., in practice

The goal of this section is to turn the concept into an operational picture: what it means, where it can be useful and what to verify before adopting it in a real project.

01

What it changes

Focus on the concrete difference compared with a traditional Web2-only approach.

Example: map the user journey before choosing the technology.
02

Where it fits

Evaluate the use case, the audience and the tools that actually support the experience.

Example: identity, payments, tokenized assets or decentralized content.
03

What to verify

Check compatibility, custody model, costs, security and the operational steps required after setup.

Example: test the complete flow on mobile and desktop before launch.

Connect wallet

The connection is non-custodial and happens directly in your browser through the wallet provider. After your consent, the page can read the public address required for the session; web3domain.it never asks for seed phrases or private keys, does not custody funds, and does not store the address in a site database.

Seed phrases and private keys remain in your wallet and must never be entered on web3domain.it.