DEV Community

jeffrey
jeffrey

Posted on

Continuwuity: 350 Title Matches Around a Federated Matrix Homeserver

Continuwuity: 350 Title Matches Around a Federated Matrix Homeserver

Continuwuity is a Matrix homeserver, so its public footprint includes more than a web login. Federation endpoints, .well-known delegation, client APIs, and administrative commands describe different relationships. A title search can locate a candidate, but the trust boundary extends past the page.

The ZoomEye SDK probe on 22 November 2026 used sub_type=all, page 1, and pagesize=1. app="Continuwuity" returned 0 matches and title="Continuwuity" returned 350. The probes ran between 06:46 and 06:47 Asia/Shanghai.

The title result may include a deployment page, documentation, or a generic homeserver response. It does not prove that federation is enabled, that the server is reachable on port 8448, or that an administrator account is exposed. Those facts require separate checks.

Federation changes the perimeter

The deployment guide lists /.well-known/matrix/client and /.well-known/matrix/server when Continuwuity handles delegation. It also describes /.well-known/matrix/support. Federation traffic can use a different port or a delegated hostname, so an inventory that stops at the web root will miss the service that other homeservers use.

The configuration reference documents a federation switch and options that affect profiles and public room visibility. Disabling federation changes which remote servers can interact with local users. Allowing it means the homeserver must correctly validate remote events and enforce its own room and identity policy.

Continuwuity's changelog says admin escape commands received over federation are never executed. That is an important defensive property, but it does not remove the need to review admin commands, OAuth scopes, and local administrator identities.

Build a federated inventory record

For each owned homeserver, record the advertised server name, client base URL, federation base URL, .well-known responses, TLS certificate, supported federation version, and whether federation is enabled. Identify the software version without exposing admin tokens.

Keep administrative APIs and client administration separated from public federation traffic. Use a reverse proxy that normalizes paths and headers and rejects unexpected upstream routes. Review OAuth scopes for administrative clients, remove unused admin users, and monitor changes to server signing keys.

If the organization does not need federation, turn it off deliberately and test that the decision is reflected in discovery documents. If federation is required, document the room and user policy that justifies remote visibility.

Measurement limits

The 350 title matches are a candidate list for ownership confirmation. They are not a count of active federated homeservers and do not show whether one server trusts another. The review should follow the complete Matrix service boundary.

References

Top comments (0)