HTTP caching for https://cachecheck.net/examples/expires-and-max-age

Overview

✅

This resource can be cached.

This response can be cached because of a directive in the Cache-Control header.

✅

This resource has a cache control header.

Cache-Control: max-age=3600
❌

This resource does not have an entity tag.

HTTP response cache headers

These are the raw caching-related HTTP headers that were returned by the server:
cache-control: max-age=3600
expires: Fri, 20 Feb 2026 22:26:14 GMT
🧭

Cache-Control

Cache-Control: max-age=3600
  • ⏳
    Max Age
    (RFC)

    The max-age directive indicates the response should be considered stale after 3600 seconds (1 hour).

    For example, since this response was fetched on Feb 20, 2026, 9:26:14 PM, it will become stale on Feb 20, 2026, 10:26:14 PM.

🗑️

Expires

⚠️ The Expires header is redundant with the max-age directive in the Cache-Control header, so the Expires header will be ignored.

The Expires header indicates the time at which the response will expire.

Expires: Fri, 20 Feb 2026 22:26:14 GMT

In this case, the response will expire on Feb 20, 2026, 10:26:14 PM (in about 1 hour).