.bill
Is .bill a real TLD? Who’s applying to run it?
Nobody has applied for .bill in its own right, as of 7 October 2026. Link Freedom Group named .bill as the backup string of its .api application.
A clear payments-and-invoicing word, useful for billing tools and pay pages, but few companies would make it their main web address.
billing, invoicing, and payments software companies wanting a literal product-style address (pay.bill-type constructions), plus utilities and service firms building branded payment pages; secondarily, people named Bill picking a vanity identity.
Nobody has applied for .bill in its own right.
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Settle up, move on.”
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a short, single-word generic verb/noun sitting directly on the money-movement transaction, whose value depends on payment processors, banks and billers wanting a functional namespace for the act itself rather than a category directory.
Same class of bet — an everyday one-syllable money noun with dual literal/idiomatic readings that anyone in consumer finance could brand on — but it names the instrument rather than the recurring obligation, so the registrant pool is broader and less operational.
Also a plain generic finance noun open to any registrant, betting that the category word itself is the identity, though it is the abstract umbrella term where the target is a specific transactional artifact with narrower, more utility-driven use.
What a .bill domain is
.bill is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. Nobody has applied for .bill in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .bill domain extension real yet?
.bill is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .bill domain?
You can’t yet. A .bill name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .bill was .pay, delegated on 10 August 2016.
Is .bill a real TLD?
Not yet. .bill is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .bill as part of an application for another string. Every entry on this page links to its source.
- Link Freedom Group · now replacementICANN
- Link Freedom Group · first recordedLink Freedom Group
“LFGL2683T-T89949 · Link Freedom Group Ltd · replacement string of .api”ICANN
“.bill · Commerce · “Settle up, move on.””Link Freedom Group
- Band chosen: usable but limited (30-49). The string is a common, unambiguous English commerce word with an obvious semantic fit for invoicing, payments, and bill-pay flows, which puts it above the vanity/joke band: a billing SaaS or a utility's payment portal could plausibly register and even use one as a functional address, and 'yourname.bill' reads naturally in a pay-this context. It falls short of the strong-niche band because, by analogy with earlier finance-flavored generic TLDs (the .money/.cash/.loans family), such strings have tended to see low registration volumes, thin aftermarkets, and almost no primary-identity adoption: serious fintechs brand on .com and treat category words like this as redirects or campaign pages at best. The noun/verb also carries a mild negative valence (a bill is something you owe), which weakens it as a brand suffix, and the personal-name reading (Bill) fragments demand without adding serious buyers. Applicant context: the string is one entry in Link Freedom Group's large 2026-round portfolio, filed under category Commerce with the tagline 'Settle up, move on.', which is consistent with a functional-payments positioning but tells us nothing yet about registrar distribution or pricing. Main market uncertainty: whether embedded bill-pay providers and agent-driven payment flows adopt semantic addresses at all over the next 5 years; if machine-readable payment endpoints start favoring descriptive TLDs, a literal string like this gains real utility, but that behavior is unproven.