# Suspicious web traffic after creating a certificate

**URL:** <https://community.letsencrypt.org/t/suspicious-web-traffic-after-creating-a-certificate/203443>\
**Category:** Issuance Tech\
**Created:** [August 13, 2023, 2:34pm UTC](https://community.letsencrypt.org/t/suspicious-web-traffic-after-creating-a-certificate/203443 "2023-08-13T14:34:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JamesLE](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jamesle/32/49364_2.png) [@JamesLE](https://community.letsencrypt.org/u/JamesLE)\
**Post date:** [August 13, 2023, 4:33pm UTC](https://community.letsencrypt.org/t/suspicious-web-traffic-after-creating-a-certificate/203443/2 "2023-08-13T16:33:44Z")

</div>

All certificates from Let's Encrypt are placed in publicly accessible logs. This system is known as Certificate Transparency. It is required for certificates to be trusted by Google Chrome, Apple Safari, and other browsers and systems.

Internet scanners can and do identify hosts based on names found in certificates logged to Certificate Transparency.

For more information, please see our documentation: [Certificate Transparency (CT) Logs - Let's Encrypt](https://letsencrypt.org/docs/ct-logs/)

---

_[View the full topic](https://community.letsencrypt.org/t/suspicious-web-traffic-after-creating-a-certificate/203443)._