blob: 653861b4388fc605b822ab86464d933e1df1ba31 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
# Instructions
--------------
## Website is using Cloudflare
**Cloudflare users** | [**List Directory**](cloudflare_users/)
| List name | Description |
| -------- | -------- |
| /domain/cloudflare_x.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**](cloudflare_inc/)
| 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](what-to-do.md) 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?](https://searxes.eu.org/collab/sxes/tool_ismitm.php)" webpage.
- Dig "[NS record](https://www.digwebinterface.com/?hostnames=emsisoft.com&type=NS&ns=resolver&useresolver=8.8.4.4&nameservers=)" of the domain.
```
emsisoft.com. 21599 IN NS bella.ns.cloudflare.com.
emsisoft.com. 21599 IN NS dom.ns.cloudflare.com.
```
- Dig "[A record](https://www.digwebinterface.com/?hostnames=dev.qubes-os.org&type=A&ns=resolver&useresolver=8.8.4.4&nameservers=)" of the FQDN, then [check the IP's owner](https://ipinfo.io/104.18.228.122).
```
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
1. Log in to *Codeberg.org*.
2. Click "*Fork*" button. (top-left corner)
3. Edit text file.
4. Click *Double-arrow* button to create a *new pull request*.
```
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
```
Type B: Use "[Is MITM?](https://searxes.eu.org/collab/sxes/tool_ismitm.php)" webpage.
3) If the website *no longer using Cloudflare*, *remove* it from /split/ list and *add* to "[ex_cloudflare_users.txt](cloudflare_users/ex_cloudflare_users.txt)".
--------------
## Website is NOT using Cloudflare (& blocking you)
**Anti-Tor users** (formerly "*TorBlocker Hall of Shame Part I*") | [**List Directory**](not_cloudflare/)
| List name | Description |
| -------- | -------- |
| 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_siteground.txt | siteground.com is a Tor-hostile hosting service that indiscriminately DoSes all Tor users with the collective judgement: "our system thinks you might be a robot!" Sometimes the site functions, and sometimes it times out, but the robot accusation (illustrated below) is very common. |
| list_formerly_tor-hostile.txt | was previously on one of the above tor-hostile lists |
| (obsolete) list_error403.txt | Superceded by list_http_error.txt. Returns HTTP Error 403 (Forbidden) |
| (obsolete) list_error462.txt | Superceded by list_http_error.txt. Returns HTTP Error 462 |
 <= This is how Siteground-hosted sites often appear to Tor visitors when timeouts/tarpitting doesn't occur. If you see this please update `list_siteground.txt`.
```
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, ...).
[Add-on "whyrejectme"](README.md#what-can-you-do) will help your `list_http_error.txt` collection.
---
Information:
- [How to setup git](instructions_git.md)
|
