What is an HTTP request?

An HTTP request asks a web server for a page or data. NetKarte organizes selected information into Host, Protocol, and headers. Protocol is a diagnostic field label, not a claim that HTTP messages contain a header with that name.

What can it tell you?

Host identifies the requested host name, while Protocol shows whether the request was handled as HTTP or HTTPS. They describe this web access, not ownership of the IP address.

How NetKarte shows it

The HTTP information card groups Host and Protocol under Request, then separates browser-originated client headers from forwarding headers handled by reverse proxies.

Notes

NetKarte does not currently show the HTTP method or version. When a reverse proxy is present, Protocol may take trusted forwarding information into account.

Do not confuse Host with your IP

In an illustrative request, Host might be netkarte.example:3000 while the client IP is 192.0.2.20. The former names the destination and port; the latter identifies the connecting side. Searching Host does not substitute for looking up your own IP.

Read the result in order

1. Compare Host with the address bar. Intermediaries can rewrite it, so a mismatch alone does not prove a fraudulent site.
2. Check Protocol. NetKarte derives it from X-Forwarded-Proto when forwarding information is trusted. An unavailable value does not mean the connection used HTTP.
3. Separate client headers from forwarding headers. One missing header is not failure of the whole HTTP diagnosis.

The screen shows selected information from this diagnostic request, not all browser traffic. It excludes sensitive headers such as Cookie and Authorization and does not inspect TLS certificates.