It looks like the test URL I posted earlier can show up as invalid in some versions of Chrome and also in Safari. Because of how Chrome updating works, as well as how Google Safe Browsing works, it's hard to tell which versions and configurations of Chrome will show the problem URL and which ones won't. My guess is that Google is busting ass to make sure all known tester URLs are handled by Google Safe Browsing and thinking about accelerating their update schedule ...