Skip to content
https://spotify.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 1559 ms total
FIX
2 redirect(s), 1559 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1559 ms total
Got: 1559 ms
Info::
Cross-domain redirect detected

https://spotify.com

1137 ms · HTTP/1.1

301

https://www.spotify.com/

168 ms · HTTP/1.1

301

https://open.spotify.com/

254 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://spotify.com3011137 msHTTP/1.1envoy
2https://www.spotify.com/301168 msHTTP/1.1envoy
3https://open.spotify.com/200254 msHTTP/1.1envoy

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

B
TLS Certificate Expiry & Recommendations
236 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

236
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: HTTP/2 edgeproxy, 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: HTTP/2 edgeproxy, 1.1 google
A
DNS Records
1 A records, 326 ms lookup
PASS
1 A records, 326 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 35.186.224.24
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2600:1901:1:7c5::
Info::
5 nameserver(s) configured
Got: ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, dns1.p07.nsone.net, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com
Info::
7 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (326 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 326 ms
A35.186.224.24
AAAA2600:1901:1:7c5::
CNAME—
NSns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, dns1.p07.nsone.net, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx5.googlemail.com
10 aspmx4.googlemail.com
10 aspmx3.googlemail.com
TXT
wiz-domain-verification=370862886b04dfa626d54d2c4cc955174c6f3164a104a85d725ae5ec...
google-site-verification=buTP-BbGUoP8lPntqskvSbeS68M4PDoIFkiUtQEA5n8
jamf-site-verification=1kKxrm0glhWvrA0YiABH_w
notion-domain-verification=AqUDuql68X5rQ1qLwho6huUjf4QteXZlyvTIKS1txnq
facebook-domain-verification=wtgn9pdvjdhs21j9gz6knsnpkafvs5
tiktok-developers-site-verification=98xFqMKsOJ51nNJpUCGPGbo7m17gtf7f
reachdesk-verification=v0DuUrKxORfyqxIOMkJm57GlQtvaAv0watqt7x7ylMN21LAHqR6dEhUpS...
onetrust-domain-verification=508849d40e2b4b8fba2b7eaf84f1bddc
loom-site-verification=3ee9ca8c2df34d08abbb7be5185bc768
tiktok-developers-site-verification=ttGXJxgq1HQKquomgiljzFq53uoLHcUC
cloudflare_dashboard_sso=19cd522a4fc20281209f03663d34ee76
atlassian-sending-domain-verification=d90f2e0c-fa57-43b6-910f-065cc4d6a0e3
_anz60jg9dhixqlmcv20ntnooz9m0k8x
have-i-been-pwned-verification=33b7ae688099ee8cca63259b769a0ea8
cursor-domain-verification-985xgr=7ROYkkLIfunrK2GtW0spMGDNw
liveramp-site-verification=IAXPTLlWofr4aaKtwVqirrHvOqUMiXnaMW8WMmuz1v0
google-site-verification=uD4f4k01lFWX3qwVbqnVaJg8atpKgAgc-_RYcyT3ofU
facebook-domain-verification=qyrvuca7h4s7wevhzbprtt3tdyyhf1
google-site-verification=0wmxUE7T2OWPhtwjco6oCyqqbYgtosjQdywAr4G4kU0
windsurf-verification=LRBAV_kH3G5aleY1GIc1jMUg_8iBpigIm2qYF00bRps=
status-page-domain-verification=wq4jns7ydgbb
parallels-domain-verification=7bb3a358f26f4e23a5077648266570c873182a57d6d44e47a5...
openai-domain-verification=dv-VNYvLsJIttFvRz7ymxFgjrPC
anthropic-domain-verification-mqtmtz=BSac9xfxvigNt4Ralt2KPkt1V
google-site-verification=ESiNWockZgSgTPSsrsAdMX9afsj2-_8504nQ0qIHkDA
MS=ms38184034
atlassian-domain-verification=1My5WsxLluUY8uIjgbLs4MY3ySFp32k9aYNW2IR4ihM64k58Cx...
tiktok-developers-site-verification=pZNawVY3o5Ma80MRCC6Fref1NiLzuEVU
google-site-verification=ehIHBRyAOKdOfUyw_ONXT0TMuUsdk1gDGSYfk8YhRgw
docker-verification=82f3553a-fb50-4d4e-9607-8a8079ee354f
vmware-cloud-verification-dab4c35d-1819-4431-add3-d3c382ee32bc
SPF v=spf1 ip4:80.76.146.172 ip4:80.76.146.173 include:_spf.google.com include:serve...
apple-domain-verification=Dxae2sKJD2O5TKGK
yahoo-verification-key=bdudmGyddArwRiVafgItrfYq8nrhd5vzNZ7Ik/G0ILM=
zapier-domain-verification-challenge=db8a0b98-bb6a-4f84-a699-344dc23fef3b
CAALookup not available with standard resolver
Resolved in 326 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
IPv6 Readiness
IPv6 reachable (3 ms)
PASS
IPv6 reachable (3 ms)
Info::
IPv6 is configured and reachable at 2600:1901:1:7c5::
Got: 3 ms connect
IPv6 Ready
AAAA Records 2600:1901:1:7c5:: Connection Reachable (3 ms)
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 592 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 592 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /*/about-us/contact/contact-spotify-password/
Disallow: /*/about-us/contact/contact-spotify-account/
Disallow: /*/get-spotify/*
Disallow: /*/xhr/*
Disallow: /*/external/*
Disallow: /*/legal/*?ets=
Disallow: /*/legal/advertiser-terms-and-conditions/
Disallow: /*/legal/gdpr-article-15-information/
Disallow: /*/legal/spotify-controller-data-processing-terms/
Disallow: /*/legal/podcast-api-terms/
Disallow: /*/account/cls/*
Disallow: /*/starbuckspartners
Disallow: /starbuckspartners
Disallow: /ppt/*?
Disallow: /partner/*?
Sitemap: https://www.spotify.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 10 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.spotify.com/
200https://spotify.com/

Preferred variant: non-www

HTTP → HTTPS

301http://spotify.com/ → https://www.spotify.com/

Consistent

A+
Domain Intelligence
spotify.com — via Abion AB, 20 years, 3 months old
PASS
spotify.com — via Abion AB, 20 years, 3 months old
Info::
Domain registered until Apr 23, 2030 (4 years remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Abion AB
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

1408 days

April 23, 2030

SSL certificate

236 days

Issued by DigiCert Inc

Domain age

20 years, 3 months

Registered April 23, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1901:1:7c5::

Registrar

Abion AB

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Abion AB
Created April 23, 2006 (20 years, 3 months ago)
Expires April 23, 2030 (4 years)
Last Updated July 8, 2024
Name Servers dns1.p07.nsone.net, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 2600:1901:1:7c5::
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 134 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
2 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
135 ms
Total Time Total request time from DNS lookup through full response.
135 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 3 ms TLS Handshake 8 ms Server Processing 122 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback