Quote from: hd49728 on August 23, 2019, 10:01:00 AM

On Windows, navigate to "C:\Windows\System32\Drivers\etc\", and open the hosts file in a text editor.
On Mac, navigate to "/private/etc/", and open the host file in a text editor.
On Linux, open terminal and write "sudo nano /etc/hosts"

Add the following two lines to the bottom of the hosts file:

Code:

0.0.0.0 bitcointalk.to
0.0.0.0 fonstavka.com

Your browser will now be unable to open those two phishing sites.

So, what is new in this thread?
Steps to add phishing sites, and turn them off are above, what we need is list of phishing site.

So, if you know any phishing sites, please leave them here, I will add them to the list. I hope that we all will make a long list of phishing sites.

The hosts file is intended to resolve domain names. For example you have a machine in your LAN called "petunia" at 192.168.1.2, you would do

192.168.1.2 petunia

So if you ping petunia your os knows this means 192.168.1.2 before asking a dns server.

Now here comes the important part hd49728: Do NOT, i repeat DO NOT put URLs in there!

You have to REMOVE the http and the / parts, like this:

http://privatemgrgg.pw/vcruntime140.dll -> privatemgrgg.pw

0.0.0.0 privatemgrgg.pw NOT 0.0.0.0 http://privatemgrgg.pw/vcruntime140.dll as you have been doing.

This is a file for manual domain name resolution, it is not a browser and it is not supposed to interpret neither URLs nor files or folders or files within (no /).

When you type the url in the browser, the browser will ask your os what IP address number that domain name has, the browser does NOT ask what http://privatemgrgg.pw/vcruntime140.dll is, it asks for privatemgrgg.pw but you defined http://privatemgrgg.pw/vcruntime140.dll in the hosts file which won't match what the browser (or program) is asking and it won't get "blocked" (resolved to oblivion).

Note that this "blocking trick" may no longer work with newer browsers since they have started to resolve dns using third parties like google's or cloudflare (so called "secure") dns resolvers bypassing the OS entirely by default (YMMV).

Yes there is a way to have your OS do secure dns resolving while NOT handling your dns history to the usual suspects, install dnscrypt-proxy and configure it accordingly. Remember to set your browser to not use their own "secure built-in" resolution as well...

PS: Just because its Linux doesn't mean it comes with nano. You should have used the exact same wording as the other OSes: "open the hosts file with a text editor".