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

Can I prove somebody viewed a particular webpage?

A request for the exact page can show that a system sought it. Evidence that the page rendered and a person actually saw it requires additional device and activity context.

From request to human view

Server logs may record the path, timestamp, response status and transferred bytes. Browser history can record the URL and title. Cache entries, page-specific storage or screenshots can show that content reached the device.

A successful response does not guarantee display. The browser may close, block the content or fetch it in the background. Conversely, cached content may be viewed later without a fresh server request.

It is like delivering a letter: dispatch, arrival, opening and reading are related but separate events.

Scrolling, form submissions, clicks, downloads or dwell patterns may support engagement, though each requires careful interpretation. Searches leading to the page, repeated access and surrounding communications can provide human context.

Align timestamps across server, browser, account and device records, allowing for clock differences. Then establish who was using the device or account.

Report the strongest supported stage rather than converting technical delivery into certain human awareness.

The point to remember

Prove request, delivery, rendering, interaction and personal viewing as separate steps, using evidence appropriate to each.

Reference: WDH-082Websites, Domains & Internet Infrastructure