Domains & launch
Connecting your domains tells Potter which public addresses belong to your Box. Potter Website Hosting then serves the correct merchant website and protects the connection with HTTPS and TLS.
Launch flow
- Add the public domains your organization will use during Box deployment.
- Copy the DNS records provided by Potter into your domain provider.
- Wait for DNS changes to propagate and verify ownership.
- Confirm the domain is ready before announcing it to merchants or customers.
Delegating DNS
Use the records shown by the Box CLI or provided during onboarding. DNS changes can take time to propagate. Keep the records in place while the domain is active on Potter.
A wildcard domain such as *.shop.example.com can provide every merchant with
a branded subdomain without requiring a separate DNS record for each store.
Before going live
- Confirm the domain appears as ready in your deployment workflow.
- Open the merchant website using its public address.
- Verify that the browser shows a valid secure connection.
- Test the domain on desktop and mobile networks.
- Keep your previous service active until the new domain is verified.
How traffic reaches the right merchant
Potter Website Hosting reads the requested public address, identifies the Box and merchant that own it, and serves that merchant’s website. Merchant records remain in the customer-operated Box; the proprietary website engine, templates, TLS operations, and hosting infrastructure remain operated by Potter.