Client address from this deployment
What Is My IP
Detect the public IP address this deployment sees for your request, show IPv4 or IPv6, expose proxy-chain context, and add reverse-DNS, ASN, and RDAP ownership hints when the network sources provide them.
Use this page when you need the public address your request presents to this deployment, not a guessed browser-side answer. It is especially useful before debugging allowlists, reverse proxies, exposed services, or address ownership questions.
The result is based on the address this deployment actually sees for your request. If the app is behind a trusted reverse proxy, the report also shows that context.
Reverse DNS, ASN data, and IP RDAP help explain who owns the visible address block and how much confidence the public metadata deserves.
If the deployment cannot safely determine a public client IP, the report says so explicitly instead of inventing a result from untrusted headers.
Request source
What Is My IP
Report
ReadySummary
Server-side diagnostic report
Run a check to generate a structured report with status, timings, technical details, and raw output where available.
01
What this tool checks
The public IP visible to this server
The result is based on the address this deployment actually sees for your request. If the app is behind a trusted reverse proxy, the report also shows that context.
Address ownership hints
Reverse DNS, ASN data, and IP RDAP help explain who owns the visible address block and how much confidence the public metadata deserves.
Proxy-awareness and limitations
If the deployment cannot safely determine a public client IP, the report says so explicitly instead of inventing a result from untrusted headers.
02
How to use it
Run this page first when you need the public address your request is presenting to Gitae right now.
Compare the result with your reverse proxy configuration if you expect one address but the platform reports another.
Open IP Lookup next when you want a dedicated report focused on address ownership, PTR records, and infrastructure clues.
03
How to read the result
The public IP is the core answer
That address is the one this deployment can attribute to your request. It is the right value for allowlists, debugging proxy behavior, or checking whether traffic exits through the network you expected.
Proxy chain context matters
When Gitae is behind a trusted reverse proxy, the report shows that it relied on forwarded client information. Without trust proxy, the backend stays conservative.
Ownership hints are still hints
ASN, PTR, and RDAP often point in the right direction, but they may describe transit, hosting, or allocation layers rather than the exact application owner.
Guides that help you get more from this tool
Interpret the output, understand common failure modes, and choose the next diagnostic step without leaving the product.
What is my IP FAQ
Is this the same as a browser-only IP widget?
Not exactly. This result is server-side and shows the public address the backend actually observed for your request, including reverse-proxy context when configured safely.
Why might the page fail to determine my public IP?
Usually because the app sits behind a reverse proxy and Express trust proxy is not configured, so the backend refuses to trust forwarded client headers blindly.
Can this prove what IP every site on the internet sees for me?
No. It proves what this deployment sees from its own network path. Another service in another region can see a different egress address.