VB.NET
12-10-2003, 02:41 AM
Hi,
having long been fed up with spam, I decided to take some measures by outputting emails on my website with Javascript. By describing the steps I took and the end result, I hope people here can tell me if this makes grabbing emails from my site somewhat more difficult
1. original email taken from the database replaces @ with [at]. So if one views source, all the emails will be like person[at]server.com
2. javascript replaces [at] with @, so when user clicks on email link, it will go to the real @dress
You can see this at http://epics.ecn.purdue.edu/jds/asp/members.asp (if you reload a couple of times you will notice the replacement taking place)
(Also if someone can test it on nonIE browsers that would be great)
I still display the RAW ORIGINAL @email on the webpage (after being replaced by javascript); however it is only [at]email in the source code. Should I get rid of any trace of raw email on the website to be more secure?
having long been fed up with spam, I decided to take some measures by outputting emails on my website with Javascript. By describing the steps I took and the end result, I hope people here can tell me if this makes grabbing emails from my site somewhat more difficult
1. original email taken from the database replaces @ with [at]. So if one views source, all the emails will be like person[at]server.com
2. javascript replaces [at] with @, so when user clicks on email link, it will go to the real @dress
You can see this at http://epics.ecn.purdue.edu/jds/asp/members.asp (if you reload a couple of times you will notice the replacement taking place)
(Also if someone can test it on nonIE browsers that would be great)
I still display the RAW ORIGINAL @email on the webpage (after being replaced by javascript); however it is only [at]email in the source code. Should I get rid of any trace of raw email on the website to be more secure?