Re: Escalation point at Google

[Jared Mauch <jared () puck nether net>]

Are they getting an error similar to:

Websites prove their identity via certificates, which are issued by certificate authorities. Most browsers no longer 
trust certificates issued by GeoTrust, RapidSSL, Symantec, Thawte, and VeriSign. www.example.com uses a certificate 
from one of these authorities and so the website’s identity cannot be proven.

You may want to check your site here:


https://www.ssllabs.com/ssltest/analyze.html?d=www.example.com

- Jared


> On Nov 12, 2018, at 3:44 PM, George Herbert <george.herbert () gmail com> wrote:
>
> If this is re os33.com where Alex emailed from, the front page is Lets Encrypt.  Which is a strange choice for a 
> financial SAAS?...
>
> Alex, if your internal app site certs are Symantec that could well explain it; check your cert locations.
>
> On Mon, Nov 12, 2018 at 12:30 PM Guillaume Tournat <guillaume () ironie org> wrote:
> Hello
>
> Problem with blacklisted CA of Symantec, that issued SSL certificates ?
>
>
>
> Le 9 nov. 2018 à 02:57, Alex Osipov <alex () os33 com> a écrit :
>
> > Hello –
> >
> >  
> >
> > Does anyone have an escalation point or a human to speak to on the Google escalations or  Google Safe Browsing team? 
> >  Our entire SaaS business, 15 years in business, in a niche software industry with a good reputation has become 
> > blocked in ALL browsers.  We are impacting 30k+ enterprise users in the financial space and have tried everything 
> > but all roads lead to automated systems. 
> >
> >  
> >
> > Can anyone please reach out with a contact if you have one? 
> >
> >  
> >
> > Sorry to spam this list if this is inappropriate content.  Very desperate here. 
> >
> >  
> >
> > Thank you,
> >
> > Alex Osipov / CTO
>
>
> -- 
> -george william herbert
> george.herbert () gmail com