UCP status report
zzll.org
No UCP profile was found at /.well-known/ucp on zzll.org.
Not Detected
HTTP 404
Response 363 ms
Checked 22 Oct, 12:02 UTC
Check trace
How zzll.org answered our check
Our request for the profile got no profile back, so the other four ways in were never reached.
0 of 5 reached
4 requests · 363 ms at the store · public requests only
4 requests · 363 ms at the store · public requests only
-
Finding the profileNot found
-
Acting for the buyerNot reached
-
In the buyer's browserNot reached
-
Calling its servicesNot reached
-
Sending the buyer to the websiteNot reached
UCP Checkerpublic requests
- 2 requestsFinding the profile/.well-known/ucp · 404
- 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 found
01 · Finding the profile2 requests
Nothing at /.well-known/ucp (404 Not Found).
Not reached
The other four ways in
Without the profile there is no list of services, sign-in or links to try.
- 01 PROFILEGET /.well-known/ucp → 404 Not Found363 ms
- 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
- 01 PROFILENothing to validate: no profile was read–
- OUTSIDE UCPGET / → 200, Organization schema found–
- OUTSIDE UCPGET /llms.txt → 404, not found–
Request
GET https://zzll.org/.well-known/ucp
Response
404 Not Found, in 363 ms
The fix
Publish a profile at
/.well-known/ucp and it will be read and scored on the next check. {
"ucp": {
"version": "2026-08-25",
"services": {
"dev.ucp.shopping": [
{
"version": "2026-08-25",
"spec": "https://ucp.dev/2026-08-25/specification/overview",
"transport": "rest",
"schema": "https://ucp.dev/2026-08-25/services/shopping/rest.openapi.json",
"endpoint": "https://zzll.org/ucp"
}
]
},
"capabilities": {
"dev.ucp.shopping.checkout": [
{
"version": "2026-08-25",
"spec": "https://ucp.dev/2026-08-25/specification/shopping/checkout",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/checkout.json"
}
]
},
"payment_handlers": {
"com.example.processor": [
{
"id": "processor-1",
"version": "2026-08-25",
"spec": "https://example.com/ucp/handler",
"schema": "https://example.com/ucp/handler/schema.json"
}
]
}
}
}
Is zzll.org your store?
Claim it with one DNS record.
Why isn't zzll.org verified for UCP?
On 22 October 2026,
zzll.org/.well-known/ucp didn't return a UCP profile, so there was nothing to validate. Stores don't publish one for a few reasons: some haven't published one yet; some don't allow automated requests, even to public pages; and some work with agents another way, such as a direct partnership with an AI platform or their own agent programme. This check looks only for a public UCP profile, so it can't tell which applies to zzll.org.Can AI agents still shop on zzll.org?
Not through UCP. Without a profile, a UCP agent has no published way to find zzll.org's catalogue, cart or checkout. Whether other agents can shop there is up to zzll.org: its own terms and any integrations it offers.
How can zzll.org get verified?
By publishing a UCP profile at
/.well-known/ucp. The /.well-known/ucp guide shows what goes in it, and the UCP Validator checks it before it goes live. Once it is published, run a new check from this page.How was this UCP report for zzll.org generated?
With public requests on 22 October 2026: we asked for
zzll.org/.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 zzll.org?
This page shows the stored result of our last check (22 October 2026). To run a new one, enter zzll.org 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.