Website profiles · Technology insights · Alternatives

cosmos.so

Public Work is a visual search engine for public domain content. Explore 100,000+ copyright-free images from The MET, New York Public Library, and other sources

No paid content found
Visit website
Profile views 22 Outbound visits 39 Normal
Public Work by Cosmos / Cosmos Full homepage screenshot

At a glance

Category
Stock Photos
Language
English
Paid-content signal
No paid content foundObserved
Registered
2020
Hosting
Amazon CloudFrontInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Cosmos?

Cosmos is an image-discovery and visual-reference app built around searching and organizing pictures rather than text-heavy browsing. Its own framing is “Your space for inspiration,” with collections that are “connected, searchable, yours.” In practice, it works like a personal mood-board library combined with a visual search engine: you save images you like, then find them later by how they look or what they contain.

What you can actually do

  • Search by color or by visual similarity, not only by keyword.
  • Filter to include or exclude content flagged as likely AI-generated.
  • See context for an image — Cosmos says it researches images and surfaces the artist, source, and story.
  • Keep your own collections and references in one searchable place.

Who it suits

Designers, art directors, photographers, architects and creative teams who collect references constantly and need to retrieve them by visual instinct. The page specifically mentions “the world’s top creative teams,” so collaboration and shared inspiration are part of the pitch. If you mostly need precise text search across documents, this is not that tool.

How it differs from a plain image search

Need Cosmos approach
“Find something that looks like this” Visual similarity search
“Find something in this palette” Search by color
“Avoid AI-generated images” AI-content detection with show/hide control
“Who made this and where is it from?” Source, artist and story research
“Keep my references together” Personal collections

The trade-off is that visual search rewards browsing and intuition more than exact queries; you may need to iterate with an image or a color rather than a phrase. A practical first step: download the app, save a handful of references you already like, then test whether color and similarity search surface them the way you remember them. If it does, it can replace the scattered screenshots and bookmarks most people use. For broader visual research alongside it, Are.na and Pinterest serve different collecting styles, while Behance leans more toward finished portfolio work.

How does Cosmos's visual search compare to keyword search for finding design references?

Cosmos is built around visual search first: you can search by color, by visual similarity, or by describing what you want, and results are meant to feel like browsing a moodboard rather than running queries. Keyword search still exists in the usual sense, but the page frames it as one way in among others — "search the way you think" — rather than the primary method. The bigger differentiator is that Cosmos attaches context to images: it researches them and surfaces artist, source and story, and it can flag content detected as likely AI-generated, with options to blur or hide it.

For design references, that changes what each approach is good at:

  • Keyword search works when you can already name the thing: "vitsoe shelving," a designer, a material, a studio, an era. It is fast and precise when your vocabulary matches the catalogue's.
  • Visual search works when you have a feeling rather than a word: a palette, a texture, a composition, a "more like this" instinct. Color and similarity search are the practical tools here.
  • AI-content filtering matters if you are collecting references for real-world projects and don't want generated imagery mixed into your boards.

The trade-off is control versus discovery. Keyword search gives you predictable, repeatable results you can refine; visual search gives you range and surprise but less precision, and you will spend more time curating. A workable habit is to start visual when you're exploring, then switch to keyword once you can name the direction — or the reverse, seeding a search with a known reference and using similarity to fan out from it.

If you want to see how this fits an actual workflow, the obvious next step is to try one real brief in both modes: search a term you'd normally use, then search the same idea by color or by uploading a similar image, and compare which set you'd actually put in front of a client. Cosmos is at Cosmos, and it also offers an app if you collect references on a phone.

Can I identify the original artist or source of an image I found elsewhere using Cosmos?

Yes. Cosmos is built to research images and surface the artist, source and story behind them, so an image you bring in from elsewhere is the kind of thing it is meant to identify.

How that works in practice

You can search by visual similarity rather than relying on keywords, and the results are presented with attribution context — the page shows credited examples such as "Editorial photography by Guiri," a plate from Unformen der Kunst by Karl Blossfeldt, and a project credited to OOAA Arquitectura Studio with design by Iker Ochotorena. That mix of photographer, publication and studio credits is the signal you want: it names a creator or a source, not just a matching picture.

Two limits are worth knowing before you rely on it:

  • Detection is not attribution. Cosmos can flag content as likely AI-generated, which tells you an image may have no human author to find — a dead end for provenance, not a wrong answer.
  • A close visual match is not proof of authorship. Reposts, mood boards and uncredited re-uploads often rank highly, so treat the top result as a lead to verify.

