Sixty Day ICANN Lock The Surprise Rule That Breaks Domain Deals

Few things derail a promising domain sale quite as abruptly—or as embarrassingly—as the moment a seller discovers the domain cannot be transferred because it is trapped under the infamous 60-day ICANN lock. This rule, enforced at the registry level and honored by all ICANN-accredited registrars, is one of the most widely misunderstood elements of domain ownership. It is also one of the most common hidden landmines waiting to explode in the middle of an otherwise solid deal. Many sellers do not learn about the lock until a buyer attempts to initiate transfer during escrow or asks for an inter-registrar transfer as a condition of sale. The seller then receives a notification that the transfer cannot proceed because the domain is within the mandatory lock period triggered by either a recent registration, a recent transfer, or certain WHOIS (contact) changes. What follows is confusion, anger, blame, and—in too many cases—a deal that falls apart due to nothing more than timing ignorance.

The 60-day lock exists for legitimate reasons: ICANN designed it to prevent domain theft, fraudulent transfers, unauthorized owner changes, and malicious hijacking. Unfortunately, the rule operates with the kind of rigidity that punishes even honest, competent sellers who simply aren’t aware of the timing constraints. Once the lock is active, there is no override, no appeal, and no workaround. Not even the registrar can remove it unless the buyer and seller had explicitly opted out before the change that triggered it. Once triggered, it is absolute. This inflexibility often blindsides sellers who assume domain transfers are as flexible as pushing a button in the registrar dashboard. They are not—especially across registrars.

The most painful version of this timing disaster occurs when a seller transfers a domain into their preferred registrar shortly before listing it or shortly before engaging in negotiations. Many investors consolidate portfolios at convenient moments without realizing that every transfer resets the 60-day timer. If a strong buyer appears days later and demands a registrar-to-registrar transfer, the seller is trapped. The buyer may have corporate requirements to hold all domains under a single registrar. They may have security policies preventing them from managing assets across multiple registrars. They may have internal DNS or IT processes tied to one specific platform. When told the domain cannot be transferred for 60 days, some buyers simply walk away.

Another form of trouble arises from contact-information changes. Many registrars automatically impose the ICANN lock when the registrant name, organization, or email is updated. This lock activates even if the domain remains at the same registrar and even if the change is simply correcting a typo or updating an old email address. Sellers who update contact information as part of portfolio maintenance often trigger the lock without realizing the implications. Then, during negotiations, they learn the domain cannot be transferred until the lock expires. Worse, some registrars hide or bury the opt-out checkbox during the update process, causing sellers to skip it unintentionally.

There is also the scenario involving newly registered domains. Fresh registrations are automatically locked for 60 days. Sellers who hand-register domains or acquire them through drop-catch services often assume they can flip them instantly on the open market. While intra-registrar pushes are allowed, inter-registrar transfers are not. If a buyer insists on moving the domain to their preferred registrar—and some do, for compliance or IT reasons—a new registration becomes temporarily illiquid. That is a rude awakening for sellers who pride themselves on quick flips.

Buyers often misunderstand the lock as well. They sometimes believe the seller is being evasive or dishonest. They suspect the seller is delaying intentionally to renegotiate price or fish for a better offer. They might think the seller is inexperienced and therefore unreliable. Even when the buyer understands the rule intellectually, they may feel uneasy committing funds to a domain they cannot control fully until the lock expires. This psychological discomfort can be enough to ruin a deal.

Timing issues become especially dangerous when escrow is involved. A buyer who funds escrow assumes the transfer will begin quickly. If the seller or escrow discovers the lock afterward, the buyer may lose trust in the seller or become anxious about the status of their funds. Escrow providers typically allow transactions to sit in limbo for extended periods, but buyers rarely have the patience to wait 45, 50, or 60 days for completion. Slow legal teams, technical constraints, and internal approvals compound the problem. A delay caused by the ICANN lock can push a buyer over their internal timeline, causing them to abandon or renegotiate the deal.

