pci.spotify.com
Every SSL/TLS certificate ever issued for this name, indexed from public CT logs.
| domain | status |
|---|---|
| pci.spotify.comcrt.sh Google Trust | expires in 7d |
| pci.spotify.comcrt.sh Google Trust | expires in 7d |
| pci.spotify.comcrt.sh ZeroSSL | expired 10mo ago |
| pci.spotify.comcrt.sh DigiCert | expired 1y ago |
| pci.spotify.comcrt.sh Let's Encrypt | expires in 2mo |
| pci.spotify.comcrt.sh Entrust | expired 1mo ago |
| pci.spotify.comcrt.sh Entrust | expired 1mo ago |
| pci.spotify.comcrt.sh Entrust | expired 7mo ago |
# Python
$ pip install ct-radar
$ ct-radar pci.spotify.com | httpx -silent# Go
$ go install github.com/imfht/ct-radar-cli/cli@latest
$ ct-radar pci.spotify.com | nucleiRelated domains under .com
About certificate history for pci.spotify.com
This page lists every X.509 (SSL/TLS) certificate ever issued for pci.spotify.com and its subdomains, as recorded in public Certificate Transparency (CT) logs. CT logs are an immutable, append-only record of every certificate issued by participating Certificate Authorities (CAs), as required by the major browsers since 2018.
Subdomain enumeration via CT logs is one of the highest-signal techniques in reconnaissance — every time a TLS certificate is issued, all Subject Alternative Names (SANs) on that certificate become public. Internal and forgotten subdomains regularly show up here days after they're set up.
To monitor pci.spotify.com for newly-issued certificates in real-time (useful for detecting unauthorized issuance, phishing variants, or shadow IT) add it to your watchlist (Pro plan).