DigitalOcean Spaces
DigitalOcean Spaces is a cloud-based object storage service provided by DigitalOcean, a cloud infrastructure provider. It allows users to store and retrieve large amounts of data, such as images, videos, audio files, backups, and logs, using a simple RESTful API or a web-based graphical user interface (GUI).
What detecting DigitalOcean Spaces tells you about a site
DigitalOcean is a developer-friendly cloud, and you usually infer it from delivery hostnames rather than headers — assets served from *.digitaloceanspaces.com (its S3-compatible object storage) or its CDN, or an origin IP in DigitalOcean's ranges. Detecting it leans toward indie developers, startups and small teams who chose simplicity and flat pricing over the sprawl of AWS or GCP. It is a tell about budget and team size more than architecture: DigitalOcean is rarely the home of a Fortune-500 platform, so its presence suggests a leaner operation.
DigitalOcean Spaces in a real-world stack
When you find DigitalOcean Spaces, it rarely travels alone. Often paired with Spaces for static assets and a managed database, fronting an app that could be on Droplets or DigitalOcean's App Platform.
About
DigitalOcean Spaces is a cloud-based object storage service provided by DigitalOcean, a cloud infrastructure provider. It allows users to store and retrieve large amounts of data, such as images, videos, audio files, backups, and logs, using a simple RESTful API or a web-based graphical user interface (GUI).
Categories: CDN, IaaS
Quick facts
Detection methodology for CDN
CDN detection runs against response headers (`cf-ray` for Cloudflare, `x-amz-cf-id` for CloudFront, `x-served-by` for Fastly, `x-cache` for Akamai) and asset hostnames in the page's resource tree. The same site can sit behind multiple CDNs (an edge cache in front of an origin CDN); we surface each one separately so the layered architecture is visible.
How we detect DigitalOcean Spaces
Sourcemap Explorer carries 1 fingerprint signal for DigitalOcean Spaces, spread across 1 channel — dom selector. The exact patterns are listed below, and you can replay each one in Chrome DevTools to confirm a match by hand.
Each signal alone is rarely conclusive — Sourcemap Explorer cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.
A DOM selector that only this technology's pages render. Verified at runtime by the content script.
img[data-src*='.digitaloceanspaces.com'], img[src*='.digitaloceanspaces.com']
FAQ
How do I check if a website is using DigitalOcean Spaces?
Open the page in Chrome, click the Sourcemap Explorer toolbar icon, and read the Stack tab. DigitalOcean Spaces's specific fingerprints here are dom selector, and the popup flags DigitalOcean Spaces whenever any combination of them is found. The same checks can be reproduced manually in DevTools — see the "How we detect" section above.
What DigitalOcean Spaces version can Sourcemap Explorer detect?
DigitalOcean Spaces ships as a hosted cdn rather than a bundled npm package, so version-specific detection isn't always possible. Where the platform leaks a version in response headers (`X-Powered-By`, `Server`, generator meta tags) we surface it; otherwise we report presence only.
How much does DigitalOcean Spaces cost?
DigitalOcean Spaces's pricing model is documented as: payg, recurring. Detection is independent of the pricing tier — Sourcemap Explorer flags the technology by its fingerprints, regardless of which paid plan a site is on. See the official site for the current pricing page.
Where can I read more about DigitalOcean Spaces?
Official site: https://www.digitalocean.com/products/spaces. For Sourcemap Explorer's detection guide, see the deep-dive link below or the related guides in the cross-link section.
Keep reading on Sourcemap Explorer
Practical guides
Alternative tools
Detected by Sourcemap Explorer
Open the popup on any page running DigitalOcean Spacesand you'll see the exact version pulled from the bundled package.json when sourcemaps are exposed.