9.5 KiB

Raw Blame History

List Instructions

Table of contents

Website is using Cloudflare

Cloudflare users | List Directory

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)

Cloudflare Corporation | List Directory

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

1) How to detect Cloudflare

There are many ways to detect it:

These add-ons will help your Cloudflare collection.
Visit a website via Tor or VPN, and you will be greeted by "Attention Required! Cloudflare" webpage.
Use "Is MITM?" webpage.
Dig "NS record" of the domain.

emsisoft.com.		21599	IN	NS	bella.ns.cloudflare.com.
emsisoft.com.		21599	IN	NS	dom.ns.cloudflare.com.

Dig "A record" of the FQDN, then check the IP's owner.

dev.qubes-os.org.	299	IN	A	104.18.228.122

ASN AS13335 Cloudflare, Inc.
Organization Cloudflare, Inc.
Route 104.18.224.0/20

2) How to add your data (A or B)

Type A: Push to Codeberg.org

Log in to Codeberg.org.
Click "Fork" button. (top-left corner)
Edit text file.
Click Double-arrow button to create a new pull request.

Type B: Just scan the FQDN

Scan FQDN on "Is MITM?" webpage.
It will be pushed to Codeberg automatically within a week.

IMPORTANT: Please add only "Base Domain"

    if "community.example.com" is using Cloudflare
        add "example.com"

    if "www.example.co.uk" is using Cloudflare
        add "example.co.uk"

    if "example.net" is using Cloudflare
        add "example.net"

... to /split/cloudflare_e.txt

3) If the website no longer using Cloudflare, remove it from /split/ list and add to "ex_cloudflare_users.txt".

Website is NOT using Cloudflare

Anti-Tor users (formerly "TorBlocker Hall of Shame Part I") | List Directory

List name	Description
/cidr_data/?.txt	other CDN IPv4 CIDR files
/domain/(cdnName).txt	Split files (FQDN)
list_othercdn_domain.txt	[DEPRECATED] domains behind these CDN (Not Cloudflare)
list_http_error.txt	Websites that instantly and unconditionally deny service to Tor visitors by returning an HTTP error. HTTP 403 is the most common but this list catalogs all HTTP responses that entail DoS (i.e. not HTTP 200). File format is: <FQDN> <http error code>
list_customerror.txt	Custom error message renders for Tor visitors generally without HTTP error.
list_other.txt	Any other form of tor-hostility or mistreatment. This includes sites somewhat functional for Tor users to some extent but sneaky and unexpected adverse retalitory actions are taken against Tor visitors.
list_formerly_tor-hostile.txt	was previously on one of the above tor-hostile lists

Add-on "Kiu retejo malakceptis min?" will help your domain collection.

Above is how Siteground-hosted(INAP;Singlehop) sites often appear to Tor visitors when timeouts/tarpitting doesn't occur. You can find such examples in /cidr_data/.

{domain} {CDN code}

{CDN code}:
'amazon.txt':'Z1'
'akamai.txt':'Z2'
(cloudflare is Z3)
'imperva.txt':'Z4'
'google.txt':'Z5'
'microsoft.txt':'Z6'
'inap.txt':'Z7'
'sucuri.txt':'Z8'

IMPORTANT: Please add only "FQDN" or "FQDN[space](comment here)"

    if "community.example.com" is blocking Tor
        add "community.example.com"

    if "example.co.uk" is blocking Tor
        add "example.co.uk Error message: Anonymous not allowed"

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, ...).

How to setup git

This procedure will give you a cloudflare-tor fork with a privacy-respecting configuration to do pushes with SSH over Tor using codeberg.org ("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 https://github.com/git-for-windows/git/releases/PortableGit-2.21.0-64-bit.7z & run git-bash.exe

install Git, SSH(Not Windows), and Tor (if you haven't already)
create a codeberg.org account (username "snowden" will be used for this example)
create an SSH key pair $ ssh-keygen -t rsa -N '' -C 'snowden at codeberg' -f "$HOME"/.ssh/id_rsa_codeberg-snowden
edit $HOME/.ssh/config:

    host codeberg-*
         hostname     codeberg.org
         ForwardX11   no
         ProxyCommand connect -4 -S 127.0.0.1:9050 $(tor-resolve %h 127.0.0.1:9050) %p
    host codeberg-snowden
         IdentityFile /home/user/.ssh/id_rsa_codeberg-snowden

copy "$HOME"/.ssh/id_rsa_codeberg-snowden.pub to clipboard
codeberg.org > settings > SSH/GPG Keys > add key (paste from clipboard)
$ firefox https://codeberg.org/crimeflare/cloudflare-tor
fork it (top right corner)
go to the directory you want the project to be rooted in (hereafter we'll call it $project_root).
anonymously download your fork: $ git clone git@codeberg-snowden:crimeflare/cloudflare-tor.git
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:

[user]
        email = BM-yadayadayada6fgnLfybVnCcWf25AGZcgg@bitmessage.ch
        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

make your first change
(from $project_root) $ git add . -u -n
check that the files listed are what you changed and intend to push upstream
if yes: $ git add . -u
$ git commit -m 'description of first change'
$ git push origin master
$ firefox https://codeberg.org/crimeflare/cloudflare-tor
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).

About Cloudflare `base domain` list

Our mission is clear - stay away from Cloudflare.

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

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

The owner of example.com can enable Cloudflare to whatever.example.com at any time without user's notice. It can be done from dash.cloudflare.com 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 example.com, we do not remove example.com from the database.

There is no exception.

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

Open "Is MITM?" webpage.
Input gitlab.com and click Skanu.
Click testo for detailed scan.
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.

9.5 KiB Raw Blame History