You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

11 KiB

List Instructions

_click me_

Website is using Cloudflare

List name Description
/domain/cloudflare_?.txt Split files (base domain)
ex_cloudflare_users.txt Domains which used Cloudflare in the past, not anymore
cloudflare_supporter.txt who is using Cloudflare or endorsing Cloudflare. (URL only)
List name Description
cloudflare_CIDR_v4.txt IPv4 CIDR owned by Cloudflare
cloudflare_CIDR_v6.txt IPv6 CIDR owned by Cloudflare
cloudflare_range_v4.txt IPv4 range owned by Cloudflare
cloudflare_owned_ASN.txt AS network owned by Cloudflare
cloudflare_owned_NS.txt Name Server owned by Cloudflare
cloudflare_owned_domains.txt Domains owned by Cloudflare
cloudflare_owned_onions.txt Tor .onions owned by Cloudflare
cloudflare_members.txt Cloudflare employer & employee

How to detect Cloudflare?

There are many ways to detect it:		21599	IN	NS		21599	IN	NS	299	IN	A

ASN AS13335 Cloudflare, Inc.
Organization Cloudflare, Inc.
IMPORTANT: Please add only "Base Domain"

    if "" is using Cloudflare
        add ""

    if "" is using Cloudflare
        add ""

    if "" is using Cloudflare
        add ""

... to /split/cloudflare_e.txt

But the website X no longer using Cloudflare!

Are you sure? Remove it from /split/ list and add to "ex_cloudflare_users.txt".

_click me_

Website is NOT using Cloudflare

List name Description
/domain/(cdnName).txt Split files (FQDN)
/cidr_data/?.txt CIDR, ASN

  • Above is how Siteground-hosted(INAP;Singlehop) sites often appear to Tor visitors when timeouts/tarpitting doesn't occur.

About "CDN FQDN list"
   ---> is using CDN.

   ---> subdomain of is using CDN.
   * unique hostname will be masked as "?".
   ---> base domain is using CDN.

Some websites use other companies with the CloudFlare business model.

This is a collection of websites that ban Tor exits, other than through Cloudflare(e.g. showing access denied pages, systematic timing out connections, ...).

_click me_

Website is rejecting Tor visitor

List name Description
/fqdn/anti_tor_fqdn.txt Split files (FQDN)

  • Some news websites are lying to Tor users. You can read their website if you are not using Tor nor VPN. If you visit their website over Tor, they just say "Sorry, article not found". How can you trust their news if they are not treating everyone equally?

About "Anti-Tor FQDN list"
   ---> denied/bullied Tor visitor.

   ---> subdomain of is denied Tor user.
   * unique hostname will be masked as "?".
   ---> base domain denied/harassed/challenged human who're using Tor.

If your website is on this list, you better talk with your network administrator.

But the website X no longer blocking Tor users!

Are you sure? There are two ways to remove yourself. First option is just remove it from the list and create a pull request. Second option is wait 1 year. We will revisit your website as a Tor user. If you're not blocking us, you will be removed.

If your website is using Cloudflare, there's a higher chance that we receive rejection webpage. Do not use cloudflare.

_click me_

How to add your data

A or B will be enough. Thank you for your contribution.

  • Type A: Push to OpenPrivacy
  1. Log in to OpenPrivacy.
  2. Click "Fork" button. (top-left corner)
  3. Edit text file.
  4. Click Double-arrow button to create a new pull request.
  • Type B: Just scan the FQDN
  1. [Cloudflare/CDN] Scan FQDN on "Is MITM?" webpage. (or just use "MITM test" API, "Detect CDN" API)
    [Anti-TOR] Just use "Is it blocking Tor?" API.
  2. It will be pushed to OpenPrivacy automatically within a week.

_click me_

How to setup git

This procedure will give you a stop_cloudflare fork with a privacy-respecting configuration to do pushes with SSH over Tor using"CDB"). This procedure is designed for linux. The first step covers Windows too, but these instructions probably need more adaptations for Windows and other platforms.

  • Linux: aptitude install git tor ssh
  • Windows: Download & run git-bash.exe
  1. install Git, SSH(Not Windows), and Tor (if you haven't already)
  2. create a account (username "snowden" will be used for this example)
  3. create an SSH key pair $ ssh-keygen -t rsa -N '' -C 'snowden at codeberg' -f "$HOME"/.ssh/id_rsa_codeberg-snowden
  4. edit $HOME/.ssh/config:
         ForwardX11   no
         ProxyCommand connect -4 -S $(tor-resolve %h %p
    host codeberg-snowden
         IdentityFile /home/user/.ssh/id_rsa_codeberg-snowden
  1. copy "$HOME"/.ssh/ to clipboard
  2. > settings > SSH/GPG Keys > add key (paste from clipboard)
  3. $ firefox
  4. fork it (top right corner)
  5. go to the directory you want the project to be rooted in (hereafter we'll call it $project_root).
  6. anonymously download your fork: $ git clone git@codeberg-snowden:crimeflare/cloudflare-tor.git
  7. edit $project_root/cloudflare-tor/.git/config to include the account name and email address that will be on every commit, as well as the URL:
        email =
        name = snowden
[remote "origin"]
        url = git@codeberg-snowden:snowden/cloudflare-tor.git
     	fetch = +refs/heads/*:refs/remotes/origin/*
[remote "upstream"]
        url = git@codeberg-snowden:crimeflare/cloudflare-tor.git
     	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master
  1. make your first change
  2. (from $project_root) $ git add . -u -n
  3. check that the files listed are what you changed and intend to push upstream
  4. if yes: $ git add . -u
  5. $ git commit -m 'description of first change'
  6. $ git push origin master
  7. $ firefox
  8. make a new pull request


Whenever git operates on the cloudflare-tor project, all connections to codeberg are automatically over Tor with this configuration (because the url in .git/config references the virtual host codeberg-snowden in ~/.ssh/config).

_click me_

About Cloudflare base domain list

Our mission is clear - stay away from Cloudflare.

If the is cloudflared, we add to the database. ( is the sub-domain of Only the owner of can create sub-domain)

Even if is not behind cloudflare we will raise a warning, because the base domain is cloudflare user.

The owner of can enable Cloudflare to at any time without user's notice. It can be done from webpage or hitting Cloudflare API. The owner is supporting Cloudflare and this is severe security risk.

Until the owner completely stop using Cloudflare service for, we do not remove from the database.

There is no exception.


$ getweb --headonly

cf-cache-status: HIT
expect-ct: max-age=604800, report-uri=""
alt-svc: h2="cflare******.onion:443"; ma=86400; persist=1
server: cloudflare

If the owner moved away from cloudflare completely, you are welcome to add to the "ex_cloudflare_users.txt" - after checking with online tool below.

  1. Open "Is MITM?" webpage.

  2. Input and click Skanu.

  3. Click testo for detailed scan.

  4. If you got ---Finish---, the domain might stopped using Cloudflare. We'll investigate and remove it - or not. (wait some days and scan again to see whether the domain is removed)

Only a few Cloudflare user leave Cloudflare. False positive is uncommon.

"Cloudflare is not an option."