stop_cloudflare/instructions.md

117 lines
4.3 KiB
Markdown
Raw Normal View History

2019-02-25 03:09:59 +01:00
# Instructions
--------------
2018-10-11 15:00:30 +02:00
2019-02-25 03:09:59 +01:00
## Website is using Cloudflare
2018-10-11 15:00:30 +02:00
2019-05-07 11:49:47 +02:00
**Cloudflare users** | [**List Directory**](cloudflare_users/)
2019-05-06 14:13:39 +02:00
2018-10-11 15:00:30 +02:00
| List name | Description |
2018-10-11 15:04:44 +02:00
| -------- | -------- |
2019-05-07 11:52:29 +02:00
| /domain/cloudflare_x.txt | Split files (base domain) |
2019-02-25 03:20:36 +01:00
| ex_cloudflare_users.txt | Domains which used Cloudflare in the past, not anymore |
2019-05-06 14:13:39 +02:00
| cloudflare_addedbyfqdn.txt | Historical data (e.g. example.com was added because xyz.example.com is cloudflared |
2019-05-07 12:15:28 +02:00
| cloudflare_supporter.txt | who is using Cloudflare or endorsing Cloudflare |
2019-05-06 14:13:39 +02:00
2019-05-07 11:49:47 +02:00
**Cloudflare Corporation** | [**List Directory**](cloudflare_inc/)
2019-05-06 14:13:39 +02:00
| List name | Description |
| -------- | -------- |
2019-02-25 03:20:36 +01:00
| 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 |
2019-03-02 04:41:09 +01:00
| cloudflare_owned_NS.txt | Name Server owned by Cloudflare |
2018-10-11 15:17:40 +02:00
| cloudflare_owned_domains.txt | Domains owned by Cloudflare |
| cloudflare_owned_onions.txt | Tor .onions owned by Cloudflare |
2019-05-07 11:53:24 +02:00
| cloudflare_members.txt | Cloudflare employer & employee |
2018-10-11 15:00:30 +02:00
2018-10-11 15:12:11 +02:00
1) How to detect Cloudflare
2018-10-11 15:00:30 +02:00
2019-03-03 00:01:42 +01:00
There are many ways to detect it:
2018-10-11 15:12:11 +02:00
- [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.
2019-04-02 04:11:43 +02:00
- Use "[Is MITM?](https://searxes.danwin1210.me/collab/sxes/tool_ismitm.php)" webpage.
2019-03-03 00:01:42 +01:00
- Dig "[NS record](https://www.digwebinterface.com/?hostnames=emsisoft.com&type=NS&ns=resolver&useresolver=8.8.4.4&nameservers=)" of the domain.
2019-03-03 00:02:09 +01:00
2019-03-03 00:01:42 +01:00
```
emsisoft.com. 21599 IN NS bella.ns.cloudflare.com.
emsisoft.com. 21599 IN NS dom.ns.cloudflare.com.
```
2019-03-03 00:02:09 +01:00
2019-03-03 00:01:42 +01:00
- 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).
2019-03-03 00:02:09 +01:00
2019-03-03 00:01:42 +01:00
```
dev.qubes-os.org. 299 IN A 104.18.228.122
ASN AS13335 Cloudflare, Inc.
Organization Cloudflare, Inc.
Route 104.18.224.0/20
```
2018-10-11 15:00:30 +02:00
2019-04-02 04:11:43 +02:00
2019-04-02 01:11:34 +02:00
2) How to add your data (A or B)
Type A: Push to NotABug.org
2018-10-11 15:00:30 +02:00
2019-02-25 03:09:59 +01:00
1. Log in to *notabug.org*.
2. Click "*Fork*" button. (top-left corner)
2018-10-11 15:12:11 +02:00
3. Edit text file.
2019-02-25 03:09:59 +01:00
4. Click *Double-arrow* button to create a *new pull request*.
2018-10-11 15:00:30 +02:00
2018-10-11 15:12:11 +02:00
```
2019-02-25 03:14:30 +01:00
IMPORTANT: Please add only "Base Domain"
2019-02-25 03:09:59 +01:00
if "community.example.com" is using Cloudflare
2019-02-25 03:14:30 +01:00
add "example.com"
if "www.example.co.uk" is using Cloudflare
add "example.co.uk"
2019-02-25 03:09:59 +01:00
if "example.net" is using Cloudflare
2019-02-25 03:14:30 +01:00
add "example.net"
... to /split/cloudflare_e.txt
2019-02-25 03:09:59 +01:00
```
2019-05-08 02:16:56 +02:00
Type B: Use "[Is MITM?](https://searxes.danwin1210.me/collab/sxes/tool_ismitm.php)" webpage.
2019-04-02 01:11:34 +02:00
2019-05-08 02:16:56 +02:00
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)".
2018-04-18 18:27:14 +02:00
2019-02-25 03:09:59 +01:00
--------------
2018-04-18 18:25:19 +02:00
2019-02-25 03:09:59 +01:00
## Website is NOT using Cloudflare (& blocking you)
2018-04-18 18:25:19 +02:00
2019-05-07 11:49:47 +02:00
**Anti-Tor users** (formerly "*TorBlocker Hall of Shame Part I*") | [**List Directory**](not_cloudflare/)
2019-03-05 03:35:07 +01:00
| List name | Description |
| -------- | -------- |
| list_error403.txt | Returns HTTP Error 403 (Forbidden) |
2019-05-06 14:09:30 +02:00
| list_error462.txt | Returns HTTP Error 462 |
2019-03-05 03:35:07 +01:00
| list_customerror.txt | Returns custom error message (not HTTP 403) |
2019-04-03 20:55:55 +02:00
| list_other.txt | any other form of tor-hostility or mistreatment |
| 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 is very common. |
| list_formerly_tor-hostile.txt | was previously on one of the above tor-hostile lists |
2019-03-05 03:35:07 +01:00
2019-04-04 01:23:12 +02:00
![](image/siteground.jpg)
2019-03-05 03:37:27 +01:00
```
2019-05-09 00:48:08 +02:00
IMPORTANT: Please add only "FQDN" or "FQDN[space](comment here)"
2019-03-11 00:44:36 +01:00
if "community.example.com" is blocking Tor
2019-05-09 00:48:08 +02:00
add "community.example.com"
2019-03-11 00:44:36 +01:00
2019-05-09 00:48:08 +02:00
if "example.co.uk" is blocking Tor
2019-03-11 00:44:36 +01:00
add "example.co.uk Error message: Anonymous not allowed"
2019-03-05 03:37:27 +01:00
```
2019-03-05 03:35:07 +01:00
2019-02-25 03:09:59 +01:00
Some websites use other companies with the CloudFlare business model.
2018-04-18 18:25:19 +02:00
2019-02-25 03:09:59 +01:00
This is a collection of websites that ban Tor exits, other than through Cloudflare(e.g. showing access denied pages, systematic timing out connections, ...).
2019-03-05 03:38:30 +01:00
2019-05-08 02:16:56 +02:00
[This add-on](addon_firefox/whyrejectme) will help your list_error403 collection.