A concrete scenario

Say you saved a minimalist interior shot from a social feed and want to credit the architect. Bring the image into Cosmos, search by visual similarity, then check whether the result names a studio or project. If it does, confirm independently on that studio's own site before you publish the credit. If the results are only reposts, try a cropped detail — furniture, a window line, a wall texture — since distinctive fragments often pull up the original shoot rather than the viral edit.

When it is the right tool

Use Cosmos when you need to trace a reference back to a person or publication for credit, licensing enquiries or research. It is less useful when you already know the subject and just want more of it — that is closer to browsing. For a second opinion on a stubborn image, general reverse-image tools can complement it: Google Images and TinEye. If the trail leads to a photographer or studio, look for their own site or an agency page to confirm the credit.

The practical rule: trust a named credit enough to investigate it, and never publish an attribution you have only seen on Cosmos.

How does Cosmos help creative teams organize and share visual references?

Cosmos is built around the idea that a visual reference library should be searchable and contextual, not just a folder of saved images. Its page describes it as "your space for inspiration," where collections, references, and taste are "connected, searchable, yours." For a creative team, that means the value is less about storage and more about retrieval and shared context.

How it helps organize references

  • Collections as the core unit. References live in collections rather than loose files, so a team can group images by project, client, mood, or campaign.
  • Search that matches how people actually think. The site highlights searching by color and by visual similarity, plus AI-content detection to flag images likely generated by AI. This is useful when you remember a reference visually but not by filename or source.
  • Context attached to images. Cosmos says it "researches images—surfacing the artist, source, and story." For a team, that reduces the friction of crediting, sourcing, or explaining why a reference matters.

How it helps sharing

Because collections are described as connected and searchable, the practical workflow is: one person adds a reference, and others can find it through search or browse the shared collection instead of asking for a link. The page also mentions inspiration for "the world's top creative teams," which suggests the intended audience is teams that already treat references as a shared asset.

A concrete scenario

A design lead preparing a pitch could build a collection for the client, add references by color and visual similarity, and let the art director and copywriter pull from the same set. When someone asks "where did this image come from?", the source and story are part of the reference rather than a separate research task.

Trade-off to consider

Search by visual similarity and color is powerful for discovery, but it depends on the library being populated and tagged consistently. Teams that save images ad hoc without organizing them into collections will get less out of it. If your team already has a messy shared drive, the first step is deciding who curates collections and how they are named.

Next step

If you want to evaluate it, start with one real project: create a collection, add ten references, and test whether color or visual-similarity search finds them faster than your current method. For broader context on visual research tools, see Cosmos.

What does Cosmos's AI content detection mean for the images I save or search?

Cosmos labels images it believes were likely generated by AI, and lets you blur or hide those results while you search. On the page, that control sits alongside other ways of searching—by color and by visual similarity—under the idea of searching "with and without AI." So the detection is a filter on what you see and save, not a verdict about your own library.

In practice, three things follow:

  • A label, not a removal. AI-flagged images can still appear; they're marked so you can decide. Blur keeps them in the grid but obscures the preview; hiding removes them from view.
  • Detection is a guess. "Likely generated by AI" means the system is estimating, so expect occasional misses and false flags, especially with heavy retouching, 3D renders or synthetic-looking photography.
  • Curation stays yours. Because Cosmos also surfaces the artist, source and story behind an image, you can check provenance when a label looks wrong—useful if you're collecting references for client work where licensing and credit matter.

Who this suits: designers and art directors building moodboards who want a clean, human-made reference set by default, and anyone who needs to know quickly whether an image has a real photographer behind it. If your work deliberately mixes AI-generated and photographed material, the blur option is the better setting—you keep the range without losing the signal.

A practical next step: pick one project and run the same search twice, once with AI content hidden and once blurred, and compare the saved collections. If hiding strips out references you actually wanted, keep it blurred and judge each flagged image by its source instead.

Is there a mobile app for Cosmos, and what can I do with it?

Yes. Cosmos is app-first: the site's calls to action are "Get the app" and "Download the app," alongside a web sign-up option. So the mobile app is the primary way to use it, with the browser version as a secondary entry point.

What you can do in the app

