For decades, almost every college with a Unix server handed students and staff a homepage. Somewhere under a people. or users. subdomain sat a ~username directory that could hold anything publishable: a résumé, lecture notes, a lab’s working papers, a thesis in progress, a Web ring for a hobby. Blogs and small projects grew there because the hosting was free and the address looked respectable, which is why other pages linked to them and course lists cited them. The university paid for the bandwidth. The account holder treated the space as theirs. Neither side treated it as permanent, and that mismatch eventually shows up as a dead link.
The arrangement only worked while the affiliation lasted.
When the account expires
University accounts are scoped to enrollment or employment. When the affiliation ends, so can the web account. Dartmouth’s policy for expiring website accounts is unusually explicit: sites on its host service expire 60 days after the owner leaves unless they are transferred elsewhere or reassigned to a current Dartmouth member.
A documented shutdown shows what this looks like. In June 2024, Missouri State University announced that personal and course websites on people.missouristate.edu and courses.missouristate.edu would be discontinued on October 1, 2024. Sites and files left on the servers would be deleted; the announcement said no action was needed from anyone who no longer used a site, only that it would disappear. It pointed account holders at commercial hosts like GoDaddy and Bluehost, and Web Strategy noted it could not help anyone move a site it did not build. Course material was steered to the university’s learning-management system; official pages moved to its content platform. The personal pages had no landing spot. Today the old URLs return 404. Years of faculty lab pages, class notes, and student projects have vanished from the university’s own servers.
What survives and what does not
Recovery is partial and accidental. The Internet Archive still serves copies of some Missouri State pages captured by routine crawling years before the shutdown; a 2015 capture of one faculty research page is still readable today. But the Wayback Machine holds only what someone happened to crawl, frozen at the moment of capture. Unlinked pages, recent changes, and sites nobody indexed are absent. Whole sets of files — especially the PDFs and images such pages accumulated — survive only if a crawler happened to reach them. An archive copy is a snapshot, not a way to restore the account.
A few schools offer a real exit instead. Dartmouth lets departing account holders transfer a site to Reclaim Hosting or hand ownership to a current student, staff member, or faculty member. Its WordPress documentation also warns users to export while their NetID is still active, because the standard export does not contain every theme, plugin, or image file. These options share a condition: the account holder has to act before institutional access disappears. The default everywhere is deletion.
A personal page on a university account is rented space, not ownership. It sits on servers the author does not control, tied to a status the author does not keep. When the status lapses, the page lapses with it. Nobody has to decide to erase this part of web history; it is an operational consequence. The record of what the internet forgot grows one expired account at a time.