Filling in the gaps: cakecentral.com. 90 IN A 174.129.211.41 If you look at http://174.129.211.41/ http://174.129.211.41/ without a host you'll see that it'

Filling in the gaps: cakecentral.com. 90 IN A 174.129.211.41 If you look at http://174.129.211.41/ http://174.129.211.41/ without a host you'll see that it's a nginx reverse proxy/cache both beerby and cakecentral are on EC2. Pretty likely that an error was made at some point in the cakecentral nginx config to include a beerby EC2 private IP as part of a load balance pool or as the single back end (either fat fingered or by retaining an old IP as instances were stopped and started). It has since been corrected (probably?), but as cakecentral.com is returning a 404 to robots on their homepage the best, most recent return google has was when it was misdirected.