Based on what the site shows, the app is built around saving, organising and searching visual references:

  • Build collections — "Your collections, your references, your taste. Connected, searchable, yours." This is the core loop: save images you find or upload, and group them into collections.
  • Search visually, not just by keyword — the site highlights searching "by color" and "by visual similarity," plus a conventional search field.
  • Filter by AI content — you can flag content "detected as likely generated by AI," and show or blur it.
  • See attribution for images — Cosmos "researches images—surfacing the artist, source, and story," so a saved image can carry its photographer, designer or studio credit.
  • Follow editorial content — the site references an editorial photography credit and a short film, suggesting curated feeds sit alongside your own saves.

Who it suits

Designers, art directors, photographers and creative teams doing mood boards or visual research. The site explicitly targets "the world's top creative teams," which hints at shared or team-oriented collections rather than purely personal scrapbooking.

Practical next step

If you're deciding whether it fits your workflow, install the app and run one real test: save five images from a current project, then try finding one again by colour or similarity rather than by name. If that retrieval feels faster than your existing folder-and-filename system, the app earns its place. For adjacent reference and mood-board tools, compare with Are.na and Pinterest.

Related questions

More questions →
How Search Engines Find, Crawl, and Rank Pages: A Practical SEO Workflow

Search engines work in three separate stages: discovery, crawling/indexing, and ranking. A page can fail at any one of them, and each failure has a different fix. If your page isn't showing up, the fastest path is to check the stages in order — don't jump straight to "ranking factors" before you've confirmed the page is even indexed.

This guide walks through each stage, what blocks it, and a step-by-step diagnostic sequence you can run with free tools.

Stage 1: Discovery — How Search Engines Find Your URLs

Before a search engine can crawl a page, it has to know the URL exists. There are four main discovery paths:

  • Links from other sites (external backlinks)
  • Internal links from pages already known to the search engine
  • XML sitemaps you submit
  • Redirects and canonical signals pointing to the URL

What blocks discovery

  • Orphan pages: no internal links point to them, and no sitemap includes them. These are effectively invisible.
  • Sitemap errors: a sitemap that lists non-canonical URLs, returns errors, or isn't referenced in robots.txt.
  • Noindex on linked pages: if the only page linking to your target is itself excluded, the crawler may never follow the path.

Practical fix

  1. Add at least one contextual internal link from a page that is already indexed.
  2. Confirm the URL appears in your XML sitemap and that the sitemap is submitted.
  3. Check robots.txt doesn't disallow the path.

Stage 2: Crawling and Indexing — Getting the Page Stored

Crawling means the bot fetches the page. Indexing means the content is stored and eligible to appear in results. These are not the same thing — a page can be crawled but not indexed.

Common crawl blockers

Blocker Where it lives Effect
Disallow rule robots.txt Bot won't fetch the URL
noindex meta tag Page <head> Page fetched but excluded from index
X-Robots-Tag: noindex HTTP header Same as above, applies to non-HTML files
Login wall / paywall Server Bot sees a different page than users
Slow or erroring server Hosting Crawl budget wasted, page may be dropped

Common indexing blockers (page is crawled but not stored)

  • Thin or duplicate content: near-identical to another URL on your site.
  • Canonical tag pointing elsewhere: you're telling the engine "index that page instead."
  • Soft 404: page returns 200 but looks empty or error-like.
  • Wrong canonical chosen by the engine: often caused by conflicting signals (sitemap says A, canonical says B).

How to check index status

Use a site: query in the search engine (for example, site:example.com/page) as a rough check. It's not exact, but it tells you whether the URL is in the index at all. For a more structured view, use the search engine's own webmaster console if you have one — that's the authoritative source for coverage status.

Stage 3: Ranking — Why an Indexed Page Still Doesn't Appear

Once a page is indexed, ranking depends on relevance and authority signals. The main on-page levers:

Title and headings

  • The title tag is still one of the strongest relevance signals. Put the primary topic near the front.
  • H1 and subheadings should reflect what the page actually covers, not keyword-stuffed variants.
  • Mismatch between title and body content is a common reason a page ranks for nothing.

Content depth and intent match

  • Does the page answer the question the searcher is asking? A page about "search engines" that only defines the term will lose to a page that explains crawling, indexing, and ranking.
  • Cover the subtopics a searcher would expect. Thin coverage on a broad topic rarely ranks.

Internal links and authority

  • Internal links pass context and relative importance. A page with no internal links is treated as low priority.
  • External backlinks still matter, but quality and relevance outweigh raw count.

