DNS × IPFS × ENS
Three naming systems, one goal: get humans to your content. Here's how they fit together — and when to use each.
The big picture
| System | What it is | Best for |
|---|---|---|
| DNS | Traditional internet phone book (heavens.tools → server IP) | Fast CDN hosting, Cloudflare, GitHub Pages, email |
| IPFS | Content-addressed storage (CID fingerprint of your files) | Censorship-resistant, immutable site bundles |
| ENS | On-chain names (you.eth) that can point to wallets, IPFS, or DNS | Web3 identity, portable sites, NFT metadata |
| eth.limo | Public gateway: you.eth.limo → your ENS content hash | Browsing ENS sites without plugins |
Path A — Web2 DNS (Cloudflare / GitHub)
Build your site
Use the Heavens Tools builder or any static HTML. Export or download.
Deploy to a host
Cloudflare Workers/Pages, GitHub Pages, Netlify, etc.
Point DNS
Your registrar or Cloudflare DNS maps www.yoursite.com → host.
Cloudflare guide → · GitHub Pages guide →
Path B — Web3 ENS + IPFS
Build & export
Static HTML folder from the builder (or any site generator).
Pin to IPFS
Upload → get a CID like Qm…. Use Kubo, Filebase, 4Everland, or a pinning service.
Set ENS content hash
In the ENS app, set your name's content record to ipfs://Qm…
Visit via gateway
Open yourname.eth.limo in any browser — eth.limo resolves ENS → IPFS for you.
IPFS vs IPNS vs content hash
From the eth.limo docs:
- IPFS CID — Immutable. Change one byte → new CID → update ENS (on-chain tx).
- IPNS — Mutable pointer. Update what IPNS resolves to without changing the ENS record.
- Content hash — The value stored on ENS linking
name.ethto IPFS/IPNS content.
DNS + ENS together
ENS supports DNSSEC import — you can bring .com, .art, .xyz names into ENS. Many projects use:
heavens.tools(DNS) → Cloudflare for the builder & hubheavens.eth(ENS) → IPFS CID for a decentralized mirror
Same content, two front doors. Users on Web2 hit DNS; users on Web3 hit ENS + eth.limo.
What is a dWebsite?
A dWebsite combines ENS (human-readable name), IPFS (distributed hosting), and optionally a gateway like eth.limo so normal browsers work. Smart contracts can add dynamic behavior — but most Heavens Tools projects start as static HTML pinned to IPFS with an interactive animation_url for NFTs.