The only locks we actually enforce are the first 60 days of a domain's life.
The other locks of 60-day wait between registrants mainly exist to prevent fraudulent conveyance of a domain through daisy chain of registrar hopping that would make IRTP almost impossible for unwinding a domain sale.
For example, last night, we were informed by Web.com that a 5L brandable .com domain bought by a customer on May 12 at Sedo was stolen goods. The domain had just arrived.
In this case, the domain buyer should be able to get a refund from Sedo as a condition for unwinding that transfer. I am guessing Web.com will end up paying off Sedo if they can't track down the seller.
Now, imagine if between May 12 and today the domain had hopped between 3 or 4 registrars. It would have been almost impossible to unwind.
So, no, we don't enforce arbitrary locks and will almost always remove them upon request, but I believe that is the reason why the 60-day cooling off period exists.
For escrow transactions, we don't enforce these locks unless the buyer is paying with a credit card or PayPal where there are reasonable forensic concerns that the transaction is high risk.
The good news is that we actually take the time to review cases, and use increasingly smart analytics to manage those risks. The DNProtect.com project will take this very far in terms of:
- Domain Risk Assessment
- Domain Insurance
- Domain Monitoring for future impairment
@bhartzer is leading that for Epik -- a very ambitious project that is making steady progress.
See related info:
https://www.icann.org/public-comments/irtp-status-2018-11-14-en