News for hackers. Stuff that matters.
Re:How I hacked chess.com with a rookie exploit by mmsc on Friday January 26, 2024 @10:30PM (#39152219)
Cool bug.

  Google did not like me setting up a chess.com subdomain, and a couple of weeks later, my domain got flagged for "phishing." - I had to contact them to explain and manually remove it as it affected my whole domain.
What? Google’s domain registrar will close your account if you have a subdomain which just happens to be named another website?
Re:How I hacked chess.com with a rookie exploit by JakeSkii on Saturday January 27, 2024 @04:34AM (#39154038)
OP - I'm honestly not sure what happened, it could be just based on the naming or something else to do with it. Either way, when I visited it, Googles Safe Browsing alert popped up with "Deceptive site ahead - recentley detected phishing".
Re:How I hacked chess.com with a rookie exploit by lobsterthief on Saturday January 27, 2024 @05:37AM (#39154406)
This is a newish _Chrome_ feature (within the past 2 years) that Google rolled out. Any subdomain that looks like a domain (especially ending in a common TLD) will trigger that warning.

I learned that because, at work, I architected a system for serving certain assets for customer sites at a subdomain off a shared root domain, keyed by their full domain (like example.com.example.org—where example.com is the customer’s site domain). We ended up changing to example-com.example.org which is far better anyways since this feature started breaking stuff once it rolled out.

But this is a Chrome feature and should not affect your rankings themselves. But couldn’t hurt to take it down just in case.

Re:How I hacked chess.com with a rookie exploit by JakeSkii on Saturday January 27, 2024 @06:04AM (#39154539)
Interesting, thanks for the insight!