deCloudflare/instructions.md

110 lines
4.0 KiB
Markdown
Raw Normal View History

2019-02-25 02:09:59 +00:00
# Instructions
--------------
2018-10-11 13:00:30 +00:00
2019-02-25 02:09:59 +00:00
## Website is using Cloudflare
2018-10-11 13:00:30 +00:00
| List name | Description |
2018-10-11 13:04:44 +00:00
| -------- | -------- |
2019-02-25 02:20:36 +00:00
| /split/cloudflare(X).txt | Split files (base domain) |
| ex_cloudflare_users.txt | Domains which used Cloudflare in the past, not anymore |
| 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 03:41:09 +00:00
| cloudflare_owned_NS.txt | Name Server owned by Cloudflare |
2018-10-11 13:17:40 +00:00
| cloudflare_owned_domains.txt | Domains owned by Cloudflare |
| cloudflare_owned_onions.txt | Tor .onions owned by Cloudflare |
2018-10-11 13:00:30 +00:00
2018-10-11 13:12:11 +00:00
1) How to detect Cloudflare
2018-10-11 13:00:30 +00:00
2019-03-02 23:01:42 +00:00
There are many ways to detect it:
2018-10-11 13:12:11 +00: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 02:11:43 +00:00
- Use "[Is MITM?](https://searxes.danwin1210.me/collab/sxes/tool_ismitm.php)" webpage.
2019-03-02 23:01:42 +00: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-02 23:02:09 +00:00
2019-03-02 23:01:42 +00:00
```
emsisoft.com. 21599 IN NS bella.ns.cloudflare.com.
emsisoft.com. 21599 IN NS dom.ns.cloudflare.com.
```
2019-03-02 23:02:09 +00:00
2019-03-02 23:01:42 +00: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-02 23:02:09 +00:00
2019-03-02 23:01:42 +00: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 13:00:30 +00:00
2019-04-02 02:11:43 +00:00
2019-04-01 23:11:34 +00:00
2) How to add your data (A or B)
Type A: Push to NotABug.org
2018-10-11 13:00:30 +00:00
2019-02-25 02:09:59 +00:00
1. Log in to *notabug.org*.
2. Click "*Fork*" button. (top-left corner)
2018-10-11 13:12:11 +00:00
3. Edit text file.
2019-02-25 02:09:59 +00:00
4. Click *Double-arrow* button to create a *new pull request*.
2018-10-11 13:00:30 +00:00
2018-10-11 13:12:11 +00:00
```
2019-02-25 02:14:30 +00:00
IMPORTANT: Please add only "Base Domain"
2019-02-25 02:09:59 +00:00
if "community.example.com" is using Cloudflare
2019-02-25 02:14:30 +00:00
add "example.com"
if "www.example.co.uk" is using Cloudflare
add "example.co.uk"
2019-02-25 02:09:59 +00:00
if "example.net" is using Cloudflare
2019-02-25 02:14:30 +00:00
add "example.net"
... to /split/cloudflare_e.txt
2019-02-25 02:09:59 +00:00
```
2019-04-01 23:11:34 +00:00
Type B: Just search about it on Searxes
Search the domain on Searxes, and it'll appear as "[MITM!] link name".
2019-02-25 02:12:19 +00:00
3) If the website *no longer using Cloudflare*, *remove* it from /split/ list and *add* to "[ex_cloudflare_users.txt](https://notabug.org/themusicgod1/cloudflare-tor/src/master/ex_cloudflare_users.txt)".
2018-04-18 16:27:14 +00:00
2019-02-25 02:09:59 +00:00
--------------
2018-04-18 16:25:19 +00:00
2019-02-25 02:09:59 +00:00
## Website is NOT using Cloudflare (& blocking you)
2018-04-18 16:25:19 +00:00
2019-03-05 02:35:07 +00:00
| List name | Description |
| -------- | -------- |
| list_error403.txt | Returns HTTP Error 403 (Forbidden) |
| list_customerror.txt | Returns custom error message (not HTTP 403) |
2019-04-03 18:55:55 +00: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 02:35:07 +00:00
2019-04-03 23:23:12 +00:00
![](image/siteground.jpg)
2019-03-05 02:37:27 +00:00
```
2019-03-10 23:44:36 +00:00
IMPORTANT: Please add only "Base Domain" or "(base domain)[space](comment here)"
if "community.example.com" is blocking Tor
add "example.com"
if "www.example.co.uk" is blocking Tor
add "example.co.uk Error message: Anonymous not allowed"
if "example.net" is blocking Tor
add "example.net"
2019-03-05 02:37:27 +00:00
```
2019-03-05 02:35:07 +00:00
2019-02-25 02:09:59 +00:00
Some websites use other companies with the CloudFlare business model.
2018-04-18 16:25:19 +00:00
2019-03-05 02:32:35 +00:00
Add them to [/not_cloudflare/](not_cloudflare/) (formerly "*TorBlocker Hall of Shame Part I*")
2018-04-18 16:25:19 +00:00
2019-02-25 02:09:59 +00: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 02:38:30 +00:00
2019-04-03 23:23:12 +00:00
[This add-on](https://addons.mozilla.org/en-US/firefox/addon/which-website-rejected-me/) will help your list_error403 collection.