Technical signals

  • Mobile rendering: if the mobile version hides content, rankings suffer.
  • Core Web Vitals: page experience is a tiebreaker, not a primary driver, but poor performance can hurt.
  • HTTPS and clean URL structure: baseline expectations.

A Step-by-Step Diagnostic Sequence

Run these in order. Stop when you find the failure point.

  1. Is the URL in the index? Run site:yourdomain.com/page. If nothing appears, go to step 2. If it appears, skip to step 5.
  2. Is it blocked by robots? Check robots.txt for a Disallow rule matching the path. Check the page's meta robots and HTTP X-Robots-Tag.
  3. Is it discoverable? Confirm the URL is in your sitemap and has at least one internal link from an indexed page.
  4. Is it canonicalized elsewhere? Check the rel="canonical" tag. If it points to a different URL, that URL is the one being indexed.
  5. Is it indexed but not ranking? Compare your title and H1 against the query. Check whether the page covers the subtopics the top results cover.
  6. Check backlinks and keyword position. Free tools like the ones on SmallSEOTools.com can give you a backlink overview and keyword position tracking. Treat these as directional signals, not precise measurements — free backlink and rank tools typically sample data and can differ from what a search engine's own console reports.

Common Misconceptions

"Submit the URL and it indexes instantly." Submission queues a crawl; it doesn't guarantee indexing or timing. Indexing can take hours to weeks depending on the site.

"Meta keywords help ranking." They've been ignored by major search engines for years. Don't spend time on them.

"I can guarantee a #1 ranking." No tool or service can guarantee a specific position. Rankings depend on competition, query, location, and personalization. Anyone promising a fixed position is overstating what's controllable.

"More backlinks always means better rankings." Low-quality or irrelevant links can be ignored or actively harmful. Relevance and trust matter more than volume.

"If it's indexed, it should rank." Indexing is eligibility, not promotion. A page can be indexed and still rank on page 10 because it's less relevant or less authoritative than competitors.

Quick Reference: Which Stage Is Failing?

Symptom Likely stage First check
URL not in site: results Discovery or crawling robots.txt, internal links, sitemap
Crawled but not indexed Indexing Canonical tag, content uniqueness, meta robots
Indexed but ranks poorly Ranking Title/H1 match, content depth, internal links
Ranked, then dropped Crawling or ranking Server errors, content changes, lost links

Work through the stages in order. Most "my page won't rank" problems turn out to be discovery or indexing problems, and those are usually the fastest to fix.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2020, this domain has about 6 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is NameCheap, a widely used domain service provider. The domain uses the common .so extension, which is not an independent safety signal.

DNS and Email

The lowest TTL is 60 seconds, supporting rapid record changes at the cost of more frequent lookups. Nameservers are provided by Amazon Route 53, indicating managed DNS hosting. MX records point to the Google Workspace email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Amazon cloud or CDN ecosystem. The certificate is valid for about 197 days in total, with 97 days remaining.

HTTP and Browser Security

X-Powered-By exposes backend information: Next.js. The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. The x-cache, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value istio-envoy.

Technology Stack Analysis

The public page identifies Next.js, Amazon CloudFront without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Open Graph is partially configured; og:type is missing. Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 6 characters, within a common display range. A meta description is present, with 26 characters.

Hosting and Email

DNSAmazon Route 53
HostingAmazon CloudFront
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 13.227.65.101

Registration details

RDAP / WHOIS

