GS1 Digital Link Conformance
Daily automated run of the official GS1 Digital Link Resolver test suite against the Closient resolver. We don't reimplement the tests — we run GS1's own JavaScript and report exactly what it says.
Test it yourself
Every claim on this page can be checked from any terminal — no account, no API key. The commands below run against www.closient.com using GS1's demo GTIN 09506000164908.
HTML redirect (what a consumer scan does)
curl -I https://www.closient.com/01/09506000164908
Returns the 30x redirect plus RFC 8288 Link headers, including rel="linkset".
Linkset via content negotiation
curl -s -H "Accept: application/linkset+json" https://www.closient.com/01/09506000164908
Returns the RFC 9264 linkset document instead of redirecting.
Linkset via query string
curl -s "https://www.closient.com/01/09506000164908?linkType=linkset"
Same linkset, requested with ?linkType=linkset — no Accept header needed.
JSON-LD structured data
curl -s -H "Accept: application/ld+json" https://www.closient.com/01/09506000164908
Returns a schema.org + GS1 Web Vocabulary JSON-LD document for the product.
Resolver description file
curl -s https://www.closient.com/.well-known/gs1resolver
The GS1-required description of this resolver's capabilities.
How other resolvers compare
Facts verified 2026-06-11 — verify yourself with the commands above, pointed at each resolver. Notably, id.orcascan.com does not return application/linkset+json.
| Capability | Closient | id.gs1.org | id.gs1uk.org | id.orcascan.com |
|---|---|---|---|---|
| Accept: application/linkset+json returns an RFC 9264 linkset |
Yes
200 with Content-Type: application/linkset+json
|
Yes
200 with Content-Type: application/linkset+json
|
Untested
No publicly resolvable demo GTIN found; tested GTINs return 404
|
No
application/linkset+json is not returned
|
| Accept: application/ld+json returns JSON-LD |
Yes
200 with Content-Type: application/ld+json
|
Partial
200, but labelled Content-Type: application/json
|
Untested
No publicly resolvable demo GTIN found
|
No
Not observed
|
| RFC 8288 Link headers on redirect, incl. rel="linkset" |
Yes
Full Link header set; rel="linkset" points at the linkset
|
Partial
Rich Link header (CURIE rels like gs1:pip) but no rel="linkset" observed
|
Untested
No publicly resolvable demo GTIN found
|
No
Not observed
|
| Public, continuously updated conformance results page |
Yes
This page — the official GS1 suite, run daily
|
No
Not published
|
No
Not published
|
No
Not published
|
| /.well-known/gs1resolver resolver description file |
Yes
200, JSON description of this resolver
|
Yes
200 with Content-Type: application/ld+json
|
Partial
File present but contains unedited GS1 Resolver CE template placeholders (resolverRoot https://id.mydomain.org, contact “My Organisation”)
|
No
404
|
Test source: gs1/GS1DL-resolver-testsuite — the unmodified JavaScript published by GS1 at https://ref.gs1.org/test-suites/resolver/. We run it in a headless browser against our resolver once a day and persist the result. No tests are reimplemented.
Want to run the suite against any GS1 Digital Link URI right now? Try the interactive test page.