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
1010 ms

  • https://glk-egoza.ru/user/steelspike21/

    Status
    200
    Message
    OK
    Time
    1010 ms
  • IP
    5.45.123.60
    View Map

  • Timing

    Wait

    0 ms

    DNS

    569 ms

    TCP

    105 ms

    Request

    0 ms

    First Byte

    122 ms

    Download

    0 ms

    Total

    1010 ms

  • HTTP Headers

    Server

    nginx

    A name for the server.

    nginx - Description of the server software.

    Date

    Fri, 09 May 2025 16:30:49 GMT

    The date and time that the message was sent.

    Content-Type

    text/html; charset=UTF-8

    The MIME type of this content.

    • Type

      text/html

    • Description

      HTML file

    • Charset

      UTF-8

    Connection

    close

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

    close - The client or server would like to close the connection.

    Vary

    Accept-Encoding

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

    • Headers

      • Accept-Encoding
    Set-Cookie

    PHPSESSID=19ooj775tv7jc8bf1a7smpnpoq; path=/; domain=.glk-egoza.ru; HttpOnly

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

    • PHPSESSID

      19ooj775tv7jc8bf1a7smpnpoq

      Cookie name and value.

    • Path

      /

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

    • Domain

      .glk-egoza.ru

      The client will only send the cookie when requesting from this domain.

    • HttpOnly

      Prevents access to the cookie through JavaScript.

    Set-Cookie

    dle_user_id=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.glk-egoza.ru; HttpOnly

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

    • dle_user_id

      deleted

      Cookie name and value.

    • Expires

      Thu, 01-Jan-1970 00:00:01 GMT

      When the cookie should expire.

    • Max-Age

      0

      Number of seconds until the cookie expires.

    • Path

      /

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

    • Domain

      .glk-egoza.ru

      The client will only send the cookie when requesting from this domain.

    • HttpOnly

      Prevents access to the cookie through JavaScript.

    Set-Cookie

    dle_password=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.glk-egoza.ru; HttpOnly

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

    • dle_password

      deleted

      Cookie name and value.

    • Expires

      Thu, 01-Jan-1970 00:00:01 GMT

      When the cookie should expire.

    • Max-Age

      0

      Number of seconds until the cookie expires.

    • Path

      /

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

    • Domain

      .glk-egoza.ru

      The client will only send the cookie when requesting from this domain.

    • HttpOnly

      Prevents access to the cookie through JavaScript.

    Set-Cookie

    dle_hash=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.glk-egoza.ru; HttpOnly

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

    • dle_hash

      deleted

      Cookie name and value.

    • Expires

      Thu, 01-Jan-1970 00:00:01 GMT

      When the cookie should expire.

    • Max-Age

      0

      Number of seconds until the cookie expires.

    • Path

      /

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

    • Domain

      .glk-egoza.ru

      The client will only send the cookie when requesting from this domain.

    • 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.

    Access-Control-Allow-Origin

    *

    Indicate whether the response can be shared with the given origin.

    * - The browser is allowed to request resources from the origin.