Timeline for Obfuscating domain names
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2011 at 13:39 | comment | added | Chris S | I think that would work perfectly. I'd still include some character to 'not obfuscate' it in the source code. It might also be nice if it caught strings that match (\w{5}-){4}\w{5} and changed a few random characters (or warned the user, or something...). | |
| Feb 16, 2011 at 2:26 | comment | added | John Gardeniers | @Chris, There's no need for the obfuscation to be obvious or the actual URLs to be modified. It's quite simple to obfuscate any text so that it won't get indexed (or harvested) but still look "normal" to humans. For an example have a look at my web page and then look at the source. | |
| Feb 16, 2011 at 2:06 | comment | added | Chris S | +1 How about something special to not obfuscate the domain/email/IP. For instance prefix it with a "?" or similar. Also ignore example.com, the internal IP ranges, etc. | |
| Feb 14, 2011 at 9:00 | history | answered | John Gardeniers | CC BY-SA 2.5 |