How to Capture a Dynamic Website With Forensic Accuracy

Why dynamic pages break the usual screenshot

A modern web page is rarely a fixed document. Content is assembled by JavaScript after the page loads, sections appear only when you scroll, prices and banners depend on the visitor's country, consent choice or test group, and a cookie banner may cover the very claim you need. Two people opening the same URL in the same minute can see different pages.

For a compliance record this matters twice. A screenshot shows one rendering and nothing about how it was produced, so it is easy to dispute. And if the record does not say which version of the page it shows, you cannot show that it is the version a customer, an investor or a regulator saw.

Client-side rendering: the HTML delivered first is almost empty and scripts build the content, as in single-page applications.
Lazy loading and infinite scroll: images, reviews or disclaimers load only when they come into view.
Consent and overlays: cookie walls, age gates, chat widgets and sticky banners hide parts of the page.
Variants: A/B tests, personalisation, geo-targeting and logged-in states serve different content to different visitors.
Time-limited content: countdown offers, flash prices and rotating banners change by the hour.

What regulators expect you to be able to show later

Several rules put the burden of proof on the business that published the content. None of them prescribes a capture tool, but all of them assume you can later show what was actually published.

UK financial promotions: under FCA COBS 4.11.1R a firm must make an adequate record of each financial promotion it communicates or approves and keep it, for example five years for MiFID business, three years in other cases and indefinitely for pension transfers.
UK advertising: CAP Code rule 3.7 requires marketers to hold documentary evidence for objective claims before an ad is published; the ASA may treat unsupported claims as misleading.
EU unfair commercial practices: Article 12 of Directive 2005/29/EC lets courts and authorities require a trader to prove the accuracy of factual claims and treat them as inaccurate if the evidence is missing or insufficient.
EU price reductions: Article 6a of Directive 98/6/EC, inserted by Directive (EU) 2019/2161, requires the prior price shown with a discount to be the lowest price applied in a period of at least 30 days before the reduction.

This is not legal advice for your situation; national rules and sector regulators add their own requirements. The common thread is simple: if you cannot reproduce the page as it was, the risk sits with you.

What forensic accuracy means for a web page

Forensic accuracy is not a prettier screenshot. It is a record that shows what the page delivered, how it was captured and that nothing has changed since. ISO/IEC 27037 and the Council of Europe Guidelines on electronic evidence both stress integrity, metadata and documentation of how evidence was collected; our methodology is designed with reference to ISO/IEC 27037. In practice, a defensible record of a dynamic page contains:

The rendered page as a full-page screenshot, plus a video of the page loading.
The page source: raw HTML and an MHTML snapshot of what the browser actually received.
A network log (HAR) of every request and response, with cookie values and authorisation headers masked.
Server context: the TLS certificate chain, DNS answers from several resolvers and domain registration data.
The capture conditions: time, viewport, consent choices made and any visual interventions, such as a hidden sticky banner.
A SHA-256 hash of every artifact, bound into a qualified electronic timestamp so that any later change is detectable.

Step by step: capturing a dynamic page

Define the version you need: country, language, device, logged in or not, and the moment that matters, such as a launch, a complaint or a price change.
Start from a clean state so that earlier cookies or a previous test assignment do not decide what you see, and note it.
Decide how to handle the consent banner and record the choice; refusing may hide some content, accepting may change the page.
Make sure the relevant parts are loaded: scroll to the footer, open the accordions with risk warnings or terms, wait for prices and reviews.
Capture, then check the result: are the claim, the disclaimer and the price legible in the screenshot and present in the HTML?
Write a short capture note: who, when, why and which version. If the record is ever challenged, it becomes your statement.

Then verify the package independently before you rely on it, for example offline with the open-source gpa-verify tool, which checks the hashes and the qualified timestamp without trusting us.

Choose the capture method by page type

No single method fits every page. GetProofAnchor offers four, and the honest choice depends on what the page does:

Public marketing, pricing and terms pages: server capture by URL. Our infrastructure retrieves the page, handles cookie walls with a logged rules layer (the strict profile uses no AI) and records every intervention in the sealed metadata.
Single-page applications and pages behind a login: the browser extension. It captures the page in your own browser and the server seals it on receipt, so the timestamp proves the time of receipt and integrity, not independent observation. Server capture refuses login-walled pages and SPAs and points you to the extension.
Multi-step journeys such as product page, configurator, checkout and confirmation, and videos: Forensic Browser, a Windows desktop app that puts a whole session into one sealed package with one qualified timestamp, as a PDF that validates in Adobe Acrobat Reader or as a ZIP. From 290 EUR a year excl. VAT (350.90 EUR incl. VAT).
No time or no staff: Assisted Capture. An operator captures the URLs for you; Rush covers up to 5 URLs within a guaranteed 60 minutes for 249 EUR excl. VAT (301.29 EUR incl. VAT).

