Location
DNS configuration (external to repo, document findings in docs/), vercel.json
Problem
If this project uses any custom domain or subdomain pointing at Vercel (or any other third-party host) via a CNAME, and that record is ever left dangling (e.g. after removing a Vercel project or changing hosting providers) without removing the corresponding DNS entry, the subdomain becomes vulnerable to takeover by an unrelated party who claims the same hosting slug, a classic and easily-overlooked risk for projects with multiple environments (production, staging, docs).
Acceptance Criteria
Location
DNS configuration (external to repo, document findings in docs/), vercel.json
Problem
If this project uses any custom domain or subdomain pointing at Vercel (or any other third-party host) via a CNAME, and that record is ever left dangling (e.g. after removing a Vercel project or changing hosting providers) without removing the corresponding DNS entry, the subdomain becomes vulnerable to takeover by an unrelated party who claims the same hosting slug, a classic and easily-overlooked risk for projects with multiple environments (production, staging, docs).
Acceptance Criteria