Well I had been procrastinating on putting dragonblogger.com behind Incapsula again due to the fact that Incapsula doesn’t do full DNS management, which means I had to do my DNS Zone Editor from my DNS company point to Incapsula, and then Incapsula point the IP behind the scenes to my web hosting company, technically adding 3 hops into the mix just to resolve DNS and end up on the right server instead of 2 just having the DNS provider point directly to web host, but in the end the fact that I was hit with a denial of service attack against my XMLRPC this weekend means I had no choice but to protect the site.
Synthesis informed me over 119,000+ hits against xmlrpc.php which is the remote publishing protocol for WordPress which I need active for Live Writer and some other services, I don’t know the source IP, but it clearly was an attack or compromise of a service that does direct remote publishing.
Meanwhile, Incapsula would likely help prevent and have allowed me to analyze at the cloud layer and block at the Incapsula cloud without having to have my web host find and block the IP’s on their side, so DragonBlogger is repointed and now on Incapsula. This gives me greater control and awareness if some unhealthy attacks or IP’s are coming in in handling it, as with WebSynthesis hosting I don’t have a panel to really look at logs and do anything at the web host end.
I use Incapsula for all of my sites, and it does a fantastic job protecting them and providing analytics.
This is an original article from WP Cypher Copyright 2012
