> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://tieback.io/docs/domains-custom-hostnames/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server. # Domains & Custom Hostnames ## Docs - [Domain Architecture](https://tieback.io/docs/domains-custom-hostnames/domain-architecture.md): How tieback serves Digital Product Passports from platform subdomains and verified custom hostnames, and how resolver requests are routed at the edge. - [Resolver Domain Flow](https://tieback.io/docs/domains-custom-hostnames/resolver-domain-flow.md): How tieback resolves Digital Product Passport scan requests across platform subdomains and custom hostnames, from QR scan through redirect to passport. - [Custom Hostname Setup](https://tieback.io/docs/domains-custom-hostnames/custom-hostname-setup.md): How to connect your own domain to tieback so consumers scan and view Digital Product Passports on your branded hostname, with DNS and activation steps. - [DNS Setup Guide](https://tieback.io/docs/domains-custom-hostnames/dns-setup-guide.md): How to configure DNS for a tieback custom hostname, including the CNAME record, activation timings, and how to test resolver and passport responses. - [Resolver and Passport Rendering](https://tieback.io/docs/domains-custom-hostnames/resolver-passport-rendering.md): How tieback scan URLs relate to the rendered Digital Product Passport page, why the two-step redirect exists, and how it stays GS1 Digital Link safe. - [Custom Hostname Lifecycle](https://tieback.io/docs/domains-custom-hostnames/custom-hostname-lifecycle.md): States and transitions of a tieback custom hostname, from initial request through DNS verification, certificate issuance, live traffic, and removal. - [Custom Hostname Troubleshooting](https://tieback.io/docs/domains-custom-hostnames/troubleshooting.md): Common issues and fixes when configuring custom hostnames for tieback Digital Product Passports, covering DNS, certificates, and 403 or 404 responses.