System architecture, protocols, data formats, and interface standards for the 1990 Web Archive infrastructure.
Distributed edge nodes located in 14 regions worldwide ensure low-latency access to archived content. Traffic is routed via anycast DNS.
All archival data is stored in append-only WARC containers with cryptographic hashing. Erasure coding provides 99.99999999% durability.
Elasticsearch-based indexing of metadata, text content, and URL structures. Supports era-specific query filters.
| Format | Specification | Support Level | Notes |
|---|---|---|---|
| WARC 1.1 | RFC 8493 | Standard | Primary archival format with WARC-GZ compression. |
| WARC-PROX | IETF Draft | Beta | Proxy capture for dynamic content reconstruction. |
| ARC | Archive-It | Legacy | Read-only support for migration from legacy systems. |
| HTML 2.0/3.2 | IETF / W3C | Standard | Native rendering support for early HTML standards. |
| Gopher / WAIS | Pre-Web Protocols | Standard | Protocol emulation and content conversion. |
Our proprietary Spectacle Rendering Engine emulates the behavior of early browsers to ensure pixel-perfect reproduction of 90s webpages, including quirks, layout bugs, and deprecated features.
Supports emulation profiles for:
Handles era-specific rendering:
| Endpoint | Method | Description | Rate Limit |
|---|---|---|---|
| /v1/search | GET | Query the archive index by URL, date, or metadata. | 100 req/min |
| /v1/snapshots | GET | Retrieve WARC or rendered HTML for a specific point in time. | 50 req/min |
| /v1/crawl/submit | POST | Submit a URL for immediate archival crawling. | 10 req/min |
| /v1/render/image | GET | Generate a screenshot of an archived page using Spectacle Core. | 20 req/min |
Every WARC record includes SHA-256 block digests. Archive integrity is verified via periodic deep-scan audits against root hashes stored on an immutable ledger.
All submissions are timestamped using RFC 3161 compliant TSA servers, providing non-repudiable proof of content existence at a specific epoch.
RBAC (Role-Based Access Control) for internal operators. Public API enforces API key rotation and IP allowlisting for enterprise tiers.
Meets OAIS Reference Model requirements. Compatible with LOCKSS, CASRA, and TRAC standards for digital preservation.