To avoid causing problems, there are a bunch of places that Cloudflare won't obfuscate email addresses. The advantage of this is that bots need to execute the JavaScript on your page in order to retrieve your email address, which raises the barrier (slightly) for bots trying to scrape the email address from your app. When the page is served, the script is executed, and the tag is replaced with the original. It will modify this element inline, and inject a script element: Contact me

If cloudflare detects an email address in an tag, for example: Contact me This has multiple parts to it, but the one I was most interested in was email obfuscation.Ĭloudflare's email obfuscation works by modifying the HTML output of your app when they serve it. One of the features of Cloudflare is Scrape Shield. At the same time, I also removed the Cloudflare caching layer, as Netlify uses its own layer of caching. Some time ago I moved my blog from a self-hosted instance of Ghost to Netlify. Somewhat surprisingly perhaps, I don't get a huge amount of spam because of it. I've personally only ever had pleasant emails from people (though I'm well aware that's a rarity for many people in our industry).

I include my email address on the about page of my blog in case people want to get in touch. It's obfuscation, not encryption! Background - Cloudflare Scrape Shield It's only meant to provide rudimentary protection against automated scraping by bots. It's important to note that the encoding scheme used here is incredibly weak. It uses a similar approach as Cloudflare Scrape Shield. In this post I show a simple way to obfuscate email addresses to make it harder for bots to scrape them from your site.

Email obfuscator albion