spotify.com
Every SSL/TLS certificate ever issued for this name, indexed from public CT logs.
| domain | status |
|---|---|
| canary-certificate-for-noop.spotify.comcrt.sh Cloudflare | expires in 1mo |
| komodo-origin.creators.spotify.comcrt.sh GoDaddy | expires in 24d |
| adshelp.spotify.comcrt.sh Let's Encrypt | expires in 23d |
| images.spotify.comcrt.sh Google Trust | expires in 22d |
| canary-certificate-for-noop.spotify.comcrt.sh Microsoft | expired 2mo ago |
| investors.spotify.comcrt.sh Let's Encrypt | expired 2mo ago |
| clicks.podcasters.spotify.comcrt.sh Entrust | expired 2mo ago |
| info.backstage.spotify.comcrt.sh Microsoft | expired 3mo ago |
| community-stage.spotify.comcrt.sh GlobalSign | expires in 8mo |
| community.spotify.comcrt.sh GlobalSign | expires in 8mo |
# Python
$ pip install ct-radar
$ ct-radar spotify.com | httpx -silent# Go
$ go install github.com/imfht/ct-radar-cli/cli@latest
$ ct-radar spotify.com | nucleiRelated domains under .com
About certificate history for spotify.com
This page lists every X.509 (SSL/TLS) certificate ever issued for 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 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).