I agree and i report everywhere - Hosting, DOmain registrar, Google Safe Browsing, NetCraft< Urlhaus, Abuse.ch and so on.
That being said, I would like Let’s encrypt to step their game up and be able to absorb reports from twitter.
I do not have time to use their abuse forms and yada yada
I’d prefer want when i tag a bad site and @leyencrypt - someone to
- see it
and - act upon it.
this is what this post is about
I can also give a small ammount of money for this initiative. If enough people chip in we can make it a salary.
do not give me generic advice
EDIT: i read the link you gave me
there is something nice there
At least for the time being, Let’s Encrypt is going to check with the Google Safe Browsing API before issuing certificates, and refuse to issue to sites that are flagged as phishing or malware sites. Google’s API is the best source of phishing and malware status information that we have access to, and attempting to do more than query this API before issuance would almost certainly be wasteful and ineffective. (Update: As of January 10, 2019, we no longer check domains against the Safe Browsing API.)
That means that all my reports to GSB and NetCraft automatically were linked to Lets encrypt!
GOOD! But why did it get disabled? The explanation looks like a “we are not a content policing entity watch dog, leave us alone and bother the hosting”
“We’ve stopped checking with Google Safe Browsing primarily because Domain Validation certificates are intended solely for use in securing the transfer of data between a site and its visitors. This is a critical component of a secure experience, but it does not mean that a site’s contents are safe. The question of whether or not content is safe is not one that we can accurately answer, and it is outside the scope of certificates and HTTPS.”