←back to thread

1021 points janpio | 1 comments | | HN request time: 0.289s | source
Show context
Animats ◴[] No.45676471[source]
If you block those internal subdomains from search with robots.txt, does Google still whine?
replies(2): >>45676712 #>>45677686 #
snailmailman ◴[] No.45676712[source]
I’ve heard anecdotes of people using an entirely internal domain like “plex.example.com” even if it’s never exposed to the public internet, google might flag it as impersonating plex. Google will sometimes block it based only on name, if they think the name is impersonating another service.

Its unclear exactly what conditions cause a site to get blocked by safe browsing. My nextcloud.something.tld domain has never been flagged, but I’ve seen support threads of other people having issues and the domain name is the best guess.

replies(1): >>45676809 #
donmcronald ◴[] No.45676809[source]
I'm almost positive GMail scanning messages is one cause. My domain got put on the list for a URL that would have been unknowable to anyone but GMail and my sister who I invited to a shared Immich album. It was a URL like this that got emailed directly to 1 person:

https://photos.example.com/albums/xxxxxxxx-xxxx-xxxx-xxxx-xx...

Then suddenly the domain is banned even though there was never a way to discover that URL besides GMail scanning messages. In my case, the server is public so my siblings can access it, but there's nothing stopping Google from banning domains for internal sites that show up in emails they wrongly classify as phishing.

Think of how Google and Microsoft destroyed self hosted email with their spam filters. Now imagine that happening to all self hosted services via abuse of the safe browsing block lists.

replies(6): >>45676948 #>>45676999 #>>45677030 #>>45677045 #>>45677050 #>>45677845 #
EdwardKrayer ◴[] No.45677050[source]
Well, that's potentially horrifying. I would love for someone to attempt this in as controlled of a manner as possible. I would assume it's possible for anyone using Google DNS servers to also trigger some type of metadata inspection resulting in this type of situation as well.

Also - when you say banned, you're speaking of the "red screen of death" right? Not a broader ban from the domain using Google Workplace services, yeah?

replies(1): >>45679064 #
1. donmcronald ◴[] No.45679064[source]
> Also - when you say banned, you're speaking of the "red screen of death" right?

Yes.

> I would love for someone to attempt this in as controlled of a manner as possible.

I'm pretty confident they scanned a URL in GMail to trigger the blocking of my domain. If they've done something as stupid as tying GMail phishing detection heuristics into the safe browsing block list, you might be able to generate a bunch of phishy looking emails with direct links to someone's login page to trigger the "red screen of death".