mirror of
https://github.com/jbowdre/capsule.git
synced 2024-11-09 16:32:18 +00:00
31 lines
No EOL
3.6 KiB
Text
31 lines
No EOL
3.6 KiB
Text
I have a small-but-growing collection of domains. Some are used for public projects like this capsule, some find purpose for internal personal projects, some are used primarily for email addresses, and several more just sit idle waiting for a use.
|
|
|
|
Assembling this collection has taken me through many different domain registrars, with varying levels of user-unfriendliness. If you, as a registrar, do any of (let alone *all* of) the following, know that your business model is hot+wet garbage:
|
|
|
|
* Parking 1000 CNAMEs on newly-registered domains, which then have to be manually removed because you don't offer a user-facing API.*
|
|
* Pushing a paid "ID Protection" add-on for domains whose registries already employ WHOIS protection/redaction by default.
|
|
* Requiring users to submit a support ticket to request an EPP/auth code so they can transfer to a registrar that doesn't disrespect its customers.
|
|
* Automatically re-locking a domain when an auth code is requested so that the first transfer attempt will fail.
|
|
* Emailing customers when a transfer is initiated advising to click a link (which contains the string `transfer-approval` in the URL) to _cancel_ the transfer, but not providing a way to _approve_ it.
|
|
* Declining a customer's request to expedite the release of a domain for which a transfer has been initiated, and instead requiring the customer to wait for the 5-day timeout to elapse.
|
|
|
|
Every step of the transfer process at these sorts of registrars is deliberately designed to make it as annoying as possible so that customers will give up and just stay with the shitty registrar. It's gross.
|
|
|
|
Fortunately, we don't have to do business with shady registrars like that, though it can often be difficult to determine how good/evil a registrar will be until you've already signed up with them - and by that point, shitty registrars will make you fight your way out. Something that can help is to look through the registrar's *publicly available* support docs to see what their policy is for transferring domains out of their registrar. Good registrars will make it easy:
|
|
|
|
=> https://kb.porkbun.com/article/27-how-to-transfer-domain-from-porkbun-to-another-registrar Porkbun: How to Transfer a Domain From Porkbun to Another Registrar
|
|
=> https://developers.cloudflare.com/registrar/account-options/transfer-out-from-cloudflare/ Cloudflare: Transfer domain from Cloudflare to another registrar
|
|
=> https://www.namecheap.com/support/knowledgebase/article.aspx/258/84/what-should-i-do-to-transfer-a-domain-from-namecheap/ Namecheap: What should I do to transfer a domain from Namecheap?
|
|
|
|
On the other hand, bad registrars might hide the instructions behind a login and/or insist that you contact support to obtain the auth code:
|
|
=> https://gen.xyz/account/knowledgebase/5/Domain-Management gen.xyz: Can I transfer my domain to another registrar?
|
|
> Submit a ticket to support, requesting your EPP/authorization code
|
|
|
|
I've been using Porkbun for more and more of my domains over the past year or so and have been positively delighted by the experience at every step of the way. I've also had a great experience registering domains (and transferring them to/from) Cloudflare. I'm sure there are many other reputable registrars to consider, but I think Porkbun should be at the top of anyone's list. Registering, managing, and transferring domains shouldn't be painful.
|
|
|
|
But if you really want a registrar that ticks all the shitty boxes above, gen.xyz is an option.
|
|
|
|
===
|
|
|
|
* Or use a handy utility to nuke 1000 bogus records after shifting DNS responsibilities to Cloudflare:
|
|
=> https://cloudflare-utils.cyberjake.xyz/dns/purge/ DNS Purge - Cloudflare Utilities |