spotify.com — domain analysis

What is spotify.com about?

The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:

• songs ×2
• globaltop ×2

Does spotify.com publish the usual trust pages?

All four of the pages a established business normally publishes were found:
about, contact, privacy and terms.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

How does spotify.com compare with other domains analysed here?

Measured against the 73 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.

Related domains in this index

Other analysed domains served from the same country:

• apple.com.tr
• erone.com
• freefirenamestyle.com
• kcu.com
• mocospace.com
• movisda.com
• perfectgift.com
• petsmart.com

When was spotify.com registered?

spotify.com was registered on 23 April 2006, which makes it about 20 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is Abion AB.

Registration runs until 23 April 2030.

The domain carries 5 registry locks, which blocks unauthorised transfer or deletion.

Where is spotify.com hosted?

The first address resolves to infrastructure in Kansas City, United States.

The network is operated by Google Cloud (AS396982 Google LLC).

Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.

What is spotify.com running on?

No platform, framework or analytics fingerprints were found in the homepage markup of spotify.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.

No recognisable platform, framework or analytics fingerprints were found in the homepage markup.

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

At 210ms to first byte this response is unremarkable for a homepage measured from a single European location.

The HTML weighs 301KB, which is ordinary for a homepage.

The HTML is compressed with gzip.

What does the homepage say about itself?

The title is 40 characters, inside the range that displays without truncation.

A meta description of 78 characters is present.

No H1 heading was found, so the page offers no single top-level statement of what it is.

All 84 images on the homepage have alt attributes.

Is spotify.com served over a valid certificate?

The HTTPS certificate is issued by DigiCert Inc and is
valid until 2027-01-23, which is 110 days from the date of this check. It covers
2 hostnames.

• *.spotify.com
• spotify.com

The certificate has 110 days left to run.

It covers 2 hostnames, so it was issued for this site specifically.

Which security headers does it set?

3 of 6 are set (HSTS, Content Security Policy, X-Content-Type-Options). Absent: X-Frame-Options, Referrer-Policy, Permissions-Policy.

How is DNS configured for spotify.com?

spotify.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.

Mail is handled by 7 exchangers.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 24.224.186.35.bc.googleusercontent.com, 2600:1901:1:7c5::, which usually names the hosting provider.

Who runs DNS and mail for spotify.com?

DNS is operated by Google Cloud DNS rather than self-hosted name servers.

Mail is handled by Google Workspace.

The domain publishes AAAA records and accepts connections over IPv6.

What else is worth noting about spotify.com?

4 of 4 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.

Can spotify.com be spoofed in email?

DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.

No CAA records are published, so any certificate authority may issue a certificate for this domain.

The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.

What else does spotify.com publish?

A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.

An ads.txt file is published with 26 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.

An app-ads.txt file is also published, which indicates mobile app inventory alongside the website.

What does robots.txt allow?

robots.txt is 592 bytes and names
1 user-agent group.

It does not blanket-disallow general crawlers.

Sitemaps declared:

• https://www.spotify.com/sitemap.xml

AI crawler policy

robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.

What structured data does the homepage publish?

No JSON-LD or microdata was found on the homepage.

What does spotify.com load from third parties?

The homepage pulls resources from 9 third-party hosts (charts-images.scdn.co, daily-mix.scdn.co, encore.scdn.co, i.scdn.co, lineup-images.scdn.co, mosaic.scdn.co). Each one sees the visitor IP and user agent on every page load.

5 cookies are set before any interaction (sp_t, sp_landing, sp_t, sp_new, sp_landing).

Does spotify.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

The www address redirects to https://open.spotify.com/, so the site settles on one canonical hostname.

How easily can spotify.com be crawled?

A sitemap index is served at https://www.spotify.com/sitemap.xml listing 10 entries.

A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.

What tracking does spotify.com run?

No analytics or advertising trackers were detected on the homepage of spotify.com, which is unusual for a commercial site.

How does spotify.com look when shared?

All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.

The page declares 12 hreflang alternates (x-default, en, id, de, pt, ja, fr, ar, es, tr, it, vi), so it targets more than one language or region.

How are images, fonts and scripts handled?

84 images on the homepage, 0 of them lazy-loaded (0%).

All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.

No srcset attributes are used, so every device is served the same image size regardless of screen.

The page pulls 1 external stylesheet and 4 external scripts, with 2 carrying defer or async.

Responses carry Varnish/Fastly edge and edge cache edge headers, so content is served from a CDN rather than straight from the origin.

Is spotify.com accessible and current?

The page uses 1 landmark element and 90 ARIA attributes.

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

Can search engines index spotify.com?

Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.

The canonical points to a different host (https://open.spotify.com), which tells search engines the authoritative copy lives elsewhere.

The homepage carries 92 internal and 0 external links across 0 outside hosts.

Visible text is only 0.4% of the HTML, which indicates the page is assembled in the browser rather than served as content.

How is spotify.com delivered?

No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.

A web app manifest is declared, so the site is installable as a progressive web app.

Analysed 5 October 2026.
Analyse another domain →