PS: My last question was marked duplicated incorrectly. For all those marking this as a duplicate of the image copying question posted earlier, I am not interested in preventing just image copying. I am looking for methods for all my html, css and js, not just images

First of all, I understand that there is NO foolproof way to prevent others from ripping my site. (See: Prevent my site from being copied)

This question is not intended for that; rather, I am asking about methodologies to make website ripping more difficult.

Most of the ripping is done via "save-as" (through right clicking). Some of them are using cURL and wget.

  1. I am aware that I can load html elements via dynamically generated ajax. This makes "save-as" saving an empty page.
  2. I understand that there are javascript obfuscators out there which can obfuscate javascript. However, I don't think there are such tools out there for html and css.

Note: A significant portion of my website is dedicated to mobile users. So this makes flash out of the question.

What other methods should I look into?

  • Are your users asked for credentials?
    – Limit
    Oct 21 '16 at 0:23
  • Whomsoever is downvoting the question, please at least give a reason to go with it. This question has already created frustration for the person once, avoid doing it again and again.
    – Limit
    Oct 21 '16 at 1:51
  • 2
    @Limit If you hover your mouse over the down-arrow, a balloon with the reason will appear on your screen. There is no need to add another explanations.
    – techraf
    Oct 21 '16 at 2:11
  • @techraf I know about the tooltip option but clearly the OP is not satisfied with that logic so maybe someobody could just explain it once to him :) That's all
    – Limit
    Oct 21 '16 at 2:13
  • 2
    @Limit And other users are clearly not satisfied with the way OP handles this question, so I thought maybe I could just explain it to you. :) That's all.
    – techraf
    Oct 21 '16 at 2:19

The very nature of the Internet/web means that browsers must have something to parse in order to have something to display. Thus, if you want users to have a site to display in their browsers, then it must be transmitted to their system where it then becomes vulnerable to scraping. So your options are very limited.

You might consider a terminal-based system wherein the users are redirected to a terminal viewer. The browser is actually on the terminal server. Their clicks are transmitted to the server where the web browser renders the page. The end users are effectively receiving a video stream of the website. https://www.citrix.com/products/xenmobile/

Alternatively, you could consider writing an app that takes the place of the browser. Write your webapp/website as a mobile app instead and distribute it through the app store.

Not the answer you're looking for? Browse other questions tagged or ask your own question.