zlacker

[return to "Itch.io Taken Down by Funko"]
◧
1. bpye+r1[view] [source] 2024-12-09 07:39:12
>>spiral+(OP)
The registrar in question is iwantmyname, so I guess you can add them to your "do not use" list.
◧◩
2. paxys+E1[view] [source] 2024-12-09 07:42:22
>>bpye+r1
I feel like it's better to have a "do use" list for something as important as a domain name registrar.

- Namecheap

- Cloudflare

- Route 53 (if on AWS)

Any others?

◧◩◪
3. koito1+y3[view] [source] 2024-12-09 08:02:05
>>paxys+E1
Personally use Porkbun since Namecheap's API is poorly-documented and they attempted a KYC audit for purchasing a $100 domain.

I am fine with the identity verification, but their ticketing system seems to have sent all of my e-mail to their spam box, because they would never respond. I attempted opening tickets explaining the e-mail situation, but they wouldn't listen. In the end, I gave up and let them deactivate the account.

Moved to Porkbun, purchased the exact same domain (no KYC required!), and have been a happy user of their API for about two years now. They also have much more lax requirements for API usage compared to Namecheap. Porkbun also supports WebAuthn and logging in with a security key. It's overall a much nicer service than Namecheap.

◧◩◪◨
4. yorer+O6[view] [source] 2024-12-09 08:38:03
>>koito1+y3
That kyc thingy is icann requirement, its how domain registration works. Icann require every accredited registrar to verify registrant details so registrar would randomly ask for id, passport etc. That include porkbun, they're bound to their contract with icann as an accredited registrar too. They probably won't ask today but maybe tomorrow, or next week, or next month, or next year, or never.
◧◩◪◨⬒
5. eps+u8[view] [source] 2024-12-09 08:56:29
>>yorer+O6
Other registrars just send an annual email asking to verify your contact details. Done. Icaan satisified. No need to actually harass your clients.
◧◩◪◨⬒⬓
6. yorer+i9[view] [source] 2024-12-09 09:06:23
>>eps+u8
They already got your details from your card details and decide its enough. Something like vpn, using niche browser, details on card not tally with registration details etc etc would throw off their threat mitigation system. Also different business operated differently, their payment gateway behave differently etc etc. Too many random factor to avoid xxx specific registrar because they ask for kyc when the kyc itself is a requirement.
[go to top]