Go-live checklist

Use a domain and DNS zone that your team owns. Exercise both an automatic path and guided manual setup before enabling Domain0 for customers.

Server boundary

• Production uses a separate Domain0 application and API key.
• The API key is stored only in the server secret manager.
• The session endpoint authenticates the user and checks product ownership.
• DNS records come from trusted product data, not arbitrary browser input.
• Connection IDs are stored with your product's domain record.
• Browser tokens are issued for one connection and the exact production origin.

Browser flow

• The same-origin bridge is deployed over HTTPS.
• Connect opens from a customer action and restores focus when closed.
• Success updates the visible domain state without a full-page reload.
• Closing and reopening resumes the existing connection.
• Expired browser access is refreshed through your server.
• Branding, copy, and supported locales have been reviewed.
• The flow works with keyboard navigation and browser zoom.

Provider paths

• Provider detection works for a controlled test domain.
• An automatic authorization and exact change-plan review completes.
• Forced manual mode shows copyable records and verifies completion.
• Ambiguous provider detection allows an explicit provider selection.
• A conflicting record is shown safely before any replacement.
• Propagation pending can be resumed after closing the dialog.

Events and webhooks

• Browser success, close, and step events update the intended product state.
• The webhook endpoint is public HTTPS when webhook delivery is enabled.
• Verification uses untouched bytes and the original headers.
• eventId is deduplicated in the same transaction as the product mutation.
• Unknown event types are ignored safely until your integration supports them.
• Logs contain request and connection IDs, never credentials or bearer tokens.

Final check

Run the complete flow with production configuration and a disposable DNS name. Verify the expected record at every authoritative nameserver, confirm your product recognizes success, then remove the disposable connection from your own product data.