When your browser reads this blog, it looks up blog.exe.dev using DNS, and sends an HTTP request with a Host: blog.exe.dev header to our servers. Our anycast network receives the request and uses Host: blog.exe.dev to figure out which of all the exe VMs to proxy your request to. Load balancers, CDNs, web servers… the modern web works because of the humble Host header. (SSH does not have such a header, alas.)

exe.dev lets you bring your own custom domain to point to your VM. Thanks to Let’s Encrypt, we're able to provision the certificate on your behalf. And, now, we also let you provision a wildcard certificate, so you can have, for example, *.example.com all point to the same VM, and you can route accordingly. domain add vm-name *.example.com in our lobby is the place to get started, and it'll walk you through it.

An earlier version of this blog post falsely accused Certificate Transparency of delaying how quickly custom domains started working. This is no longer a problem! (DNS time-to-live configuration remains an occasional stumbling block, though.)