33 ms·
That's on the registry, not the registrar. Point your anger at whoever owns that TLD.
by 0x0000000 3y ago
That's on the registry, not the registrar. Point your anger at whoever owns that TLD.
- CharlesW 3y agoSo does your response mean (1) "take it easy on Namecheap because this kind of bait-and-switch is common among registrars", or (2) "take it easy on Namecheap because it was unintentional incompetence"?
- 0x0000000 3y agoI'm saying take it easy on Namecheap because it's out of their control, and would have happened regardless of the registrar you used for that particular domain. The incompetence is on the part of the registry, for not having properly identified the given domain as premium until post-registration.
- CharlesW 3y ago> I'm saying take it easy on Namecheap because it's out of their control… If we assume that Namecheap is incapable of malice, then it means Namecheap's systems and/or processes are broken. (Registry agreements don't allow registries to retroactively reclassify domains as "premium".)
- 0x0000000 3y ago> Registry agreements don't allow registries to retroactively reclassify domains as "premium". On what do you base this? Registration agreements allow quite a lot in favor of registrars and registries.