It would be beneficial to have your eMail-Address on your homepage when you want to give people the opportunity to contact you. In my case, I actually want to give people that opportunity ((That does not go without saying: In some cases it is very important to discourage people from contacting you directly. For instance, it could be that you are <i>usually</i> not the right person to ask, but you get flooded with requests that you have to manually redirect elsewhere: It would be better if people got discouraged from contacting you while finding it very easy to contact the person that can <i>actually</i> help them.)). However, we all know that there are villains out there who harvest emails from websites in order to sell them to spammers. Hence, you would want to obfuscate your eMail-Address in such a way that it cannot be read from the HTML source code of the website easily. It goes without saying that naive obfuscation techniques like `mymail(at)domain(dot)com` are beaten more easily by machines than by people, and the more creative you get with your substitutions, the easier the machines can do it and the less easy your customers can. Images are the end of that line of thought, the point where a user has no chance at all other than to copy your eMail address letter by letter from an image which could still theoretically be <a href="http://en.wikipedia.org/wiki/Optical_character_recognition" target="_blank">OCR</a>'d by a decent program. Therefore, Javascript methods to encode and on-the-fly decode the eMail address ((Famous enodings are <a href="http://en.wikipedia.org/wiki/Rot13" target="_blank">ROT13</a>, <a href="http://en.wikipedia.org/wiki/Base64" target="_blank">Base64</a>, etcetera.)) seemed like the best choice to me for a long while. It is harder to run a Javascript interpreter than simple regular expressions for the email harvester, but to a user there is no difference: The browser already comes equipped with Javascript. At this point, some people get cranky that everything should work also without Javascript, and I can understand that. However, the main reason for me to abandon the Javascript method was simple necessity: I have to publish my eMail on the homepage of a university, which is managed from within a complex <a href="http://de.wikipedia.org/wiki/Content-Management-System" target="_blank">CMS</a>, and the system would not allow me to use Javascript. This makes a lot of sense, you don't want every user of a large webportal to be able to stick whatever Javascript they like into the page, that stuff can make everything go to hell. <a href="http://www.jayway.com/2012/11/30/smart-email-obfuscation-using-css/" target="_blank">This blog post</a> is one among many advertising the capability of unicode to display letters from right to left. However, seriously, how difficult do you think it is for an email harvester to check for <i>reversed</i> email addresses as well? I would suppose it's more or less just a matter of checking for the <i>reversed</i> regular expression, too. Easy prey, if you ask me. But I had an idea! <a href="https://blag.nullteilerfrei.de/2013/11/08/email-obfuscation-from-several-directions/#more-2271" class="more-link">Do you want to know what that idea was?</a>