The lock also causes practical workflow disruptions. Some registrars will not allow a push if the domain is in certain parts of the expiration or renewal cycle. If the domain expires during the lock period and the seller fails to renew on time, the domain may enter redemption. A domain in redemption cannot be transferred even after the lock expires until it is restored—a costly process. Sellers in negotiation must juggle these timing obligations, and failure to do so can escalate one timing problem into multiple overlapping ones.

The unpleasant part for sellers is the helplessness. Unlike payment delays, legal reviews, or negotiation standoffs, the ICANN lock is not negotiable. No argument, escalation, or customer-service call will remove it once activated. Registrars are bound by policy. Escrow cannot override it. The buyer cannot waive it. Even if all parties agree, the lock remains in place. Thus, the seller must navigate around it rather than through it.

Fortunately, while the lock cannot be removed, its impact can be mitigated through strategic negotiation, proper framing, and process transparency. The first key is proactive disclosure. Sellers who verify the lock status before entering serious negotiation can communicate the situation early. Buyers rarely appreciate surprises. But when the issue is explained upfront—before the buyer commits emotionally or financially—they are far more likely to accept a temporary limitation. Sellers can say the domain is fully transferable via registrar push now and via registrar-to-registrar transfer after the lock expires. This positions the lock as a logistical detail rather than a red flag.

Another strategy is shifting the mode of transfer. If a registrar push is acceptable to the buyer, the deal can proceed immediately. Many buyers accept pushes, especially when they trust the registrar’s security. Corporate buyers may resist pushes, but independent entrepreneurs, startups, and small businesses are often flexible. A registrar push bypasses the ICANN lock entirely because the domain does not leave the registrar; it only changes accounts within the same system.

Sellers can also manage expectations by aligning escrow timelines with the lock period. Some deals can move to escrow now, with the understanding that the transfer will occur once the lock expires. This works best when the buyer is patient and when the domain’s value justifies the wait. Of course, the seller must maintain impeccable communication during the lock period to ensure trust does not erode.

Sellers should also avoid harmful behaviors triggered by anxiety around the lock. They should never transfer early due to buyer pressure. They should never attempt evasive tactics such as switching registrars again or attempting to circumvent the lock rules. These will only make the situation worse and may destroy the buyer’s trust entirely. Honesty and clarity are the only effective approaches.

Even with best practices, some buyers will still walk away. And this is where sellers must accept reality: some deals collapse not because of price, trust issues, or negotiation errors but because of immutable timing constraints. This does not reflect the seller’s competence. It reflects the rigid architecture of domain transfer rules.

The long-term solution is operational awareness. Sellers must treat registrar transfers, WHOIS updates, and fresh registrations as events that freeze liquidity. That means never transferring domains between registrars unless absolutely necessary and never making ownership-data changes casually. Regular portfolio audits, a structured renewal process, and meticulous timing checks before listing premium domains can prevent the lock from jeopardizing deals.

It is equally important for sellers to educate themselves about registrar-specific rules. Some registrars provide an opt-out for the lock when updating contact information; others do not. Some registrars automatically enforce additional restrictions beyond ICANN’s requirements. Understanding these nuances reduces surprises.

Ultimately, the 60-day ICANN lock is not a deal-killer by nature; it becomes one only when it is discovered too late. Sellers who anticipate it, verify lock status early, disclose it transparently, and negotiate transfer methods with flexibility can keep their deals alive. It is not the lock itself that destroys transactions—it is the shock of the unexpected, the loss of momentum, and the erosion of trust that follow. Good domain sellers eliminate surprises by mastering the timing realities of the assets they manage. In a business where timing is often everything, this small slice of knowledge can mean the difference between a smooth sale and a deal that collapses under the weight of a rule no one sees until it is too late.

Few things derail a promising domain sale quite as abruptly—or as embarrassingly—as the moment a seller discovers the domain cannot be transferred because it is trapped under the infamous 60-day ICANN lock. This rule, enforced at the registry level and honored by all ICANN-accredited registrars, is one of the most widely misunderstood elements of domain…