Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Help
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Are there any alternative providers to Cloudflare?

13»

Comments

  • nghialelenghialele Member
    edited November 2025

    @plumberg said:

    @nghialele said:
    Login to Clouflare Dashboard: 0 domains.

    Im safe.

    No fumos in CF?

    fumos are safe from CF

    Thanked by 4plumberg tentor callynne peter1756
  • rick321rick321 Member

    Gigahost.no has recently started free dns service.

  • manishmanish Member

    @Fubukibox said: you can swap servers and cf will give you the same duelstack IP address

    One advantage of Cloudflare is that you can make your v6-only web server accessible to all v4-only users with a click!

    However, I still think that DDoS mitigation from your data center or provider should be preferred to sending your data to Cloudflare or relying on them.

  • tdy0923tdy0923 Member

    @COLBYLICIOUS said:
    Well you can use Bunny (aff/non-aff) if you need an EU alternative to Cloudflare.

    I like that DNS has really generous free tier and also CDN has very good pricing, you can give it a shot.

    Also quick tip, you can create vanity nameservers which is a big plus for me (don't ask why).

    LE: Also you can see an comparison between them.

    @Proxysolid said:
    If you are looking for alternatives, it is depends on whether you need DNS, CDN, or maybe full application protection. If it´s for DNS, maybe Bunny DNS, Hurricane Electric (they are free), and in CDN, BunnyCND (not free but very cheaper).

    They are not perfect, but Cloudflare replacement.

    Thank you all. That's a great suggestion. I'll migrate a portion of it to give it a try.

    Thanked by 1COLBYLICIOUS
  • owrbitowrbit Member, Patron Provider

    @nghialele said:

    @owrbit said:

    @plumberg said:

    @owrbit said:
    I can offer free hosting but for free cdn it cloudflare only

    You're not supposed to offer services without host rep/ patron provider tag

    Sorry for that

    Dude get a tag atp.

    Applied for that already.

  • sullivanroger867sullivanroger867 Member

    I switched to Vercel Hobby for my static sites after a previous Cloudflare Pages outage. Their free tier is very generous for small projects and deploys easily from GitHub. For a purely free DNS alternative, I keep a zone replicated on Hurricane Electric as a secondary.

  • whynotlearnwhynotlearn Member

    @sullivanroger867 said:
    I switched to Vercel Hobby for my static sites after a previous Cloudflare Pages outage. Their free tier is very generous for small projects and deploys easily from GitHub. For a purely free DNS alternative, I keep a zone replicated on Hurricane Electric as a secondary.

    To be honest for static pages, I recommend codeberg pages.

    Codeberg is a github alternative and I think that its nice for static pages

    https://docs.codeberg.org/codeberg-pages/

  • zmeuzmeu Member

    Do you pay any taxes? Or, you're living by coupons. :smiley:

  • rscrsc Member

    @alexhost said:
    We have completely FREE DNS, available.

    https://alexhost.com/dns/

    Could you please tell the DNS names of the name servers you are offering? The DNS servers you seem to be using for your reverse DNS, at least for me, do not look promising at all:

    $ host -t A alexhost.com.
alexhost.com has address 176.123.0.32

    $ host -t NS 0.123.176.in-addr.arpa.
0.123.176.in-addr.arpa name server pdns2.alexhost.com.
0.123.176.in-addr.arpa name server pdns1.alexhost.com.

    $ host pdns1.alexhost.com.
pdns1.alexhost.com has address 176.123.0.50
pdns1.alexhost.com has IPv6 address 2001:678:6d4:cafe::50

    $ host pdns2.alexhost.com.
pdns2.alexhost.com has address 176.123.1.50

    $ whois -h whois.ripe.net 176.123.0.50 | grep origin:
origin:         AS200019

    $ whois -h whois.ripe.net 176.123.1.50 | grep origin:
origin:         AS200019

    Conclusion: Both authoritative DNS servers are unfortunately running in the same autonomous system (AS), which does not look like anycast, thus any larger network issue might make both of them unreachable at the same time.

    DNS result also can be verified at RIPE stat at https://stat.ripe.net/widget/dns-check#resource=0.123.176.in-addr.arpa by selecting test result 2026-02-28T20:01:04Z | warning.

    That it does not look like anycast can be verified at RIPE Atlas at https://atlas.ripe.net/measurements/157797882/overview (visually) and https://atlas.ripe.net/measurements/157797882/results (sort by "Min RTT").

    For pdns2.alexhost.com, I am additionally not sure if there is some (broken) GeoDNS attempt, because pdns2.alexhost.com resolves either to 176.123.1.50 or to 185.53.179.136, however 185.53.179.136 does not answer DNS queries (or if with NXDOMAIN).

    $ host -t PTR 176.123.0.32 185.53.179.136
;; connection timed out; no servers could be reached

    This can be verified at RIPE Atlas at https://atlas.ripe.net/measurements/157797954/results (sort by "Destination IP") and https://atlas.ripe.net/measurements/157798041/results (sort by "Response Time").

    Finally https://atlas.ripe.net/measurements/157798130/results (sort by "Destination IP") shows another (broken) GeoDNS attempt (or so) for pdns1.alexhost.com as well, leading to same 185.53.179.136 as mentioned before.

  • alexhostalexhost Member, Patron Provider

    @rsc said:

    @alexhost said:
    We have completely FREE DNS, available.

    https://alexhost.com/dns/

    Could you please tell the DNS names of the name servers you are offering? The DNS servers you seem to be using for your reverse DNS, at least for me, do not look promising at all:

    $ host -t A alexhost.com.
alexhost.com has address 176.123.0.32

    $ host -t NS 0.123.176.in-addr.arpa.
0.123.176.in-addr.arpa name server pdns2.alexhost.com.
0.123.176.in-addr.arpa name server pdns1.alexhost.com.

    $ host pdns1.alexhost.com.
pdns1.alexhost.com has address 176.123.0.50
pdns1.alexhost.com has IPv6 address 2001:678:6d4:cafe::50

    $ host pdns2.alexhost.com.
pdns2.alexhost.com has address 176.123.1.50

    $ whois -h whois.ripe.net 176.123.0.50 | grep origin:
origin:         AS200019

    $ whois -h whois.ripe.net 176.123.1.50 | grep origin:
origin:         AS200019

    Conclusion: Both authoritative DNS servers are unfortunately running in the same autonomous system (AS), which does not look like anycast, thus any larger network issue might make both of them unreachable at the same time.

    DNS result also can be verified at RIPE stat at https://stat.ripe.net/widget/dns-check#resource=0.123.176.in-addr.arpa by selecting test result 2026-02-28T20:01:04Z | warning.

    That it does not look like anycast can be verified at RIPE Atlas at https://atlas.ripe.net/measurements/157797882/overview (visually) and https://atlas.ripe.net/measurements/157797882/results (sort by "Min RTT").

    For pdns2.alexhost.com, I am additionally not sure if there is some (broken) GeoDNS attempt, because pdns2.alexhost.com resolves either to 176.123.1.50 or to 185.53.179.136, however 185.53.179.136 does not answer DNS queries (or if with NXDOMAIN).

    $ host -t PTR 176.123.0.32 185.53.179.136
;; connection timed out; no servers could be reached

    This can be verified at RIPE Atlas at https://atlas.ripe.net/measurements/157797954/results (sort by "Destination IP") and https://atlas.ripe.net/measurements/157798041/results (sort by "Response Time").

    Finally https://atlas.ripe.net/measurements/157798130/results (sort by "Destination IP") shows another (broken) GeoDNS attempt (or so) for pdns1.alexhost.com as well, leading to same 185.53.179.136 as mentioned before.

    Hi

    Please check here
    https://bill.alexhost.com/knowledgebase/article/33/how-to-set-up-and-configure-dns-service/

    I think you picked the wrong DNS, this are the correct:
    alpha.alexhost.com
    beta.alexhost.com

    Best Regards,
    Alexhost

  • rscrsc Member
    edited February 28

    @alexhost said:
    I think you picked the wrong DNS, this are the correct:
    alpha.alexhost.com
    beta.alexhost.com

    Well, unfortunately these look similar less promising to me (even both of these DNS servers even have IPv6):

    $ host alpha.alexhost.com
alpha.alexhost.com has address 176.123.0.35
alpha.alexhost.com has IPv6 address 2001:678:6d4:5000::35

    $ host beta.alexhost.com
beta.alexhost.com has address 176.123.0.36
beta.alexhost.com has IPv6 address 2001:678:6d4:5000::36

    $ whois -h whois.ripe.net 176.123.0.35 | grep origin:
origin:         AS200019

    $ whois -h whois.ripe.net 2001:678:6d4:5000::35 | grep origin:
origin:         AS200019

    $ whois -h whois.ripe.net 176.123.0.36 | grep origin:
origin:         AS200019

    $ whois -h whois.ripe.net 2001:678:6d4:5000::36 | grep origin:
origin:         AS200019

    All in the same autonomous system (AS), so no redundancy on that level, but also no GeoDNS, and no anycast.

    Neutral measurements via RIPE Atlas are confirming this:

    From some providers, alpha.alexhost.com and beta.alexhost.com even resolve both only to 185.53.179.136, which unfortunately does not answer (or if, only with NXDOMAIN). Details for these affected networks can be found at the before mentioned IPv4 measurements at the "Results" tab, order by "Destination IP" (and in my comment before).

    Edit: It seems like the 185.53.179.136 results from some geo-blocking on DNS level (which is bad for DNS server reachability). But finally, as long as you are using Cloudflare DNS servers to connect your domain alexhost.com, Cloudflare DNS outages might also affect your DNS servers beyond your alexhost.com domain (because DNS is hierarchical).

    $ whois alexhost.com | grep ^Name
Name Server: cris.ns.cloudflare.com
Name Server: mckenzie.ns.cloudflare.com
Sign In or Register to comment.