Site inspiration & templates / Experimental website archive
Brutalist Websites
Explore expressive, unconventional web composition.
Understand the resource
What it is.
Brutalist Websites documents sites that deliberately challenge polished, comfortable web conventions. It can broaden visual options for cultural or experimental work, while essential tasks still need to remain understandable.
When it is useful
The project’s identity calls for a raw or unconventional expression.
A proposed application
Put it to work.
This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.
Try this
Explore a typographic direction for a cultural event while keeping tickets, dates and navigation easy to find.
Result to aim for
An expressive visual proposal with protected task clarity.
Before you start
What you need.
- An appropriate brand context and explicit usability constraints.
The practical boundaries
What to watch for.
- Aesthetic difficulty is not a reason to remove keyboard access, legibility or familiar recovery paths.
- Archived references may have changed, and their visual assets remain their owners’ work.
Review record
What we could establish.
- Public primary documentation reviewed. See the account-free evaluation for executed checks and remaining workflow limits.
The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.
Check current access, terms, licensing and data handling before using a resource with your own material.
Runtime and security evaluation
What the evaluation covers.
The American Millennial interview opened with its image and editorial content. The observed link used HTTP but the final browser document was HTTPS.
Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.
- Target
- https://brutalistwebsites.com/
- Version or capture
- Unversioned public page observed on 2026-10-19
- Integrity scope
- sha256:13834a1aea8164dfcd9b6d5046873d4e54e4c79b06d9f7659ea676078b92a129 — initial HTTP 200 response body only; not whole-application integrity.
Test conditions
- Chromium 155.0.8059.82, 1365×900 desktop viewport.
- Separate fresh, ephemeral browser contexts for entry and interaction; no owner profile, credentials or stored session.
- Only GET/HEAD network requests allowed; forms, downloads, WebSockets and service workers blocked. Some analytics endpoints also blocked.
- Short bounded waits; no mobile, assistive-technology, cross-browser or performance certification.
Individual checks and observations
Public HTTP response
passPublic HTTP response: Anonymous GET with redirects followed, response-body SHA-256 and selected security-header summaries; no cookies retained.
Observed: The standalone client received 200 at https://brutalistwebsites.com/. This establishes response delivery only.
Fresh browser entry
passPublic browser sample: Open the catalog URL in a new anonymous Chromium context with read-only network guards and no inherited profile.
Observed: The document returned 200 and identified itself as “Brutalist Websites”. 1599 image elements were present; no account was used.
Observed public sample or navigation
passPublic browser sample: Follow the observed Interview link to http://brutalistwebsites.com/americanmillenni.al.
Observed: The destination returned 200; title: “Brutalist Websites – American Millennial”. 1 page image elements had decoded during the bounded wait. This count is not a catalog size or performance benchmark.
Security findings and boundaries
Passive inspection of the initial public document’s response headers and anonymous browser request hostnames, with read-only guards. No source exploitation, account access, dependency audit or private data.
Observed · info
Public response protections
The initial browser page used HTTPS. No HSTS response header was observed. No enforcing Content-Security-Policy response header was observed. This records the sampled response only; meta policies, backend authorization and exploit resistance were not assessed.
Observed · info
Observed host boundary
The initial Brutalist Websites browser visit attempted requests only to brutalistwebsites.com. This does not cover later features, server-side processing or a complete session.
Practical advice · caution
Before using this reference
Keep the HTTPS address and check individual archive destinations before relying on them. Experimental visual style does not remove readability and recovery requirements.
Observed · caution
HTTP archive link
The selected Interview anchor used http://brutalistwebsites.com/americanmillenni.al, while its final document loaded over HTTPS. Prefer the HTTPS destination; this one upgrade does not establish the transport behavior of every archive link.
Practical caveats
- Keep the HTTPS address and check individual archive destinations before relying on them. Experimental visual style does not remove readability and recovery requirements.
- Aesthetic difficulty is not a reason to remove keyboard access, legibility or familiar recovery paths.
What remains untested
- The external featured website was not opened; archived links, accessibility, historical availability and any submission workflow were not audited.
- Results describe the observed public pages and a bounded action, not the entire product or the referenced designs.
Security limits
- No authentication, authorization, tenant separation, data retention or backend handling was tested.
- Header presence or absence is a sampled configuration observation, not a security certification or an exploit finding.
- 0 blocked-request records were retained across entry and interaction checks. Guards may alter normal page behavior; the logs do not represent unrestricted traffic.
Evaluation sources
Follow the evidence
Sources and further reading.
Keep exploring