DFINITY wants the Internet Computer to have its own top-level domain. On October 7, 2026, ICANN published its bid for .icp alongside 1,614 others, out of 1,615 bids for new TLDs. Nothing is approved. By most estimates the earliest a .icp site could load in an ordinary browser is 2028, and the record revenue headline from that same week comes out at about half on the network's own meter. I expected a launch story and found a paperwork story, and the paperwork is the more useful read if you are weighing crypto domain names.
What DFINITY actually filed
ICANN's public record lists the application as DS2698T-T60168, primary string "icp", status active, applicant DFINITY Stiftung of Zurich. On October 8 the page read "Active · Pre-Evaluation Processing". Applications went in between April and August 2026, and the window closed on August 12. October 7 was Reveal Day, when ICANN published every bid at once.
DFINITY stayed quiet for two days. A community member found the application on ICANN's site and posted it on the DFINITY forum at 18:18 UTC on October 7, eighteen minutes after the reveal, and an eight-page deck had gone up in the final two hours of the window. The announcement came on October 9 at 09:33 UTC: the application had passed ICANN's "initial review" and was public in the 2026 round. It added: "If approved, sovereign software and AI-ware get their own top-level domain."
Initial review is an administrative check that the paperwork and the fee are in order. It is not approval, and the post says so. The review of the string itself starts on November 17.
Anyone could register a .icp name through an ordinary registrar, because the TLD would be open. No one else applied for the same string, so there is no contention set, ICANN's term for two or more applicants chasing the same label. The filing says the TLD's primary intended use is for services that run on ICP, and gives less centralized trust assumptions as one reason. An open, uncontested string is a different proposition from a corporate brand land grab.
How a .icp name would work
Under ICANN's contract a .icp name would be an ordinary DNS name, not a token. The root zone sits at the top of the address system; the registry keeps the database of names; registrars sell them to the public; and the owner's DNS settings decide where visitors land. DFINITY's deck uses brand.icp as its example and says the name resolves through ordinary DNS to the same service the ICP identifier points to.
The ICP part starts behind the name. Under the proposed rule the front-end, meaning the pages a visitor loads, would be an app on the Internet Computer, reached through a gateway. A gateway turns a browser's ordinary request into a call the network can answer and hands back a page, which is how ICP apps reach people on ordinary browsers today.
The pointer problem
A domain in front of an ICP app can be repointed by whoever owns it. DFINITY's own security documentation warns that the owner can send it to a completely different web application, including one that does not run on ICP at all. Bob shows how that goes: bob.fun, the domain of the ICP app, expired on September 3, 2026, and OHSHII Labs, a team of ICP builders, warned users on September 13: "If someone buys the bob.fun domain, do not log in with Internet Identity on bob.fun or launch.bob.fun." On October 8 the app still listed bob.fun as a log-in address.
A name anyone can buy, sitting in front of a log-in page people already trust, is the gap the .icp rule aims at. When I land on a log-in page, the first thing I check is the address it will send my credentials to. A padlock says the connection is encrypted; it says nothing about who is behind the name.
The rule that every .icp site must prove it runs on ICP
DFINITY proposed what ICANN calls a Registry Voluntary Commitment. It would require every .icp website to be hosted on the Internet Computer within 90 days, every page it serves to carry a cryptographic receipt signed by the network, and a scanner to check at least once a month. A site that fails gets 30 days of warning before the name goes on hold.
Only the front-end is covered. Back-ends, in the filing's words, "may be hosted on any infrastructure". The rule does not tie a name to one canister, the unit of compute and storage on ICP, so any ICP app would satisfy it. The gateway checks the certificate rather than the browser, so a visitor who reaches the app another way sees no proof.
Of the 1,615 bids, five carry a Registry Voluntary Commitment by ICANN's own list, and only DFINITY's is about where a site runs. ICANN reviews the rule separately from the application, and without a yes, .icp is one more crypto TLD with a Swiss foundation behind it.
The clock: November 17, March 16 and 2028
| Date | What happens |
|---|---|
| October 7, 2026 | ICANN publishes all 1,615 bids on Reveal Day |
| November 17, 2026 | String Confirmation Day: ICANN publishes the final list of strings |
| November 27 | Last day to withdraw and recover 65% of the application fee |
| March 16, 2027 | Comment and objection window closes |
| First half of 2027 | Lottery sets the order in which applications are processed |
| End of 2027 | Simplest bids, with no extra reviews, reach a signed contract |
| 2028 | Earliest a .icp name could be delegated, by most estimates |
On November 17 the four-month comment and objection window opens, and a 180-day string review runs alongside it. Then the lottery, then contracting. Adding up ICANN's own processing times, the simplest bids with no extra reviews land at a signed contract around the end of 2027. .icp's rule adds a separate review, and delegation, the point where the string enters the root zone, comes after the contract.
Then there is the price of entry: $227,000 as a base fee, plus $15,000 to review the rule, and at least $25,750 a year to ICANN from the day the string enters the root. Withdraw by November 27 and ICANN refunds 65% of the application fee.
Most estimates put delegation in 2028 at the earliest, and ENS is among them. I read that as a floor. It assumes no objection, no trouble in the rule review and no delay in the lottery or contracting; any one of those pushes the date out.
Who holds the switch
Follow a .icp name from the top and several hands are on it. The root zone is kept by ICANN's technical arm and Verisign. ICANN holds the contract. The registry operator would be DFINITY Stiftung, a Swiss foundation whose filing names one person as director, executive and ultimate control: DFINITY's founder, Dominic Williams. Swiss register notices show one board member since December 2024, the same name. A back-end provider, the company that would run the technical plumbing, needs ICANN's approval; the name in the filing is confidential, and DFINITY was not on ICANN's list of evaluated back-ends as of October 6.
Below that sit registrars, the owner's DNS and an off-chain gateway. Past the gateway, the boundary nodes and the network under an app answer to a vote of the Network Nervous System, ICP's on-chain governance system. The app itself answers to a vote only if its developers put it under one. The filing names the NNS for the network and as the key its certificates trace back to, and gives it no registry role. Nothing in the public filing names who would run the registry day to day.
The history explains why that gap draws comment. In 2023 DFINITY's naming lead wrote that a .icp domain under ICANN would "still be centralized under ICANN", and that CNS, DFINITY's planned on-chain naming system, aimed to manage its root through a DAO. In November 2025, Williams wrote that he would like a name service "orchestrated by the Network Nervous System" and, longer term, "a .icp TLD assigned to the Internet Computer". ICANN's rules require a legal entity to apply, and a DAO cannot be the applicant on its own, so the foundation is the name on the form. Another bid in the round, .agent, ties its registry policy to an outside foundation; this one does not.
ICANN keeps the last word under the contract. It can install a stand-in operator in an emergency and terminate for cause. That is the counterweight to one person holding the Swiss side.
The other crypto projects in the same round
| String | Applicant | Notes |
|---|---|---|
| .icp | DFINITY Stiftung, Switzerland | Open TLD for services on ICP, with a hosting rule |
| .ada | Cardano, through a Swiss foundation | Community domain for ADA holders and Cardano builders |
| .ethereum | The Ethereum Foundation, through a Swiss foundation | Closed brand |
| .ens | ENS Labs | .eth was impossible, it is a country code |
| .sol, .solana, .sui, .ape | Red Rock, a Cayman foundation | The Solana Foundation endorsed the bid |
| .btc | Two companies | Competing bids for the same string |
| .crypto | Five applicants | Competing bids for the same string |
Cardano and Ethereum both went through Swiss foundations, as DFINITY did. ENS Labs filed for .ens; ENS could not apply for .eth, which is a country code. Red Rock filed four strings and got an endorsement from the Solana Foundation rather than a filing by the foundation itself. Two companies want .btc, five want .crypto. Unstoppable Domains, which sells blockchain names, filed nothing: ICANN's draft rules would have required its linked names to be registered and paid for in the DNS, and the company said, "We aren't willing to force that on our users or bill them for it."
The names already sold on ICP
Projects on ICP have sold on-chain .icp names since 2022. IC Naming moved to .ic that year. ICNS still holds 24,273 in a registry whose renewal canister has no code, and its own name expired in February 2025. The application does not mention them.
An ICNS name and a .icp name in the DNS are different things. One is an entry in a smart contract on ICP; the other would be a registration under ICANN's contract, sold by a registrar and resolved by every browser. Nothing in the filing connects the two.
ENS is the comparison most readers already hold. It maps a readable name to a wallet address and other records through smart contracts on Ethereum, and an .eth name is a token kept in a wallet. Ordinary browsers do not resolve .eth on their own, so those names mostly appear inside wallets and apps. A TLD filing works at a different layer: it changes what the DNS resolves for everyone, and only ICANN can grant it.
The "$360K record" on the network's own meter
The Internet Computer counts the cycles burned on it, and cycles are the fuel apps pay for compute and storage. Over the 30 days to October 7 the network burned about 135,000 trillion of them. It prices a trillion cycles at 1 XDR, an IMF unit worth about $1.35, which puts the total near $180,000.
On October 5 a tracker called Chainspect posted that the Internet Computer had crossed $360,000 in monthly revenue. Its word was milestone. Within days, news sites and an X news card were calling it a record. The network keeps a second, daily count of cycles that runs about 10% lower, and Chainspect's figure matches that count to the dollar if each trillion cycles is counted as one ICP token at ICP's market price that day. Chainspect defines revenue as the fees users pay; as of October 8 its site gave no method for ICP. DefiLlama, which does publish its method, reads $190,886 for the same 30 days on the same network count.
On the meter it is not a record. The meter is up about a quarter since late August, its highest since February, but January ran higher: about $450,000 even by the tracker's arithmetic, whose chart shows only 90 days. In January 2025, while proof-of-work mining ran on the network, the meter read more than 20 times today's rate. DFINITY's Mission 70 paper sets a target of 0.77 trillion cycles a second, and the current reading is under 7% of it, with a 30-day mean of 0.0521 trillion cycles a second on October 8. Since late August, Chainspect's line rose nearly 60% while cycles rose 18%, and the token's price carried the rest.
The method matters more than any single month. A number built on the token's daily price moves when the token moves, even if nobody burns an extra cycle.
Who is actually burning the cycles
About one cycle in seven is a bill being paid rather than a program running. The Swiss subnet's rent, paid by its tenant, burns every minute whether the subnet is used or not. The cloud engine fee burn is paid on-chain by DFINITY's billing accounts. On the hourly meter, the busiest day of those 30, October 7, owed its spike to a single bill, one cloud engine fee burn.
Counting DFINITY's own exchange, Multi/DEX, DFINITY's accounts fund about 9% of the meter. Follow the money of one top-up service and it may be up to a quarter. The rest is the tenant's rent, other projects' apps, and a share the creator could not trace.
I would not read a rising line as demand until I knew how much of it came from repeat payers. A total can climb on a few large accounts, and an account that tops up its own bill lands on the same line as a developer buying compute. A monthly figure on its own does not show how many independent teams are paying.
What I would check before the next headline
- November 17, 2026: ICANN publishes its final list of strings. If .icp is on it, the objection window opens and the bet gets real.
- March 16, 2027: objections close. One successful objection resets the timeline.
- The first half of 2027: the lottery sets the order, and a low position adds months.
- The contract: whether the hosting rule survives ICANN's review. Without it, .icp is an ordinary crypto TLD.
On the technical side, watch whether DFINITY names a back-end that appears on ICANN's evaluated list, because that company runs the plumbing a .icp name would depend on. On the money side, read the burn rate rather than the dollar headline: one trillion cycles a second equals 1 XDR a second, about $1.35, so 0.0521 trillion cycles a second works out to a few cents a second of network fees. Compare any figure with the 0.77 trillion cycles a second in Mission 70, and ask whether the count includes a token price.
Chris Yost holds ICP and uses .icp in his X display name. That matters when you weigh his verdict on the revenue figure. I keep the two claims apart anyway: a filing that may not resolve until 2028, and a monthly number that halves when you price it the way the network does.
