Check your visible IP
Run the lookup and copy the IP address returned by the Convurter server.
Output
IPv4 or IPv6 request address
Network, IP, DNS, And Security Tools
What Is My IP
Check the public IP address Convurter sees from your request.
Waiting
Uses Convurter servers for lookup or processing. Do not enter secrets.
Input
What Is My IP. This lookup uses public network records and responses. Do not enter secrets or private URLs.
No input is required. Run the lookup to see the request address Convurter receives.
Guide
How to use What Is My IP
Step-by-step
- Open the tool and review any available settings.
- Run the inspection lookup and review the point-in-time response.
- Review the ip-address result, then copy or download it if the workbench offers that action.
- Use the related tools on this page for cleanup, validation, conversion, or the next step in the workflow.
Questions
Is What Is My IP free to use?
Yes. The public lookup is free to use with bounded rate limits.
Are my files uploaded?
No files are uploaded, but the entered lookup target is sent to Convurter servers to fetch the public response. Do not enter secrets.
What should I check before using the ip-address result?
The result comes from the incoming request after trusted proxy handling. Review the final output before using it in production work.
What can I do after this?
Good next steps include DNS Lookup, HTTP Headers Checker, and Subnet Calculator.
Workflow fit
Use What Is My IP in the right place
If you are unsure, use the related tools and family hub to choose the closest workflow before committing to an output.
Best for
- Point-in-time network, DNS, HTTP, email DNS, SSL, redirect, IP, or password checks that need a quick operational signal.
- Support tickets, implementation QA, and configuration review before deeper security testing.
- A focused inspect task where the expected output is ip-address.
Before you start
- This tool runs in the browser, so keep the tab open until the result is created and downloaded or copied.
- Use domains, public hosts, and values you are authorized to inspect.
- Avoid pasting private keys, production secrets, or credentials into lookup-style tools.
- Network answers can differ by resolver, cache, region, and timing.
- Use the report as a decision aid, then route to cleanup, conversion, or verification tools if it finds something notable.
Quality checks
- Treat inspection output as a signal report, not as a guarantee that every possible issue was checked.
- Treat results as a point-in-time signal, not a complete security audit.
- Recheck after DNS, certificate, redirect, or header changes have propagated.
- Escalate critical production security questions to a full security review.
- Copy or download the result only after confirming the displayed output matches the task you intended.
Common mistakes
- Assuming one successful lookup proves every region or client sees the same result.
- Treating a header, SSL, or DNS report as proof that the entire application is secure.
- Ignoring caching and propagation windows after configuration changes.
- Skipping input review because the tool feels instant.
- Treating the first result as final without checking the destination requirement.
Continue the workflow
Use these when the current result is only one step in a longer task.
Verify or clean up
Use these when the output needs checking, cleanup, comparison, compression, or a final share-ready pass.