# Acme.sh supports Google CA, try it!

**URL:** <https://community.letsencrypt.org/t/acme-sh-supports-google-ca-try-it/174804>\
**Category:** Client dev\
**Created:** [March 30, 2022, 3:13pm UTC](https://community.letsencrypt.org/t/acme-sh-supports-google-ca-try-it/174804 "2022-03-30T15:13:11Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![rmhrisk](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@rmhrisk](https://community.letsencrypt.org/u/rmhrisk)\
**Post date:** [April 12, 2022, 7:19pm UTC](https://community.letsencrypt.org/t/acme-sh-supports-google-ca-try-it/174804/21 "2022-04-12T19:19:14Z")

</div>

> [@schoen](#):
>
> I'm kind of curious about the close timing match between Google's creation of this service and their discontinuation of their CT query tool. Is there some reason that they would specifically not want to run both of those things simultaneously?

The CT query tool was not much at all and there were much better tools out there, such as the Facebook CT monitor, Hardenize, Censys, etc.

It is conceivable CT monitoring gets integrated into other products into the future but the product that the web search page wasn't a good fit for use needs based on usage.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 12, 2022, 7:19pm UTC](https://community.letsencrypt.org/t/acme-sh-supports-google-ca-try-it/174804/22 "2022-05-12T19:19:59Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.letsencrypt.org/t/acme-sh-supports-google-ca-try-it/174804.md?page=1)
