Website traffic is hijacked? How to solve?

　　The so-called flow is to hijack other people's traffic, take it over, to become their own. Such is the middleman earnings. Web site traffic flow are generally people get the number. It can also be said to be the site hijacking.
　　So the problem is how to detect the site of the hijacking?
　　IIS7 website monitoring
　　whether the test site has been hijacked, DNS information pollution detection.
　　How to solve the problem of traffic hijacking?
　　To increase the listener on a page, insert dom whenever you return, then insert the rules of our own to capture all the dom, dom then these features added to the exception in all. In addition to any dom insert all removed. So these hijacked ads will immediately be deleted when inserted.
　　There is also another approach.
　　Not the DOM, using C language and framework of Emscripten, WebAssembly write programs with full-screen canvas to do their own set of interface or even a window manager (back-end do not know Emscripten qt like to now not to the extent of use) They engaged in a OpenSSL and the like, by self WebSocket protocol and server communication, or even engage in a back-end of the desktop of the front end.
　　WebAssembly so long as the loader and a few lines of HTML that is not tampered with, on the line.
　　If you just want to monitor treatment, simply the whole DOM dynamically generated, always monitor the establishment of all DOM elements, all without their own script .js extension but only to determine the Content-Type, anti-hijack critical logic with WebAssembly avoid being modified once DOM is inserted in an external script, or the like element, directly hit the log to the server.
　　Of course, with the full link traffic hijacking, the end of HTTPS (not only to the user station further comprising a link to a CDN source station, etc.) can be solved half.