Small on purpose
IPGetter is built with plain PHP, CSS and a small amount of JavaScript. There is no heavyweight front-end framework sitting between you and a lookup.
Network tools that get out of your way.
IPGetter started as a tiny public IP checker. The idea is still the same: give you the network information you need quickly, explain what it means, and avoid burying the answer under clutter.
Why IPGetter exists
Sometimes you just need to know your public IP. Sometimes you need to check a DNS record, follow a redirect, inspect a TLS certificate or work out why email authentication is failing. Those jobs are related, so IPGetter keeps them together in one lightweight toolbox.
The site is designed around direct answers first. Tools stay usable without creating an account. A free account is optional for synced terminal history, higher limits and developer API keys, rather than a gate in front of basic network checks.
Explain the result
A value without context is not always useful. Tool pages explain what is being checked, how the result is produced and where its limitations matter.
IP data stays close
Core GeoIP and ASN lookups use local MMDB databases on the IPGetter server rather than sending every visitor's IP to a live third-party geolocation API.
Use the tool and leave
Most network checks should not require an account, a project, a workspace or a ten-step onboarding flow. The basic tools are intentionally immediate.
How the tools work
Different tools use different sources. Some calculations, such as subnetting and address conversion, happen directly in PHP. DNS tools query public DNS data. TLS and HTTP tools make controlled outbound connections from the IPGetter server. Domain registration data comes from authoritative RDAP services.
Where a result has an important limitation, IPGetter tries to say so. GeoIP is approximate. DNS propagation is really a comparison of resolver caches, not a map of every DNS server on earth. A security header being present does not automatically mean its policy is correct.
Pages or terminal
Everyday checks are available as normal web tools. Many of the same checks are also available through the browser IPGetter Terminal, and the terminal can be embedded on another site.
For scripts and integrations, the developer API exposes versioned public endpoints. Basic calls work anonymously, while free accounts can create revocable API keys for higher limits.
Understand the networking behind the result
The IPGetter Guides go deeper into the concepts that span several tools, including DNS caching, email authentication, TLS certificates, IPv4, IPv6 and CIDR.
Questions, bugs or API help?
If something is not behaving as expected, an API integration is giving you trouble, or you have a general question about IPGetter, there is now a dedicated support route.
Support
Talk to a human.
Use the contact page for product support, bug reports, API questions or general feedback.
Privacy by design
IPGetter uses local GeoIP data, one-way password and API-key hashes, short-retention first-party analytics and minimal account data. You can review the details in the Privacy Policy and control first-party analytics from the Cookies page.