The Announcement
NameBlock announced that its BrandLock service is now fully integrated with Freename’s Web3 extensions — a move the Oslo-based company framed as a significant step for brand identity protection across decentralized namespaces. The announcement, dated August 28, 2024, came in the context of new challenges in intellectual property and trademark protection brought about by Web3 domains and top-level domains.
The framing was direct. CEO Pinkard Brand said: “The ever-expanding Web3 universe presents a challenge to brands to ensure their digital presence is consistent and uncontested as there are no standard rights protection mechanisms in place.” That is accurate. It is also, as this piece will outline, a problem that applies to NameBlock itself. Through the partnership, Freename and NameBlock designed a set of blocking packages intended to prevent the unauthorized use of a brand’s name across Freename’s extensive network of Web3 extensions. The product line comes in three tiers. FreenameALL blocks a label across all Web3 TLDs currently existing on the Freename platform — cited as approximately 16,000-plus TLDs as of August 2024 — with the block automatically applying to all future Web3 TLDs created on the platform during the subscription term. Freename4K offers defense across 4,000 key TLDs, and Freename100 secures an exact match label across 100 essential TLDs. The pitch is defensible cost efficiency. NameBlock’s CEO stated that “BrandLock product integration with Freename is far less costly compared to resources needed to register, manage, and maintain each Web3 domain name in hundreds if not thousands of extensions.”
Freename’s side of the announcement was candid in its own way. Davide Vicini, CEO and Co-Founder at Freename, acknowledged that “enforcement options in this decentralized world can be challenging.” That admission matters. It sets the operational context. The partnership is a workaround for a structural gap — the absence of rights protection mechanisms native to the Web3 layer — rather than a solution to the underlying architecture. Freename itself is a domain registrar based in Zurich, Switzerland, founded by Vicini and Mattia Martone in 2021, and is notably the first Web3 namespace to receive ICANN accreditation. The platform uses DNS technology compatible with blockchain networks including Polygon, Solana, Base, Chiliz, and BNB Chain, as well as browsers such as Google Chrome and Safari. By the time of the BrandLock announcement, Freename’s namespace was large. Selling protection across it is a real commercial proposition. NameBlock made the move. That part is not the problem.
The TLD Question
The problem is simpler and harder to answer with a press release.
NameBlock operates as a brand protection and domain blocking service. NameBlock describes itself as a leading provider of domain blocking and trademark protection services, with products including BrandLock and AbuseShield. The product now covers Web3 namespaces. BrandLock for Freename is a set of security packages designed to prevent the unauthorized use of a brand’s name across Freename’s extensive network of Web3 TLDs, with the mechanism being the blocking of registration or minting of domain names that match the brand. That is the offer. The company sells protection in a layer it has not staked its own presence in.
No activated second-level domain (SLD) under .nameblock exists on Freename. The TLD .nameblock — the most natural onchain identity anchor for the company itself — is not registered or minted. More specifically, web3.nameblock does not exist. That is the SLD that would correspond most directly to NameBlock’s Web3-facing product line: a dedicated, chain-anchored identifier for the BrandLock Freename product, its terms, its supported chains, its coverage tiers, and its verification status. It is not there. NameBlock has not used its own tool on itself — or anything adjacent to it. BrandLock is marketed as a solution for anyone who wishes to protect an idea or product name online, with the mechanism being prevention of registration of identical domain names across multiple extensions — described as a strong proactive line of defense. The company describes proactive defense as the operative posture. Its own namespace does not reflect that posture.
This is not an accusation. It is an observation with structural consequences. The Web3 space that NameBlock is now serving is not just a threat surface for brands. It is also an identity layer. A company operating in that layer without a presence in that layer is asking its clients to trust an authority that does not itself exist onchain.
The Missed Use Case
The practical dimension of this absence becomes clearest when you consider how information flows in an agentic environment.
AI agents are now economic actors. The x402 protocol, developed by Coinbase and co-founded with Cloudflare in May 2025, transforms the long-dormant HTTP 402 “Payment Required” status code into a practical, blockchain-powered payment mechanism. Developed by Coinbase and Cloudflare, x402 enables AI agents and applications to pay for web services automatically using stablecoins like USDC, embedding payment instructions directly in HTTP headers and allowing settlement with zero protocol fees beyond minimal blockchain gas costs. The adoption curve is not slow. Launched in May 2025 by Coinbase and Cloudflare using USDC and EIP-712 signatures, x402 had processed over 115 million transactions as of early 2026.
The agent commerce stack is also developing an identity layer to accompany payment rails. The ERC-8004 standard, combined with the x402 payment protocol, enables autonomous agent-to-agent transactions and provides interoperable identity infrastructure — having launched on Ethereum mainnet in January 2026. ERC-8004 establishes three lightweight registries on-chain: an Identity Registry where each agent receives an on-chain ID based on an ERC-721 NFT, a Reputation Registry where feedback signals between agents are recorded on-chain, and a Verification Registry providing cryptographic proof of task completion. The relevant word in that architecture is verifiable. Agents do not read PDF documentation and trust it. They query endpoints. They resolve identifiers. They verify claims against on-chain state.
This is where the absence of web3.nameblock becomes a real operational gap. A brand team or an AI agent doing due diligence on NameBlock’s BrandLock coverage today has no chain-native endpoint to query. There is no SLD map. There is no machine-readable record of which Freename package tier is active, which chains are covered, or whether the FreenameALL block extends to newly created TLDs as claimed. That information exists in PDFs, on web pages, in press releases. It does not exist as a verifiable, immutable, chain-anchored record. In an environment where x402 provides cryptographic proof of not just payment, but who authorized it and for what purpose, a brand protection service that cannot anchor its own service terms to a verifiable onchain identity is running on trust rather than proof.
Consider what web3.nameblock could structurally be. Not a marketing page. Not a landing URL. An onchain record publishing NameBlock’s current Web3 blocking coverage in a machine-readable format — supported chains, active Freename package tiers, SLD maps, coverage update timestamps. Freename’s platform already uses proprietary technology for blockchain mirroring between Web2 domains and their on-chain identities, enabling Web3 use cases such as wallet resolution and crypto payments on tokenized Web2 domains. The infrastructure to anchor that record exists inside the very platform NameBlock has partnered with. The SLD web3.nameblock could be minted on Polygon, Base, or Solana — all chains supported by Freename’s proprietary DNS system, which ensures functionality across major blockchain networks including Polygon, Solana, Base, and BNB Chain while remaining fully compatible with mainstream browsers such as Chrome and Safari.
The speculative extension of this is worth stating plainly. Brand teams making purchasing decisions about BrandLock packages in 2025 and 2026 are operating in an environment where their own counsel, their compliance tools, and increasingly their autonomous procurement agents are capable of querying onchain records before committing. AI-powered services and agents are increasingly capable of browsing websites, consuming APIs, and transacting autonomously, yet they remain unable to pay for assets or services directly when legacy payment methods require human intervention — and when an AI hits a paywall or needs to purchase data, it currently must defer to a human, highlighting the lack of an internet-native, machine-friendly standard. x402 is closing that gap for payments. The adjacent gap — machine-readable identity verification for the services being purchased — closes when service providers anchor their own terms onchain. NameBlock has not done this. A procurement agent querying whether NameBlock’s Freename block covers a given chain, or whether the FreenameALL tier truly future-proofs against newly created TLDs, would find no authoritative onchain source. It would fall back to Web2 documentation. That is not verification. That is a trust assumption.
In 2024, Freename launched the service NOTO, in close beta, which crawls blockchain naming systems to compile lists of domain names and allows internet service providers such as browsers and wallets to resolve Web3 domains in a safe and interoperable way. Freename is building the resolution infrastructure. The companies selling services on top of that infrastructure are expected, eventually, to inhabit it. NameBlock sells the argument that brands must be proactive. After securing a label with BrandLock, it remains protected as long as it is renewed — and when ready, the owner has the flexibility to unblock it across one or multiple domain extensions. The argument for proactive presence is NameBlock’s own product thesis, applied outward to its clients. It does not yet apply inward.
The Dry Conclusion
NameBlock went to market with a product that covers over 16,000 Web3 TLDs. It cannot be verified via any of them.
The company’s CEO described the Web3 universe as a challenge for brands. That framing is correct. It is also a challenge for the services that manage brand identity in that universe — specifically, the challenge of existing in it with the same verifiability they promise their clients. The BrandLock Freename integration is a real product. The FreenameALL tier is a real offer. The enforcement gap Pinkard Brand described is real.
What is also real: web3.nameblock is an unresolved identifier. No SLD map lives there. No chain-anchored coverage record. No machine-readable endpoint for an agent to query before a procurement decision. The x402 protocol is processing millions of agentic transactions. ERC-8004 is establishing identity registries for autonomous agents. Freename is building resolution infrastructure that standard browsers can read. The layer is forming. The companies that operate in it will need to be findable in it.
NameBlock is not yet findable in it.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.