Terms of Service
Last updated: 2026-05-25
These terms govern your use of IPconf — the websites ipconf.me, ipconf.cn, and the API at api.ipconf.me ("the Service"). By using the Service you agree to them. If you don't agree, please don't use it.
1. The Service
IPconf provides IP geolocation information, network diagnostic tools, and a public REST API. The Service is provided as a free utility, on a best-effort basis. We may change, add, or remove features at any time without notice.
2. Acceptable use
You may use the Service for personal, research, educational, and reasonable commercial purposes. You may not:
- Use the Service in a way that disrupts it for other users (e.g., automated requests at a rate that triggers abuse protection).
- Use the network-diagnostic tools (
/api/tools/*) to scan, probe, or attack systems you don't own or have explicit permission to test. - Republish bulk geolocation data as your own dataset, or attempt to scrape the entire database.
- Use the Service for illegal purposes under the laws applicable to you or to us.
- Bypass or circumvent the rate limits, authentication tokens, or other technical access controls.
3. Rate limits and fair use
Public IP endpoints are rate-limited (currently 60 requests/minute per IP for /api/ip).
Network-tool endpoints require a client key and have lower limits, documented on the
API documentation. If you need higher limits, contact us — we accommodate
reasonable use cases.
4. Accuracy and "as-is" disclaimer
The Service is provided "as is", without warranty of any kind. IP geolocation is inherently approximate: country-level accuracy is high, region- and city-level accuracy is best-effort and known to be unreliable for mobile carriers, corporate networks, and cloud IPs. The data and tool results are for informational purposes only. We make no warranty of fitness for any specific purpose.
5. No liability
To the maximum extent permitted by law, we are not liable for any direct, indirect, incidental, consequential, or special damages arising from your use of the Service — including but not limited to: incorrect geolocation, downtime, missed alerts, lost data, or decisions made based on the Service's output.
6. API attribution
You may use the IPconf API in your own applications without attribution requirements. If you build a product or research that depends on it, a credit linking back to ipconf.me is appreciated but not required.
7. Third parties
The Service uses third-party data sources (MaxMind GeoLite2, ip-api.com) and infrastructure (Cloudflare, analytics providers, ad networks). See the Privacy Policy for details on how each interacts with your visit.
8. Changes
We may update these terms when our practices change. The "Last updated" date at the top reflects the most recent revision. Continued use of the Service after a change constitutes acceptance of the new terms.
9. Contact
For questions about these terms, reach out via the channels listed on the About page.