A Honduran ccTLD Joins the Network
On May 13, 2026, NameBlock — the domain blocking platform helping registries and rights holders proactively prevent abusive and unauthorized registrations — announced a new collaboration that will enable .HN to offer NameBlock’s protection services, including AbuseShield and BrandLock, giving businesses, brands, and organizations stronger tools to safeguard their digital identities within the Honduran namespace. The announcement dropped from Oslo and Tegucigalpa simultaneously, which tells you something about how NameBlock has structured its geographic ambition: a Nordic technology company that operates as the connective tissue between national registries and the brand protection economy.
Dr. Wilmer Reyes, Executive Director of Red de Desarrollo Sostenible - Honduras (RDS-HN), framed the deal plainly: “At .HN, we are committed to strengthening the value and trust of Honduras’ digital presence. Partnering with NameBlock allows us to introduce an additional layer of protection for businesses, institutions, and brand owners operating in our namespace. This agreement supports our long-term vision of providing secure, reliable, and forward-looking registry services for Honduras.” The agreement identifies RDS-HN as the registry operator of .HN, headquartered in Tegucigalpa, Honduras, while NameBlock will provide the platform, reseller support, and technical services required to deliver blocking solutions to market. That tripartite structure — Oslo platform, local registry, shared revenue — is the NameBlock model. It is repeatable, modular, and expanding fast.
The .HN deal is not a one-off. NameBlock has been adopted by 85+ domain registries and registrars. In December 2025, five months before this announcement, NameBlock launched a Trademark Blocking Suite — a unified protection system designed to help trademark owners safeguard their brands across eighteen global top-level domains, including .bond, .buzz, .cfd, .cv, .cx, .cyou, .fans, .icu, .ke, .one, .qpon, .ruhr, .rw, .saarland, .sbs, .wang, .ws, and .lk. The Trademark Blocking Suite is available through participating registrars including CSC, Markmonitor, Lexsynergy, Com Laude, Safenames, 101Domain, Gandi, and more. That is a significant distribution footprint for a company that formally launched only in March 2024. The .HN partnership adds another entry to a partner map that keeps growing — but that map has no machine-readable layer.
What Exists Onchain — and What Doesn’t
NameBlock sells protection across both traditional and emerging namespaces. NameBlock currently offers three primary services: BrandLock — exact match blocking across selected domain extensions; AbuseShield — variant blocking across selected domain extensions; and BrandLock for Freename — Web3 domain blocking across blockchain-based naming systems. The Freename integration is the relevant onchain thread here. NameBlock’s BrandLock service is fully integrated with Freename’s Web3 extensions, marking a step in proactively safeguarding brand identities in the rapidly evolving world of Web3. There are three BrandLock for Freename packages: FreenameALL offers protection by blocking a label across all existing approximately 16,800 Web3 TLDs hosted by Freename; Freename4k provides essential brand protection across a fixed list of 4,000 Freename Web3 TLDs.
So NameBlock does touch the onchain world. It does so as a service provider — helping brands block their marks inside Web3 namespaces they do not control, on a platform someone else operates. That is a different thing from having an onchain TLD of your own. BrandLock blocks exact-match domains across one or several extensions — gTLDs, ccTLDs, and Web3 — in a unique pay-per-TLD model. NameBlock enables this. It does not hold a position in the layer it is helping others navigate. There is no .nameblock onchain. There is no partner.nameblock anywhere in any naming system — traditional or distributed. The company’s own partner identity layer is entirely DNS-dependent: press releases, a website, a list of resellers that a human can read and that no machine can verify without scraping.
That is the gap. Not a catastrophic one. Not one the market is punishing them for today. But a gap that becomes structurally significant as the internet moves from human-readable trust signals toward machine-verifiable ones.
The Use Case That Isn’t Being Served
Here is the concrete problem. A compliance tool, an AI agent, or an automated brand protection system wants to verify whether .HN is an active NameBlock partner. Right now, it cannot do that programmatically without hitting a press release from Access Newswire or scraping nameblock.com’s registry page. NameBlock connects to a backend service provider and then maintains domain block lists as they are created, renewed, or deleted. Blocked domains don’t resolve or have a WHOIS/RDAP entry. The irony: NameBlock’s own partner relationships have no RDAP entry either. They live in HTML. They depend on someone updating a webpage.
Consider what partner.nameblock — as an onchain-resolvable second-level domain under a registered .nameblock TLD — could actually do. It could carry a structured record: a list of active registry integrations, with activation dates, service types (AbuseShield, BrandLock, BrandLock for Freename), and revocation status. Any tool with a resolver could query it. No scraping. No parsing press releases. No waiting for a human to update a partner page. The data would be onchain, immutable once written, auditable without an API key, and readable by any system that can talk to a blockchain name resolver.
This is precisely the kind of use case that the x402 and ERC-8004 stack is being built to serve. ERC-8004 defines a lightweight on-chain registry system that enables AI agents to be discovered, evaluated, and collaborate across organizations and platforms without relying on centralized intermediaries. ERC-8004 and x402 form a complete autonomous transaction loop: ERC-8004 answers “who you are” and “how trustworthy you are” through on-chain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments. The domain namespace is the anchor for both. An AI agent operating in an agentic commerce stack doesn’t read a website. It resolves a name, reads a record, and either proceeds or doesn’t. In May 2025, Coinbase, in collaboration with Cloudflare, officially launched the x402 protocol. In September, they partnered to announce the formation of the x402 Foundation. Google subsequently integrated x402 into the Agent2Agent (A2A) protocol and released the Agentic Payments Protocol. The major infrastructure players are already building toward machine-native identity verification as a baseline assumption.
Autonomous software agents capable of executing transactions on behalf of users are giving rise to agentic commerce, an emerging paradigm where AI agents engage in buying and selling with minimal human involvement. However, traditional online payment systems assume a human is always behind the request and are thus ill-suited for agent-led transactions. What is true of payment systems is equally true of partner verification systems. If a compliance agent needs to check whether a given ccTLD registry has an active NameBlock relationship before flagging a domain abuse report, it should be able to do that in one resolver call. Today, it cannot. The data doesn’t exist in any form an agent can trust without a human in the loop to verify it. X402 is enabling the rise of agentic commerce, where autonomous agents pay one another for data, services, or compute in real time. This machine-to-machine economy is still early, but x402 provides the payment primitive needed to make these cross-agent transactions simple, verifiable, and fully automated. A partner directory that agents can query isn’t a luxury feature. In the direction the internet is moving, it is table stakes.
The competitive situation makes this more pointed. NameBlock’s closest analogues in the blocking space — DPML from Identity Digital, GlobalBlock from the Brand Safety Alliance — also lack onchain TLDs. CoCCA, which makes registry software used by 57 ccTLDs, has announced its support for NameBlock’s services. The Brand Safety Alliance, a GoDaddy-led initiative, provides blocking coverage in hundreds of TLDs — over 560 at the current count — with prices starting at about $6,000 a year retail. While GlobalBlock and NameBlock are certainly operating in the same space, there appears to be enough variation between the two services that the market might be able to support both. None of them have solved the onchain partner identity problem. The first one to establish a machine-readable onchain partner registry — as a named, resolvable TLD with structured second-level records — builds a moat that a press release cannot replicate and that a competitor cannot easily copy without doing the same work. Right now, the moat is unbuilt.
The Dry Math
NameBlock’s value proposition is trust. Its solutions are designed to help stop harmful lookalike registrations, impersonation attempts, typo abuse, and unauthorized use of protected names before they happen — reflecting a shared commitment to building a safer and more reliable domain ecosystem. That is a compelling proposition, and the 85-plus registry and registrar relationships suggest the market agrees. The .HN deal extends NameBlock’s reach into Latin America with a legitimate national registry operator running critical digital infrastructure for Honduras. The announcement language is careful and deliberate. The company is building something real.
But the company selling namespace trust does not have a trustworthy, machine-readable representation of its own partner network. A continuously updated list of accredited resellers can be found on NameBlock.com. A webpage. Updated by humans. Readable by humans. Opaque to agents. In 2024, that was fine. The agent economy had its most consequential month in January 2026, when three foundational layers converged — x402 payments, onchain identity, and autonomous agents. The infrastructure for machine-native verification is no longer theoretical. It is in production. It is processing transactions. It is resolving names. NameBlock is in the business of identity protection at the namespace layer. That business is about to be judged by machines as well as by humans. A company that helps others protect their names online has not yet staked its own.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.