Request Header Viewer
The request inspector shows the IP address, request line, host, user agent, language, and safe HTTP headers visible to this site, plus browser-side context for localhost debugging.
Fast checklist
- 1 Open the homepage request inspection panel.
- 2 Review the detected IP, request line, host, user agent, language, and safe HTTP header list.
- 3 Copy the debug snapshot when reporting a local development issue.
- 4 Never paste secrets, cookies, authorization headers, or private tokens into public bug reports.
Quick diagnostic checks
request line + host + safe headersThis is useful when a reverse proxy, deployment edge, or browser setting changes the host, protocol, or language context.
host, user agent, viewport, timezoneThe viewer cannot inspect a private localhost app directly, but it can show the context your browser is sending to this site.
copy filtered snapshotCookies, authorization headers, and common token headers are filtered, but you should still review the copied text before posting it.
Live request inspection
IP, request line, and HTTP headers
This panel uses the same-origin endpoint, not a third-party IP lookup API.
HTTP request headers
Sensitive headers such as cookies and authorization tokens are filtered before display.
What the request inspector shows
The same-origin endpoint shows the IP address seen by the deployment, the request line, host, protocol, user agent, accept-language value, and a filtered list of safe request headers.
What is filtered
Cookies, authorization values, common API token headers, and other sensitive headers are excluded before the response is displayed. You should still review any copied debug report before sharing it publicly.
When this tool helps
Use it when you need a compact diagnostic note for a browser, proxy, localization, or request-header issue. Use the port and URL tools when the problem is a local service that will not open.
Related localhost guides
Localhost not working
Use a practical localhost not working checklist for wrong URLs, stopped servers, port conflicts, HTTPS mistakes, and path problems.
Typo guideLocalhost Typo Fixer
Fix common localhost typos such as locallhost, localhos, lcoalhost, localhost.com, http localhost, and https localhost.
Developer toolLocalhost URL Builder
Build localhost URLs with the right protocol, host, port, and path, then compare localhost, 127.0.0.1, and LAN IP patterns.
Developer toolLocalhost Port Lookup
Look up common localhost ports, what they are usually used for, and which command can check if a port is busy.
FAQ
Does this viewer use a third-party IP API?
No. The IP is read from the same request received by the site, using deployment headers such as CF-Connecting-IP or X-Forwarded-For when available.
Should I share request headers publicly?
Be careful. Headers can include cookies, tokens, or internal hostnames. Remove secrets before sharing any diagnostic report.
Does this tool make network calls to third-party services?
The URL builder and port lookup run in the browser, and the request inspector uses this same site endpoint. Locallhost.im uses Pageview for basic pageview analytics, but the request inspector does not call a third-party IP lookup API.
Why should I copy the debug snapshot?
The snapshot gives a concise record of the URL, request line, safe headers, user agent, and browser context. It is useful when reporting a localhost issue to a teammate or coding assistant.
Are cookies and authorization headers shown?
No. Sensitive headers such as cookies, authorization, and common API token headers are filtered before display.