The eternal problem with the publication of your email, of course, I don’t want to receive spam as a result in my inbox, and here we start to resort to different ways of obfuscation (so that people can understand, but it’s not clear to bots) of our email address.
Silvan Mühlemann took up this issue, created
9 different email boxes , protected them in
9 ways , placed them on a popular
server , so that they could be properly indexed by
google , waited (everything, nothing) for 1.5 years and here it is ...

The graph shows the methods of protection and the amount of spam in mb obtained by each method. As a result, the following 3 methods turned out to be the most reliable:
1. Change directly through CSS <br>moc.etalllit@7raboofnavlis
2. Using CSS display: none
silvanfoobar8@nulltilllate.com
3. ROT13 - codingYou can
encode email in ROT13 using the
rot13 tool or php using the
str_rot13 function and then decode it with Javascript. From 3x, I liked the 2nd method most of all as the easiest to implement.
And, at
451 degrees Fahrenheit you can still read different things.