Service Domains

Here is a list of all domain names used by StarCat Systems and its projects and services.

This list helps to ensure that you're only dealing with official, legitimate StarCat services. If you come across a site with a domain name that is not on this list, that is claiming to be part of StarCat Systems, do not provide any personal or login information, and please contact Security immediately.

• starcat.systems - the StarCat Systems homepage. Also hosts certain sites and services on its subdomains (like this site!)
• wiki.starcat.systems - the site that you're on right now! Our wiki and documentation site for all things StarCat.
• id.starcat.systems - the StarCat ID site. Use your StarCat ID to log in to all other StarCat Services.
  • This is the only site that you should enter your StarCat ID login information or 2FA information into. All StarCat sites and services will redirect to id.starcat.systems for you to log in.
• git.starcat.systems - the StarCat Git server, powered by Forgejo.
• policies.starcat.systems - a quick link that redirects to the Policies section of this site.
• support.starcat.systems - a quick link that redirects to the Support section of this site.
• status.starcat.systems - a quick link that redirects to our InStatus offsite status page (below).
• *.starcatsys.net - a backend domain used to host “under the hood” apps and services. It is unlikely that you would come across this domain.
• starcatsys.instatus.com - hosts our off-site system status page. Sign up here to receive notifications if we're having issues with any of our systems.

• source.camp - the homepage for SourceCamp
• docshub.io - the homepage for DocsHub
• postline.email - the homepage for Postline
• stagelink.cloud - the homepage for StageLink
• openho.st - the homepage for OpenHost

• *.starcathosted.com (e.g., example.starcathosted.com)
• *.hosted.source.camp (e.g., example.hosted.source.camp)
  • These subdomains host users' Forgejo instances. If you are an owner or user of one of these instances, you should use your Forgejo login information to sign in to Forgejo. Do not use your StarCat ID login information.
• *.hosted.docshub.io (e.g., example.hosted.docshub.io)
  • If your DocsHQ site is set to require authentication, you will be redirected to auth.example.hosted.docshub.io to log in with your company credentials. Do not use your StarCat ID login information.
• lists.postline.email
  • When you create or subscribe to a PostLine list, you will be prompted to create a separate PostLine login which will only work with PostLine lists. Do not use your StarCat ID login information.
• *.dedicated.postline.email (e.g., example.dedicated.postline.email)
  • For PostLine Dedicated servers, you will be prompted to create a separate login for your dedicated server, which you will use to administer the server, manage and/or subscribe to lists, etc. Do not use your StarCat ID login information.
• *.connect.stagelink.cloud (e.g., example.connect.stagelink.cloud)
  • Depending on how your StageLink tenant is set up, users connecting to your StageLink Outpost will either log in with their own StarCat ID (via id.starcat.systems), or will log in using your company's SSO integration.
• *.openhosted.net (e.g., example.openhosted.net)
  • Services hosted by OpenHost will prompt you to set up a unique login using the service's authentication system the first time you set up the service. This login information is isolated to your service, and does not interact with your StarCat ID login information whatsoever.