Fetching response headers & auditing Cache-Control policy...
Likely Cacheable
HIT
1 hour
421 seconds
Googlebot Index Backup Snapshot
View Google's cached HTML backup snapshot of this page stored during Googlebot's last visit:
Open Google Cache Snapshot| Cache Layer | Reported Status / Evidence | Inspection Limitation Details |
|---|
| HTTP Header | Raw Value | Technical Meaning |
|---|
| Input URL | Policy Status | CDN Status | Observed Age | HTTP Status | Action |
|---|
Recent Audit History
HTTP Cache Control Architecture & Developer Reference
Cache-Control Directives
public: Response may be stored by browser and shared proxy/CDN caches.
private: Intended for a single user; shared CDNs should not cache.
no-cache: Must revalidate with origin server before using cached copy.
no-store: Prohibits storage in any cache layer.
CDN Edge Cache Status
Edge cache status headers (CF-Cache-Status, X-Cache) indicate whether a Cloudflare, Varnish, Fastly, or Nginx edge server served a HIT or MISS response.
SSRF Protection for Header Audits
Header audits validate host IP addresses before fetching, blocking requests to internal/loopback address blocks (127.0.0.1, localhost, 10.0.0.0/8, 169.254.169.254).
Remote Inspection Limitations
A server-side HTTP auditor cannot determine browser cache status or origin server-side memory cache status. Only header policies and CDN edge signals are determinable.