UCP Checker
Check a store
UCP status report

365jersey.com

We could not read 365jersey.com’s UCP profile: our request was refused (HTTP 403). That is what our crawler met, not a statement about how the store treats other agents.

Blocked
HTTP 403 Response 124 ms robots.txt allows /.well-known/ucp Checked 23 Oct, 05:01 UTC
Check trace

How 365jersey.com 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
2 requests · 124 ms at the store · public requests only
  1. 01Hosting ↗
    Finding the profile
    Refused
  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
  • 2 requestsFinding the profile/.well-known/ucp · 403
  • Acting for the buyernot reached
  • In the buyer's browsernot reached
  • Calling its servicesnot reached
  • Sending to the websitenot reached
Refused
01 · Finding the profile2 requests
Our request for the profile was refused (403 Forbidden). robots.txt allows the path, so this came from a firewall or bot rule.
Not reached
The other four ways in
Without the profile there is no list of services, sign-in or links to try.
  1. 01 PROFILEGET /.well-known/ucp → 403 Forbidden124 ms
  2. 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
  3. 01 PROFILENothing to validate: no profile was read–

What we requested

Request
GET https://365jersey.com/.well-known/ucp
Response
403 Forbidden, in 124 ms
robots.txt
Allows /.well-known/ucp, so the refusal came from the server, usually a firewall or bot-protection rule.
The fix
If this is your store, allow unauthenticated GET requests to /.well-known/ucp at your firewall or bot protection, then check again.
Is 365jersey.com your store?
Claim it with one DNS record.
Claim this store

Questions

Why is 365jersey.com's profile blocked?
Our request to /.well-known/ucp was refused (HTTP 403). This usually means a firewall or bot-protection rule is rejecting unauthenticated automated requests — even though the profile is supposed to be public. It is what our crawler met on that date, not a statement about how 365jersey.com treats other agents.
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 365jersey.com wants UCP agents to find its profile, /.well-known/ucp needs to answer automated requests.
How was this UCP report for 365jersey.com generated?
With public requests on 23 October 2026: we asked for 365jersey.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 365jersey.com?
This page shows the stored result of our last check (23 October 2026). To run a new one, enter 365jersey.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.