S03-TS: No
Rationale
The selected managed deployment depends on externally delegated service names and publicly allocated infrastructure addresses for coordination and relay access. Private overlay addresses do not make that complete deployment independent of allocation authorities.
Assessment method
Primary documentation, pinned source and explicit whole-stack inference
Source context
Tailscale bootstrap DNS, infrastructure requirements and RFC 4271
Outstanding qualification
Users need not obtain their own domain or public prefix. This evaluates the whole selected hosted composition; a privately operated alternative control plane is not selected.
Public sources
- https://tailscale.com/docs/reference/faq/firewall-ports
- https://raw.githubusercontent.com/tailscale/tailscale/566f89e0fb2aa4b2f1ebf98761e45e62aa5ef225/net/dnsfallback/dnsfallback.go
- https://tailscale.com/docs/reference/faq/firewall-ports
- https://www.rfc-editor.org/rfc/rfc4271.html#section-3.2
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round590.html
- round590-sources.json