How you got here

Most people reach this page one of three ways: a link from an internal doc, a leftover bookmark, or curiosity about a hostname that turned up in DNS or in a report. Whichever it was, here is the full path your request took.

The request path

1. Your resolver asked for dev.cleardmarc.com

   The name is delegated to its own Route 53 hosted zone, separate from the parent cleardmarc.com zone, so dev records can change without touching production DNS.

2. Route 53 answered with an alias record

   An A record aliased to a CloudFront distribution rather than a fixed IP, so the address follows the CDN and costs nothing to resolve.

3. Your browser opened TLS to the nearest CloudFront edge

   The certificate is issued by AWS Certificate Manager in us-east-1, which is the only region CloudFront reads certificates from.

4. CloudFront looked for the object in its cache

   On a miss it fetched from a private S3 bucket in ap-south-1 (Mumbai) over an Origin Access Control signature. The bucket itself blocks all public access - it is not reachable directly.

5. S3 returned this HTML and the edge cached it

   Plain static files. No server, no database, no application runtime anywhere in the path.

The same thing as a diagram

you
 |  https://dev.cleardmarc.com
 v
Route 53  (hosted zone: dev.cleardmarc.com)
 |  A / AAAA alias
 v
CloudFront  (TLS terminates here, ACM cert from us-east-1)
 |  signed origin request, OAC
 v
S3 bucket  (ap-south-1 Mumbai, private, static files only)

If you were looking for something else