A live infrastructure experiment

Brendan + Instinct set this up.

This small site exists to make the custom-domain customer journey tangible: choose a hostname, prove control, route traffic, issue a certificate, and verify the result.

HTTPS connected
01 · HOST

Publish

The site first receives a provider hostname. That origin stays available while DNS is configured.

origin.pages.dev
02 · DNS

Route

A CNAME maps the friendly hostname to the provider. The authoritative DNS service publishes it.

www → origin.pages.dev
03 · CONTROL

Verify

The platform checks DNS to prove the customer controls the hostname and to prevent domain hijacking.

status: active
04 · TLS

Secure

The platform requests and renews a publicly trusted certificate, then serves the site over HTTPS.

certificate: valid