On a Mac with current Chrome (Version 27.0.1453.116) hitting your sample dev URL, I don't get any errors at all...
It is like playing proverbial whack-a-mole. Every update of chrome can potentially change their "heuristic" that thinks it has "found" a phishing attack.. and we have to scramble to see what the heck caused it and fix it.
This would be funny if it wasn't so detrimental to a business. I will get the dev to recreate this on dev1 and post it.