HTTP Headers

Show the HTTP headers for a URL, with a full break-down of details. Will follow redirects.

Summary

Response
200
Total Requests
1
Total Time
407 ms

  • https://4-house.ru/elektrika

    Status
    200
    Message
    OK
    Time
    407 ms
  • IP
    45.12.5.198
    View Map

  • Timing

    Wait

    0 ms

    DNS

    5 ms

    TCP

    126 ms

    Request

    0 ms

    First Byte

    147 ms

    Download

    1 ms

    Total

    407 ms

  • HTTP Headers

    Server

    nginx/1.18.0

    A name for the server.

    • Server

      nginx

      Description of the server software.

    • Version

      1.18.0

      Version number.

    Date

    Sun, 16 Aug 2026 02:55:43 GMT

    The date and time that the message was sent.

    Content-Type

    text/html; charset=UTF-8

    The MIME type of this content.

    Problems were detected with this header

    • Unknown MIME type.
    Connection

    keep-alive

    Control options for the current connection and list of hop-by-hop response fields.

    keep-alive - The client would like to keep the connection open.

    Vary

    Accept-Encoding

    Indicates that different content may be provided to different clients, depending on the vary header.

    • Headers

      • Accept-Encoding
    Set-Cookie

    PHPSESSID=t21n3kqdsaq1sa914gmhsk5ltu; expires=Sun, 23-Aug-2026 02:55:43 GMT; Max-Age=604800; path=/; HttpOnly

    A cookie sent from the server to be set on the client

    • PHPSESSID

      t21n3kqdsaq1sa914gmhsk5ltu

      Cookie name and value.

    • Expires

      Sun, 23-Aug-2026 02:55:43 GMT

      When the cookie should expire.

    • Max-Age

      604800 (7 days)

      Number of seconds until the cookie expires.

    • Path

      /

      The client will only send the cookie when requesting this path, or subdirectories, from the server.

    • HttpOnly

      Prevents access to the cookie through JavaScript.

    Expires

    Thu, 19 Nov 1981 08:52:00 GMT

    The time at which the response is considered stale.

    Cache-Control

    no-store, no-cache, must-revalidate

    Inform all caching mechanisms from server to client whether they may cache this object.

    • no-store

      May not be stored by any cache.

    • no-cache

      May be stored by any cache but must be validated by the server.

    • must-revalidate

      Stale caches must not be used.

    Pragma

    no-cache

    HTTP/1.0 backwards compatible cache handling.

    no-cache - Force requests to the origin server before releasing a cache.

    X-Powered-By

    MODX Revolution

    The software powering this site.