Warning. This is a non-real simulation. If you do harm to other people by exploiting the following, you will be punished by law.
For this DNS spoofing test, the sniffing should be preceded. Refer the sniffing procedure here.
❑ Detail procedure
It's simple. I used hosts file. It has the characteristic that are referenced in preference to DNS query results.
The victim system then accesses the sites reflected in the hosts file.
In my case, www.rlacjftn123.com worked but the zum and binance didn't work. The above image is the result of setting to connect to msn.com when inputting to www.rlacjftn123.com.
And this is result of DNS spoofing with Ettercap. I tried to connect to microsoft.com but failed.
Approximately since the second quarter of 2017, spoofing on most sites has been become difficult because the many web browsers are more secure than before including IE.
For this DNS spoofing test, the sniffing should be preceded. Refer the sniffing procedure here.
❑ Overview
1. Set sniffing environment.
2. Create the hosts file.
3. # dnsspoof -f [Host file path]
4. Connect to the websites.
❑ Detail procedure
It's simple. I used hosts file. It has the characteristic that are referenced in preference to DNS query results.
The victim system then accesses the sites reflected in the hosts file.
In my case, www.rlacjftn123.com worked but the zum and binance didn't work. The above image is the result of setting to connect to msn.com when inputting to www.rlacjftn123.com.
And this is result of DNS spoofing with Ettercap. I tried to connect to microsoft.com but failed.
Approximately since the second quarter of 2017, spoofing on most sites has been become difficult because the many web browsers are more secure than before including IE.