Search.chatgpt.com domain and SSL cert have been created

Post by raincole » Thu, May 02, 2024, 12:25 PM UTC

rany_ wrote: post #7

I know about things like https://crt.sh but how could you be notified about something like this? Is there some service that allows you to be alerted whenever a new certificate is generated for a domain?

Post by spacebanana7 » Thu, May 02, 2024, 12:26 PM UTC

seydor wrote: post #25

jsheard wrote: post #19

Earlier quoted context omitted.

Unless this is the Microsoft deal, and they're using Bing as their indexing backend.

"chat gee pee tee search" is a terrible name. In comparison, bing is genius

Post by [deleted] » Thu, May 02, 2024, 12:26 PM UTC

Post by lifthrasiir » Thu, May 02, 2024, 12:27 PM UTC

lambdaxyzw wrote: post #20

rany_ wrote: post #7

I know about things like https://crt.sh but how could you be notified about something like this? Is there some service that allows you to be alerted whenever a new certificate is generated for a domain?

You can set up your own certificate transparency listener, and get notified of every certificate created, in realtime, assuming you can handle the load. In my company we do this to scan new domains for potential phishing domains, to take them down before they become active.

Post by vbezhenar » Thu, May 02, 2024, 12:27 PM UTC

lambdaxyzw wrote: post #29

filleokus wrote: post #11

I'm taking this opportunity to once again ask for the widespread adoption of the Name Constraints extension in x509, and subsequent roll-out of constrained intermediate CA certs signed by a publicly trusted root. Would be so convenient to have an intermediate CA cert constrained to *.my-name.com to avoid situations like this. Being forced to either use a private PKI infrastructure or using wildcards to not leak host…

The point of certificate transparency is to have a public audit log of every certificate issued. Even if you had your own CA, you would be obliged to report every certificate you issue to the CT. This is a feature, not a bug.