deCloudflare/deCloudflare
deCloudflare
/
deCloudflare
mirror of https://git.sdf.org/deCloudflare/deCloudflare/
0
0
Fork 0
Code Issues Releases Activity

Update 'instructions.md'

This commit is contained in:
cloudflarevirus 2019-08-25 02:17:03 +02:00
parent 64ae128387
commit dcaaf3e4eb
1 changed files with 1 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
instructions.md
View File

@ -32,7 +32,6 @@ 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.
```
@ -51,7 +50,7 @@ Route 104.18.224.0/20
```
2) How to add your data (A or B)
2) How to add your data
Type A: Push to Codeberg.org
@ -75,9 +74,6 @@ IMPORTANT: Please add only "Base Domain"
... to /split/cloudflare_e.txt
```
Type B: Use "[Is MITM?](https://searxes.eu.org/collab/sxes/tool_ismitm.php)" webpage. Just scan the FQDN.
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)".
@ -138,28 +134,3 @@ This is a collection of websites that ban Tor exits, other than through Cloudfla
Information:
- [How to setup git](instructions_git.md)
- 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](cloudflare_users/ex_cloudflare_users.txt)" - after checking `example.com` with online tool below.
1. Open "[Is MITM?](https://searxes.eu.org/collab/sxes/tool_ismitm.php)" webpage.
3. Input `gitlab.com` and `mastodon.technology` and click `Skanu`.
4. Click `testo` for detailed scan.
`Only a few Cloudflare user leave Cloudflare. False positive is uncommon.`