Download websites that use TeamCity

About TeamCity

Build servers are supposed to be unreachable from the open internet. A continuous integration system holds credentials, deployment keys, source code and the machinery that pushes changes to production, which is why it normally lives on an internal network behind a VPN. A fingerprint for one turning up in a public crawl is interesting for exactly that reason, whatever else the row does or does not tell you.

What our record holds for TeamCity is close to nothing. No vendor, no license, no category, no first year and no version data came through with the match, so the honest summary is that a pattern fired on a host and everything else about the product remains unrecorded on our side. Product names are shared more often than researchers expect, and a fingerprint confirms a pattern rather than a corporate identity, so a row of this kind is evidence that something answering to the pattern was served, not confirmation of a particular vendor's software.

As of October 2026 our detection count for TeamCity is 1. Small counts carry a specific kind of value, because whatever the true installed base of a developer tool may be, the part of it that answers on a public address is a different population, and often a more interesting one. A public match tends to mean a login page, a dashboard or an artifact endpoint that somebody left reachable. Security researchers doing external attack surface work want precisely that population, and it is not the population a popularity figure would describe.

Finding those hosts is the part a per-domain lookup cannot do. Checking a domain you already suspect confirms a suspicion and adds nothing else. The question worth paying for runs the other way, which domains anywhere in the crawl carry the pattern, and answering it means reading the index from the technology end. A downloadable list also gives a fixed set to work through and to compare against a later refresh, which is how a slow drift of exposed instances becomes visible.