DSTS connects with the Muon Noi ecosystem, but an external link should only be public when it does not send users into connection errors, SSL issues, origin failures, or 502 pages. If the destination domain is not stable, the responsible approach is an internal bridge.
An internal bridge is not a page that hides an error. It is a transparent surface that explains why users are not sent directly outside yet, what status is being verified, and where they can continue inside DSTS.
Do not let the homepage lead to a broken experience
The homepage is where newcomers place their first trust. If a CTA sends them to a broken external domain, they will not separate that domain's failure from DSTS. They will simply experience the system as unreliable.
A bridge needs status and next steps
A good bridge should state that the external domain is being verified, that DSTS does not collect data there, does not require login, does not open payment, and offers safe routes back to homepage, library, Movement, or manual contact.
External links should be checked like internal routes
A mature public site should not only smoke test internal routes. Important external links should also be monitored, especially when they are part of an ecosystem promise.