RegistrarNameCheap
Registered2020-06-16
Expires2031-06-16
Domain statusactive https://icann.org/epp#active、clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Nameserversns-1105.awsdns-10.org、ns-1857.awsdns-40.co.uk、ns-705.awsdns-24.net、ns-92.awsdns-11.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Awww.cosmos.so13.227.65.10160—
Awww.cosmos.so13.227.65.11060—
Awww.cosmos.so13.227.65.12660—
Awww.cosmos.so13.227.65.4760—
AAAAwww.cosmos.so2600:9000:2202:200:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:3400:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:5c00:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:6800:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:b400:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:b800:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:c600:14:8672:fc00:93a160—
AAAAwww.cosmos.so2600:9000:2202:ee00:14:8672:fc00:93a160—
MXcosmos.soaspmx.l.google.com144001
MXcosmos.soalt1.aspmx.l.google.com144005
MXcosmos.soalt2.aspmx.l.google.com144005
MXcosmos.soalt3.aspmx.l.google.com1440010
MXcosmos.soalt4.aspmx.l.google.com1440010
NScosmos.sons-1105.awsdns-10.org172800—
NScosmos.sons-1857.awsdns-40.co.uk172800—
NScosmos.sons-705.awsdns-24.net172800—
NScosmos.sons-92.awsdns-11.com172800—
TXTcosmos.sofacebook-domain-verification=ueqk35lrg6njuf30vwbedwa3vsgy3h14400—
TXTcosmos.sogoogle-site-verification=C2QZeHe4j9dsf-rzg26TrolCwef4xNrkQLCmgd9gTVc14400—
TXTcosmos.sogoogle-site-verification=TmVkiuKAy4MBTmlPkqlmtqjNW3-fnGKcKneDhaGFk4I14400—
TXTcosmos.sogoogle-site-verification=g0_gGiFq6hX7F0InTaPs7Bs-uGPHG9fdH4E0qIR9tSQ14400—
TXTcosmos.sogoogle-site-verification=kywqYvAu_VSPtcTPs1Gi1VEBJV8u8vEZzxEJ0FGiQkw14400—
TXTcosmos.somixpanel-domain-verify=491b153c-f8ad-4184-a569-df07e3be936214400—
TXTcosmos.sov=spf1 +a +mx +a:ns-705.awsdns-24.net include:_spf.google.com include:_spf.mailspamprotection.com ~all14400—
DMARC_dmarc.cosmos.sov=DMARC1; p=quarantine; pct=10; rua=mailto:[email protected], mailto:[email protected];ruf=mailto:[email protected];fo=1;140—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subject*.cosmos.so
IssuerAmazon
Valid until2026-12-29T23:59 · Remaining when checked: 97 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlprivate, no-cache, no-store, max-age=0, must-revalidate
serveristio-envoy
set-cookieRedacted

Identified technologies

Next.jsAmazon CloudFront

Pages, Search and Sharing

Meta descriptionYour space for inspiration
Canonical URLhttps://www.cosmos.so
LanguageEnglish (default)
Twitter Cardsummary_large_image
All bots 2 allowed · 9 disallowed
  • Allow/
  • Allow/_next/image
  • Disallow/api/
  • Disallow/studio/
  • Disallow/login
  • Disallow/signup
  • Disallow/forgot-password
  • Disallow/settings/
  • Disallow/account/
  • Disallow/external/
  • Disallow/*?*
gptbot 1 allowed · 8 disallowed
  • Allow/
  • Disallow/api/
  • Disallow/studio/
  • Disallow/login
  • Disallow/signup
  • Disallow/forgot-password
  • Disallow/settings/
  • Disallow/account/
  • Disallow/external/
oai-searchbot 1 allowed · 8 disallowed
  • Allow/
  • Disallow/api/
  • Disallow/studio/
  • Disallow/login
  • Disallow/signup
  • Disallow/forgot-password
  • Disallow/settings/
  • Disallow/account/
  • Disallow/external/
claudebot 1 allowed · 8 disallowed
  • Allow/
  • Disallow/api/
  • Disallow/studio/
  • Disallow/login
  • Disallow/signup
  • Disallow/forgot-password
  • Disallow/settings/
  • Disallow/account/
  • Disallow/external/
claude-searchbot 1 allowed · 8 disallowed
  • Allow/
  • Disallow/api/
  • Disallow/studio/
  • Disallow/login
  • Disallow/signup
  • Disallow/forgot-password
  • Disallow/settings/
  • Disallow/account/
  • Disallow/external/
perplexitybot 1 allowed · 8 disallowed
  • Allow/
  • Disallow/api/
  • Disallow/studio/
  • Disallow/login
  • Disallow/signup
  • Disallow/forgot-password
  • Disallow/settings/
  • Disallow/account/
  • Disallow/external/
chatgpt-user 1 allowed · 0 disallowed
  • Allow/
claude-user 1 allowed · 0 disallowed
  • Allow/
perplexity-user 1 allowed · 0 disallowed
  • Allow/
google-extended 1 allowed · 0 disallowed
  • Allow/
applebot-extended 1 allowed · 0 disallowed
  • Allow/
bytespider 0 allowed · 1 disallowed
  • Disallow/
ccbot 0 allowed · 1 disallowed
  • Disallow/

Recent Updates

  • HTTP Response Information
  • Website Description
  • Website Name

User reviews (0)

  • No reviews yet.