Infrastructure & Hosting

Analyst Toolkit

Whose servers, whose network, and where.

The physical and corporate reality behind the traffic. Every domain, host, address, provider and certificate an application touched, resolved to who operates it, where it sits, and whether the machine that answered is the one you thought you were talking to. It is where a list of server names becomes a list of companies you have a relationship with, whether you intended to or not.

Two questions run through every report here. Who is actually behind each thing the application loaded, and how much of the application depends on any one of them. The first turns technical measurement into due diligence. The second is where concentration shows up: a supply chain that sits mostly on one provider, or behind one delivery network, has a single point of failure whether or not anyone has abused it yet.

SCVue hostname matrix, listing every hostname observed in a capture alongside the infrastructure and providers serving it.
The hostname matrix: not only who the application talked to, but what it received from each of them.

Integrated Reports

Domains

Every domain the application contacted, ranked by how many calls went to each. The simplest answer to who this site talks to and how much, and the natural starting point for the section.

Domain Ownership

Who actually controls each domain, with the owning entity and links to its privacy policy and terms. Every field is editable, so your own research, a contract, a subsidiary relationship, a registry lookup, becomes part of the record and is reused across every application that touches the same domain. This is the bridge between technical measurement and business due diligence.

Domain Map

The same domains as a picture, each area sized by the traffic it carries. Where the Domains report gives you the numbers, this shows you the proportions, and concentration, sprawl, or unexpected weight in one corner is visible at a glance.

Hostnames

A matrix of hostname against content type. A more precise question than the domain view: not just who did we talk to, but what did we get from each of them. A host serving both images and executable code is a different proposition from one serving only fonts.

IP Addresses

Traffic grouped by the server that actually answered, with its provider, network operator and location. Where the domain reports tell you who you think you are talking to, this tells you which machine replied. Those can differ, and the difference matters.

Internet Service Providers

The network operators carrying the traffic, plotted on a world map with the hosting jurisdictions involved. For any question that begins with which countries our data passes through, this is the report that answers it, and the map is the artefact that goes into the report you hand upward.

Cloud Providers & Services

Which cloud platforms host the infrastructure behind the application, by provider and by service, with the share of traffic each carries. Ninety percent of a supply chain on one provider is a resilience finding as much as a security one.

CDNs

Content delivery networks with each provider's traffic share and the hostnames it serves. They earn their own report because a delivery network can see and modify everything it delivers, and one compromise has historically affected thousands of sites at once.

SSL Certificates & Providers

Whether each host encrypted its traffic, fell back to plain connections, or instructs browsers to always use encryption, with how many calls were made in the clear and full certificate detail behind each host. Unencrypted traffic in a supply chain is one of the few findings that is unambiguous. This report finds it and quantifies it.

One capture is enough to start

Capture a session in the browser, import it, and read what comes back. A free community account is available immediately.