Well, why not? It's a great host with a whole bunch of features you'd have to invent yourself otherwise like feature branch previews. It's a static site/documentation site afterall.
former netlify employee here. all sites on netlify have a netlify subdomain, that doesnt go away when you add a custom domain. its just useful for deploy previews and stuff, content is basically the same. nothing untoward here
I think we're misunderstanding each other. I'd expect an official UK government site hosted on netlify to have a custom .gov.uk domain and to use that to refer to the site. Same as most large commercial enterprises probably do, right? Instead of using the netlify subdomain as the public host.
