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

  • https://ugzhnkchr.ru/user/peakdimple41/

    Status
    200
    Message
    OK
    Time
    778 ms
  • IP
    87.236.16.58
    View Map

  • Timing

    Wait

    0 ms

    DNS

    275 ms

    TCP

    141 ms

    Request

    0 ms

    First Byte

    218 ms

    Download

    0 ms

    Total

    778 ms

  • HTTP Headers

    Server

    nginx-reuseport/1.21.1

    A name for the server.

    • Server

      nginx-reuseport

      Description of the server software.

    • Version

      1.21.1

      Version number.

    Date

    Wed, 03 Jul 2024 09:23:38 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
    X-Powered-By

    PHP/5.6.40

    The software powering this site.

    Set-Cookie

    PHPSESSID=91946689f31c219382515032ea5e61c3; path=/; HttpOnly

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

    • PHPSESSID

      91946689f31c219382515032ea5e61c3

      Cookie name and value.

    • 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, post-check=0, pre-check=0

    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.

    • post-check

      0

      Problems were found.

      • Option is not one of known values.

    • pre-check

      0

      Problems were found.

      • Option is not one of known values.
    Pragma

    no-cache

    HTTP/1.0 backwards compatible cache handling.

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