From one capture to an evidence series: scheduled monitoring

A single capture proves one moment. Compliance questions are usually about periods: was the risk warning there all quarter, when did the price change, how long did the claim stay online. Website Monitoring captures a public page daily or weekly at a time you choose. Every check is a full sealed proof with a qualified eIDAS timestamp, and you get an e-mail when the content differs from the previous run.

Business, 99 EUR a month excl. VAT (119.79 EUR incl. VAT): 10 monitors, 400 proofs per 30 days, 10 users.
Monitoring 50, 399 EUR a month excl. VAT (482.79 EUR incl. VAT): 50 monitors, 1,800 proofs per 30 days.
Monitoring 100, 599 EUR a month excl. VAT (724.79 EUR incl. VAT): 100 monitors, 3,500 proofs per 30 days.
Each check uses one proof: a daily monitor needs about 30 proofs a month, a weekly one about 4 to 5.

Limits worth knowing: monitoring works on publicly accessible pages only, sites with hard bot protection can block it, and nothing is recorded between two runs, so a change that appears and disappears within a day can be missed. For a page behind a login, use the extension one capture at a time.

What the timestamp proves, and what it does not

Under Article 41(2) of the eIDAS Regulation a qualified electronic timestamp enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data it is bound to, and Article 41(3) requires it to be recognised as a qualified timestamp in all EU member states. For your record this means: the artifacts existed in exactly this form at the sealed time and have not changed since.

It does not mean that every visitor saw the same page, that the content is true or that a court or regulator must accept the record. That is why the capture conditions and your note matter as much as the seal. No tool can guarantee how evidence is weighed; a documented, sealed and independently verifiable record is simply much harder to dismiss than a screenshot.

A practical setup for a compliance team

List the pages that carry regulated content: financial promotions, product claims, prices and discounts, terms, privacy notices, sponsorship or AI labels.
Set a frequency per page: weekly for stable pages, daily during campaigns, plus a manual capture at every launch and every change.
Name an owner and write the version rules once (country, device, consent choice) so that captures stay comparable.
Match retention to the strictest rule that applies to you and keep the evidence ZIP files, not only the reports.
Group proofs by campaign, product or client with Cases and export a whole case as one ZIP for an audit or a dispute.
Run a test verification with gpa-verify once a quarter, so you know the records will check out when someone asks.

FAQ

Is a screenshot enough as a record of a financial promotion?

The FCA rule asks for an adequate record and does not prescribe a format. A screenshot shows one rendering but not the source text, hidden disclaimers or how and when it was taken. A sealed capture with HTML, network log and capture metadata is easier to rely on. Ask your compliance adviser what your regulator expects.

How do I capture a page that looks different in another country?

Decide which variant you need, capture it under those conditions, for example with Forensic Browser on a computer in that market, and say so in your capture note. A server capture shows what the page served to our capture infrastructure.

Why does the server capture refuse some single-page applications?

Some applications only render reliably in a real user session. Rather than seal an incomplete page, the server capture refuses them and recommends the browser extension, which captures what your own browser rendered and seals it on receipt.

Does monitoring catch every change?

No. It captures on a schedule, daily or weekly, and changes that appear and disappear between two runs are not recorded. For known events such as a launch or a price change, add a manual capture at that moment.

Can I see a sample before buying?

Yes. Write to sales@getproofanchor.com with a public URL you need to keep a record of and we capture it as a free sample so you can inspect the evidence package. The smallest paid option is the 9 EUR pack with 3 proofs (10.89 EUR incl. VAT).

Sources

For compliance and audit teams

Prove what was published — and when it changed

Scheduled forensic captures of policies, prices, disclosures and competitor claims. Every run is a sealed proof with an eIDAS qualified timestamp, building an unbroken evidence series.

Solutions for compliance Set up website monitoring

See plans and pricing →

Related guides

Keep a record of your pages that holds up

Capture a dynamic page once, or put it under scheduled monitoring. Every capture is a full evidence package sealed with an eIDAS qualified timestamp.

Create a proof Verify a proof

Business from 99 EUR/month excl. VAT, Monitoring 50 and 100 from 399 EUR/month, 9 EUR pack (10.89 EUR incl. VAT). No guarantee of how a court or regulator weighs evidence.

How to capture a dynamic website with forensic accuracy for compliance