Create a new article
Write your page title here:
We currently have 539 articles on Soyjak Wikia. Type your article name above or click on one of the titles below and start writing!

Soyjak Wikia

Welcome to the Soyjak Wikia

Make sure you follow the Rules before editing, or you will be permanently banned!!!!!!!!!

(if you prefer monobook or vector more, you can change that in your settings)

Cloudflare feraljak.png

Cloudflare (also known as Cuckflare and Crimeflare) is an American botnet disguised as an affordable reverse-proxy and DDoS-mitigation service. Its business model consists of a campaign of intimidation of DDoS attacks against website administrators, against which, suspiciously, only Cloudflare's protection service is effective. The army of servers is kept well-fed by a steady stream of harassment-sales. Thus the botnet grows, kind of like homosexuals[1].

On soyjak.party[edit | edit source]

Soot enabled Cloudflare in an attempt to stop Colorjak, CP and other types of spam. At first it was accepted, even with some users starting to defend the decision, calling all the Cloudflare detractors as spammers but it quickly became an annoyance to most users as cloudflare requires you to refresh the page every five minutes. Higher protection modes also block archive sites from taking snapshots.

The Man in the middle[edit | edit source]

Cloudflare-protected servers are instanced across a vast content-delivery-network, with visitors never interacting with the real server. The unencrypted contents of user's interaction are entirely handled by Cloudflare. This is indistinguishable from a man-in-the-middle attack, no more no less. From hosting your bank's website to soyjak.party, Crimeflare dominates the CDN market with an 80% share, essentially performing a man-in-the-middle-attack on all of the internet. Some have pointed out the colossal datamining potential of such a position, but the argument loses ground when verified fact-checkers revealed the proponents are conspiracy theorists who should take their meds.

Note for a site to use cloudflare, the owner has to point their DNS records to cloudflare's servers, at which point they effectively handed cloudflare full control of their website (as long as the DNS records point to cloudflare's servers). They can prove control of a domain to certificate authorities who will issue certificates for your domain to cloudflare.

Now cloudflare has control to eavesdrop and log any user interactions with your website or silently tamper content if they please.

However, this is not a Man-in-the-Middle attack, because the website owner gave cloudflare permission to do all of this. So it's not an attack, it's a secure connection to cloudflare (who the website owner gave permission to serve content at their domain name).


In the end, that's all you have. You have to trust that the organization running the website at the other end is trustworthy with whatever data you give them by browsing there. When visiting websites on the cloudflare CDN part of the trust is in cloudflare.[2]

See also[edit | edit source]

Citations[edit | edit source]