Direct answer: The 25 homepages were checked again after about 48 hours (2026-11-05 12:41–12:43). Compared with the 01:40 snapshot, all six policy fields in both header sets show zero changes. Since 2026-11-03 the only cumulative changes remain two: E28 added X-Frame-Options: DENY and E24 added Vary: Accept-Encoding; both persist.

HSTS 5, CSP 11, anti-framing 15, nosniff 6, Referrer 4, Permissions 1 and version disclosure 6 are unchanged; cache policy distribution, ETag 4, Last-Modified 4, Vary 23, gzip 23, Brotli 1 and no compression 1 are unchanged too. The only non-policy difference is E20 moving from chunked to Content-Length (25 pages either way), a transport shift.

25
sites rechecked
0
new policy changes
2
cumulative changes
15
anti-framing
23
Vary
6
none of six

Method: a third snapshot

The study uses the 25 usable homepages from study 48 and their final hosts. On 2026-11-05 between 12:41 and 12:43 it requests each site twice, serially with at least 0.8 s between: security headers without Accept-Encoding, cache headers with gzip, deflate, br; only headers and at most 1 KB are read. All 25 sites returned 200 in both passes.

SnapshotSecurityCacheInterval
Baseline11-03 11:4111-03 12:40—
Study 5511-05 01:4011-05 01:40About 38/37 h
This study11-05 12:4111-05 12:41About 49/48 h

Security: three snapshots

ItemBaseline38 h48 h
HSTS555
CSP111111
Anti-framing141515
nosniff666
Referrer-Policy444
Permissions-Policy111
Version disclosure666
Still HTTP444
ScoreBaseline38 h48 h
0766
1677
2777
4444
5111
6000

Cache and compression: three snapshots

ItemBaseline38 h48 h
No Cache-Control888
no-store888
private / no-cache888
Positive max-age111
ETag444
Last-Modified444
Vary: Accept-Encoding222323
gzip / br / none23 / 1 / 123 / 1 / 123 / 1 / 1

Change list: nothing new

SiteChangeStatus
E28Added X-Frame-Options: DENYAppeared at 38 h, persists at 48 h
E24Added Vary: Accept-EncodingAppeared at 38 h, persists at 48 h
E20chunked → Content-LengthTransport change, not a policy field
Other 22No policy change in either set—

E20's chunked/Content-Length shift does not change cache policy or encoding; the 25 pages still use one transport each (15 chunked, 10 Content-Length in this snapshot).

What this means for acceptance

  1. Policy is stable for 48 hours. No policy field changed between the 38-hour and 48-hour snapshots.
  2. The E28 and E24 fixes persist. The new XFO and Vary did not revert; they look like settled single-site fixes.
  3. Backlog does not disappear by itself. Six sites score 0, four are HTTP, eight lack Cache-Control, and only one has a positive max-age.
  4. Transport can fluctuate. E20 moved between chunked and Content-Length and should not count as a policy change.
  5. 48-hour stability is not permanence. One recheck cannot infer long-term behaviour or the industry.

Limits

  • About 49/48 hours: not the same instant, so not a precise rate.
  • Single snapshot: CDNs and WAFs may vary by region, time or UA.
  • Headers only: cache hits, compressed size and browser behaviour are not tested.
  • Policy field scope: eight security and six cache fields are compared; chunked/Content-Length are separate.
  • 25-site pilot: no industry claim.

Data and reproduction

Anonymised data: equipment-security-headers-recheck48-2026.csv (25 rows, three snapshots) and equipment-cache-compression-recheck48-2026.csv (25 rows, three snapshots). The repository keeps both under docs/research/2026-11-*-recheck48.csv.

Evaluation and comparison: security_headers_probe.py (10 tests), cache_compression_probe.py (10), header_recheck.py (6). Run:

python -m unittest scripts.test_security_headers_probe scripts.test_cache_compression_probe scripts.test_header_recheck

Related: the 38-hour header recheck, the homepage security header pilot, and the homepage cache and compression pilot.

Sources and definitions

  1. Sites: the 25 usable homepages from study 48.
  2. Fetch: 2026-11-05 12:41–12:43, serial, ≥0.8 s apart; both passes returned 25/25 200.
  3. Comparison: eight security and six cache policy fields; chunked/Content-Length listed separately.
  4. Timing: about 49 hours for security, 48 for cache.
About the author

Lingyi Information Official (delivery team) works on requirements, proposals and acceptance for corporate websites, brand and smart-manufacturing projects. This article compares literal header values across three snapshots only; it does not infer long-term behaviour and is not a final judgement of any site's security, performance or compliance; the 25-site sample is a pilot.

No new changes between the two rechecks

Policy fields from 38 to 48 hours are unchanged; the E28 and E24 fixes did not revert.

Request a recheck plan