Skip to content
Skip to main content
Websites, Domains & Internet Infrastructure Technical Explainer

If I identify the server, have I identified the website operator?

No. A server is infrastructure. It may support several websites, customers and administrators, and its owner may have no involvement in the content.

Move from machine to service

First identify the particular website service on the server. Shared hosting may place many customers on one operating system. A virtual server may be rented to one customer but administered by a contractor. A platform may abstract the server entirely, while a compromised machine may host material without the customer’s knowledge.

Finding the server is like identifying the apartment block where an event occurred. The building owner, tenant, visitor and person responsible for the event remain separate questions.

Provider records may connect the server or virtual resource to a customer account, payment, assigned IP address and service period. Server data may include website configuration, virtual-host records, files, logs, user accounts and remote-access history.

Even an administrator login identifies a session and credential, not automatically the person using it. Match server events with platform activity, communications, devices and relevant provider records.

Be precise about time. Virtual resources can be rebuilt, IP addresses reassigned and websites moved. The machine identified today may not be the one serving the site during the relevant event.

The point to remember

Identifying the server locates a technical environment. Establish who controlled the relevant service and action at the relevant time.

Reference: WDH-045Websites, Domains & Internet Infrastructure