UCP Checker
Check a store
UCP status report

170c86-3.myshopify.com

170c86-3.myshopify.com’s robots.txt disallows the UCP profile path, so an agent that honours robots.txt will not read it.

Blocked
robots.txt disallows /.well-known/ucp Checked 21 Oct, 16:02 UTC
Check trace

How 170c86-3.myshopify.com answered our check

Our request for the profile wasn't made, so the other four ways in were never reached.

0 of 5 reached
3 requests · public requests only
  1. 01Hosting ↗
    Finding the profile
    Not requested
  2. 02Identity Linking ↗
    Acting for the buyer
    Not reached
  3. 03Embedded ↗
    In the buyer's browser
    Not reached
  4. 04Services ↗
    Calling its services
    Not reached
  5. 05continue_url ↗
    Sending the buyer to the website
    Not reached
UCP Checkerpublic requests
  • not requestedFinding the profilenot requested · robots.txt
  • Acting for the buyernot reached
  • In the buyer's browsernot reached
  • Calling its servicesnot reached
  • Sending to the websitenot reached
  • 2 requestsOutside UCPhomepage · /llms.txt
Not requested
01 · Finding the profilenot requested
robots.txt disallows /.well-known/ucp, so we didn't ask for the profile.
Not reached
The other four ways in
Without the profile there is no list of services, sign-in or links to try.
  1. 01 PROFILENo request for /.well-known/ucp: robots.txt disallows it–
  2. 01 PROFILEGET /robots.txt → disallows /.well-known/ucp–
  3. 01 PROFILENothing to validate: no profile was read–
  4. OUTSIDE UCPGET / → 429, no Organization schema found–
  5. OUTSIDE UCPGET /llms.txt → 429, not found–

What we requested

Request
None. robots.txt disallows /.well-known/ucp, so we did not ask for the profile.
robots.txt
Disallows /.well-known/ucp, so an agent that honours robots.txt will not read the profile, and we did not request it.
The fix
Allow /.well-known/ucp in robots.txt so the profile can be read and scored.
Is 170c86-3.myshopify.com your store?
Claim it with one DNS record.
Claim this store

Questions

Why is 170c86-3.myshopify.com's profile blocked?
170c86-3.myshopify.com's robots.txt disallows /.well-known/ucp. Agents that follow robots.txt won't read the profile, even if one is there.
Is this intentional?
We can't tell from outside. Some stores refuse automated requests on purpose; others do it through a firewall or bot-protection default. If 170c86-3.myshopify.com wants UCP agents to find its profile, /.well-known/ucp needs to answer automated requests.
How was this UCP report for 170c86-3.myshopify.com generated?
With public requests on 21 October 2026: we asked for 170c86-3.myshopify.com/.well-known/ucp and read its robots.txt. No profile came back, so there was nothing to validate. No sign-in, no purchase and no manual review. How we check.
How do I get a newer result for 170c86-3.myshopify.com?
This page shows the stored result of our last check (21 October 2026). To run a new one, enter 170c86-3.myshopify.com on the Check page.
Why does this status matter?
Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.