The notes are original operational summaries. This page lists the core static-site references used for protocol details, server behavior, and command examples. Broader topics in the Posts section cite their own references. The links are the authority; the summaries on this site are not substitutes for reading the relevant specification.
Individual notes record dates for their source checks. Those dates describe the recorded check, not a guarantee of current reachability or of every claim in an article. A successful link request alone does not establish that the source supports a conclusion, and an upstream document can change after it was consulted.
HTTP and discovery#
| Reference | Used for |
|---|
| RFC 9110 — HTTP Semantics | Status codes, validators, conditional requests, and redirect semantics. |
| RFC 9111 — HTTP Caching | Freshness, revalidation, Cache-Control, Age, and Vary. |
| RFC 7538 — 308 Permanent Redirect | Historical 308 definition; RFC 9110 section 15.4.9 is the current reference. |
| RFC 9309 — Robots Exclusion Protocol | The /robots.txt file, parsing, and crawler scope. |
| RFC 1034 — Domain Names: Concepts and Facilities | DNS caching and resolver behavior. |
| RFC 1035 — Domain Names: Implementation and Specification | Record formats and TTL fields. |
| RFC 2308 — Negative Caching of DNS Queries | Cached negative answers and their lifetime. |
| Sitemaps Protocol | XML encoding, host scope, and sitemap size limits. |
MDN: Cache-Control | Practical examples and browser-facing terminology. |
| MDN: Content Security Policy | Resource policies and deployment guidance. |
MDN: Strict-Transport-Security | HTTPS-only browser policy and deployment cautions. |
MDN: Content-Type | Media types and character-set metadata. |
MDN: X-Content-Type-Options | nosniff behavior for script and style destinations. |
| curl manual | HEAD, Range, header, redirect, and transport inspection commands. |
Release and recovery#
Servers and operations#
Web security#
The site does not claim affiliation with any of these projects. Their names and documents remain the property of their respective authors and maintainers.