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

What does controlling a website actually mean?

Website control is not one permission. It can mean control of the domain, DNS, hosting, platform, content, user accounts, business activity or payments.

Define the specific capability

A registrar-account user may redirect the domain without accessing the website files. A server administrator may maintain infrastructure without choosing the content. An editor may publish articles without controlling billing. A business owner may receive proceeds while technical work is delegated.

Think of a theatre: one person owns the building, another controls the lighting, another sells tickets and actors control what happens on stage. Saying one person “controlled the theatre” hides the act that actually matters.

Permissions show what an account was allowed to do. Logs and change histories may show what it did at a particular time. Payment, communication and device evidence can help identify the person behind that session.

Ask the narrow question: who could change this DNS record, upload this file, create this user, publish this page or receive this payment? Then identify the record created when that action occurred.

Do not treat job title, business ownership or account registration as proof of personal use. Shared access, delegation and compromise should be considered where supported by the circumstances.

The point to remember

Replace the vague claim that someone “controlled the website” with the precise capability, action, account, person and time supported by the evidence.

Reference: WDH-036Websites, Domains & Internet Infrastructure