News for hackers. Stuff that matters.

samatcloudflare

Re:Cloudflare One on Monday October 12, 2020 @09:55AM (#24754355)
Happy to help. We can use our network, specifically our Access product, to check for identity. When a user requests an application, our network can stop that request and ask the user to show ID.

The difference is that we don't issue that identity. We aren't an identity provider, like Okta or Azure AD. Instead, teams integrate our Access product with their identity provider which tells us which sources of identity to trust (in the same way a bouncer or border guard doesn't create your identity card for you, but they know what a valid one looks like).

Re:Argo Tunnel AAAA Record on Thursday August 27, 2020 @12:53PM (#24295635)
Hi - Argo Tunnel creates AAAA records, but will still return IPv4 addresses. Tunnels with those records will still work on IPv4-only networks.

Can you test by running `dig +short foo.app.com`

and confirm that you get IPv4 records? It is potentially another issue with the site or Cloudflare's Happy Eyeballs feature at play; happy to help debug that as well.

Re:Argo and the Cloudflare Global Private Backbone on Monday May 13, 2019 @07:14PM (#19905009)
Yes you can. You can run an Argo Tunnel without a Cloudflare account using the feature below. It's like ngrok, but with Argo Smart Routing.

https://developers.cloudflare.com/argo-tunnel/trycloudflare/

Re:Cloudflare Registrar on Thursday March 21, 2019 @01:26PM (#19454930)
Some registrars will block transfers if certain types of privacy protections are enabled (or they'll require you expose your data to the public in order to give you your auth code).

Namecheap can block transfers with WHOIS Guard enabled in some cases; as soon as it is transferred to Cloudflare, though, the info will be redacted.

Re:Cloudflare Registrar on Thursday March 21, 2019 @12:48PM (#19454442)
We do - all whois information is redacted by default for every domain on Cloudflare Registrar.
Re:Cloudflare Registrar on Thursday March 21, 2019 @12:13PM (#19454011)
I'd still understand being frustrated with $8. We're asking you to trust us with your domain's registration and that starts with handling the charges for it in the right way. We're going to fix that.
Re:Cloudflare Registrar on Thursday March 21, 2019 @11:48AM (#19453733)
If you can find it for $15.18 without having to buy other services, that's a deal and you should take it. Most discounts like that are offered as loss leaders in the hopes that you'll buy other add-ons.
Re:Cloudflare Registrar on Thursday March 21, 2019 @11:41AM (#19453632)
I apologize for the billing issue. I understand how frustrating that would be and it's well below our standards. We're working as a team to make that right and earn back your trust now.
Re:Cloudflare Registrar on Thursday March 21, 2019 @11:36AM (#19453549)
Sorry about the billing issue; that's really frustrating. We've been working on a migration of our billing systems, but that has led to some cases of double charges which are unacceptable. Working to make that right now and glad the refund was successful.

I'm looking at your ticket now; will make sure this gets solved today.

Re:Cloudflare Registrar on Thursday March 21, 2019 @11:34AM (#19453509)
Thanks for the feedback. Working on new registrations now; focus at launch was to help users of Cloudflare's DNS services find a better alternative to domain registration.
Re:Cloudflare Registrar on Thursday March 21, 2019 @11:33AM (#19453491)
.io is heavily subsidized by most registrars for a couple reasons: the .io registry offers substantial volume discounts and .io domains are associated with a higher spend on add-on services. In most cases, they discount .io domains because they hope users spend more on other upsell products.