CI had the privacy and redaction feature enabled at the timeIt's not a feature that you can enable on checkout, Cloudflare just has redaction on by default.
us
X.ai.io
XCwhoisai.ai
.aiQuick update from the team is that this is expected behavior as the .ai TLD does not censor this info, and they'll take steps to make that clear when registering .ai domains similar to what we currently do for .us.So I guess difference between redaction and full whois privacy. Hoping for some proper communication from the Registrar team to affected users. In the short term, I would consider changing the info on there like your phone/email etc to non-personal or virtual numbers. Your ticket is still escalated though, this is separate from that
XXwebsim.aicopy.aiguides.ainotion.aicharacter.aijasper.aiAre registrars like PorkBun, NameCheap, NameSilo, Proxy LLC, etc. in violation considering this domain is privatized by them per the official .ai WHOIS (http://whois.nic.ai/) and using Cloudflare name servers?It's the difference between Whois Redaction and full whois privacy. Whois privacy is a service which they replace your details with theirs. Redaction (which is what Cloudflare uses) simply doesn't send info. For
comI imagine the no refund policy is still in effect for registering this domain for two years despite there being an option to enable WHOIS privacy during registration and seemingly being a feature other registrars can provide?I'd push that with support once they respond to you, they should do something, obviously not right for them to claim that it would be redacted repeatedly during the checkout process and then it's just not...
Is there a definitive source of truth for which TLDs are compatible with WHOIS privacy, or a list of sources per TLD? The policies page seems to be outdated: https://www.cloudflare.com/tld-policiesNot as far as I am aware of
XIt's the difference between Whois Redaction and full whois privacyIs the MVP speaking here from 2018 mistaken in their claim that WHOIS privacy is explicitly offered by Cloudflare?: https://community.cloudflare.com/t/cloudflare-registrar-and-whois-privacy/36225
Redaction (which is what Cloudflare uses) simply doesn't send info.The TLD WHOIS wouldn't have been able to display my info at all in this case; is redaction done as an after-the-fact request that a WHOIS provider can deny or not support? This may affect whether or not I complete the transfer of other domains to this registrar.
not right for them to claim that it would be redacted repeatedly during the checkout processTrue, I'll leave these tickets open after all. Thank you again for helping me understand! I'd rather have my domains with Cloudflare but don't yet have the business revenue to support registered agent nor PO box for physical addressing.
Not as far as I am aware ofGiven the recent announcement by ICANN, is there any roadmap for sunsetting WHOIS and implementing RDAP, or for users to enable one or both?: https://www.icann.org/en/announcements/details/icann-update-launching-rdap-sunsetting-whois-27-01-2025-en I do see this little tool: https://rdap.cloudflareregistrar.com/
CIs the MVP speaking here from 2018 mistaken in their claim that WHOIS privacy is explicitly offered by Cloudflare?: https://community.cloudflare.com/t/cloudflare-registrar-and-whois-privacy/36225It just gets confusing with terminology. As far as I know
whois privacyThe TLD WHOIS wouldn't have been able to display my info at all in this case; is redaction done as an after-the-fact request that a WHOIS provider can deny or not support?True, I believed that CF was redacting and sending info to be displayed in whois (as otherwise this gets tricky with gdpr), and just implemented that somewhere on their backend and then other private info another way to the registry, but it seems more complicated then that.
CGiven the recent announcement by ICANN, is there any roadmap for sunsetting WHOIS and implementing RDAP, or for users to enable one or both?: https://www.icann.org/en/announcements/details/icann-update-launching-rdap-sunsetting-whois-27-01-2025-en I do see this little tool: https://rdap.cloudflareregistrar.com/This is more of a thing with the Registries and not really Registrars, you query whois.nic.ai, not Cloudflare's typically, although some tools do both. Cloudflare already supports rdap though as you see. They show the same info regardless, just different format
C.aiA final point on gTLDs and ccTLDs, it seems there's some flex there as well as to what (maybe only monopoly-sized) orgs can choose to do,I mean fundementally to a user, to dns, etc, gTLDs and ccTLDs aren't much different. That's in the search/seo context, which makes sense for them.
.com