[pevey]

I'm not saying this is acceptable in any way... But there IS something you can try to get resolved fairly quickly if it ever happens again.

Be sure to claim domain ownership in the Google search console. If there is a flag of some sort, it will show up there. And you can address it there.

I worked for a financial services company where this happened. The public-facing .com domain was set up first, before I got there. Later, I added the .net domain behind zero trust to serve as our entry point for internal apps. Google marked the .net as a phishing domain. Verifying ownership of both under the same google search console account and then contesting the flag got it removed.

[midenginedcoupe]

This evidently doesn't work for all flags. Your own experience != all other peoples' experience.

My domain ownership was already registered even before it was flagged. I _think_ it was the search console I used to request a review of the flag. But it still took that long to resolve.

This wasn't an issue of not realising what had happened for 3 days, it was 3 days after letting Google know they'd got it wrong. And spending hours on the phone to anyone I could get hold of to try to escalate etc.

[mike_d]

You want the Postmaster Console for delivery and abuse issues, not the Search Console which is probably why you couldn't find anything.

If you've already verified your domains in the search console it is one click to add them. https://postmaster.google.com/

[ImPostingOnHN]

what number do you call to speak to a human at Google to help when this doesn't work "fairly quickly"?

obviously the biggest issue described in the above post is the lack of humans in the loop

[hansvm]

If you can afford it, the fastest and easiest technique I've found is just showing up at HQ. The front desk is kind and helpful and knows the right person to route you to.