What Survives of Castle Hedingham's Old Village Website?

What an old village website actually is

A website that once lived at castlehedingham.org is distinct from the Internet Archive copy of it. The original domain was a separate thing, registered and run by someone, and it may now host something else, nothing, or a parked page. The Wayback Machine holds a capture taken on 4 December 2008, which you can open and inspect yourself at the 2008 archive lead for castlehedingham.org. This is a research lead, not a source of record until you have looked at what the capture actually shows. The capture date is fixed. The live domain is not, so a normal old URL typed today can behave very differently from the Wayback URL that includes a timestamp and snapshot ID.

Why a working old link is not a 2008 archive by default

A common mistake is to assume that any link containing castlehedingham.org must automatically open the 2008 page. It does not. A live URL and a Wayback URL have different hosts, different paths, and different behaviour. The live domain may redirect, time out, or serve unrelated content. Only the archive URL with the timestamp is tied to a specific snapshot. When you follow a citation, note whether the link goes to the original domain or to web.archive.org, and record that difference in your notes.

This matters because local history writing often recycles links. A document written years ago may still carry the old domain, and a reader clicking it today meets whatever the domain now does. The archive URL is the stable one. The live URL is the volatile one.

A compact comparison table

Question	Live old-domain URL	Wayback archive URL	Current official or academic source
What does the address point to?	Whatever the domain currently serves	A specific dated capture	A body that maintains the page
Is the destination stable?	No	Yes, within the archive	Usually, with revision dates
Can you read the original text?	Only if still hosted	Often, depending on the capture	Not applicable
Good for present opening times?	No	No	Only if the body publishes them
Good for place names and old phrasing?	Sometimes	Sometimes	Yes, if sourced
Who is accountable for content?	Often unclear	The archive preserves, it does not verify	Named publisher

How to read a capture without overclaiming

Open the archive lead and look at what is actually there. Note the capture date stamped by the Wayback Machine. Identify the site: was it a parish body, a society, a business, or an individual? The capture may show a header, a navigation bar, or a copyright line. Record only what you can see. Do not assume the snapshot is complete. Captures can miss images, stylesheets, linked pages, or internal files. A page that looks plain may simply have lost its formatting.

Treat every claim on the capture as a claim made at that time, not as a fact about today. A page describing a footpath, a hall, a service, or a building tells you what someone published then. It does not tell you about access rights, opening hours, or current ownership. If the capture mentions a local event, check whether the event recurs and who runs it now.

Worked research example, clearly hypothetical

Imagine you are writing a short note about a village walk. You find a citation in an old document to castlehedingham.org. You open the archive lead and see a capture from 4 December 2008. It lists a path name and a short description. That is a lead.

Step one: record the capture date and the original domain in your notes. Step two: check whether the path name appears on a current map or in a current rights-of-way record. Step three: look for a second source, such as a parish council notice or a county council path list. Step four: if the second source agrees on the name but not the description, cite the current source for the description and the capture only for the old phrasing. Step five: label the archive material clearly in your own text. If any step fails, keep the capture as a pointer and do not present it as evidence of present conditions.

This is a hypothetical example. It shows a method, not a finding.

Which anchors are concrete enough to use

The operator of Hedingham Castle dates the Norman keep to around 1140 and identifies Barnack stone in its construction, as set out on the Hedingham Castle history page. That is a specific claim from a named source with a stated subject. Use it near a sentence about the keep, and attribute it.

The Dartmouth Occom Circle placeography documents Samson Occom preaching at Castle Hedingham in 1767, as recorded in the Occom Circle placeography entry for Castle Hedingham. That is a scholarly source with a date, a person, and a place. Use it near a sentence about Occom, and attribute it. These two anchors are enough for the historical frame. The rest of your work is method.

Do not treat modern sources as automatically correct

A modern page is not correct just because it is recent. Identify the publisher, the date, the topic, and whether another source corroborates it. A council page, an estate page, and an academic database each have different scope. A council page may be accurate about notices and silent about medieval building. An estate page may be accurate about its own site and silent about parish matters. An academic database may be accurate about a document and silent about present access. Compare them where they overlap, and note where they do not.

A practical checklist for readers

1. Record the original domain and the capture date separately.
2. Distinguish a live old-domain URL from a Wayback URL with a timestamp.
3. Open the archive lead and describe only what you can see.
4. Note whether the capture looks complete or partial.
5. Check time-sensitive claims against a current named source.
6. Use the two anchors above only for the claims they support.
7. Label archived material clearly in your own notes and drafts.

For related background, see Why is the village called Castle Hedingham?, Who preached at Castle Hedingham in 1767?, and Barnack stone and the Norman keep. Each page covers one strand. Together they show how to separate a lead from a fact.