About Watch-IP
Watch-IP (watch-ip.com) is an HTTP API and dashboard for IP-based geolocation and related network and signup signals. It's operated by Digitload Inc., based in Ontario, Canada.
What we build
Watch-IP started as a single endpoint — GET /v1/geo, called from a visitor's own browser — and grew into a small family of related APIs: server-side IP lookup and batch lookup for backend workflows, disposable-email checks for signup forms, and an impossible-travel comparison for login review. Each endpoint has its own key type, data source, and limits; the docs and product pages describe them separately rather than as one undifferentiated “IP intelligence” product, because they aren't interchangeable.
Who operates it
Watch-IP is designed, built, and operated by Digitload Inc. We don't have a public team roster to publish here yet; if you need to know who you're speaking with for a specific account, support, security, or contractual question, ask through the contact form and we'll tell you directly rather than have you guess from a generic “team” page.
Who it's for
Watch-IP is built for developers adding location, network, or signup context to a website or backend service — personalization, regional defaults, and basic signup or login review — not for identity verification, precise physical tracking, or compliance determinations. The product pages and data sources page are explicit about what each field can and can't establish.
Product history
Watch-IP shipped its first API (visitor geolocation, self-serve signup, and a customer dashboard) as an initial release, then added enrichment fields, VPN/Tor/threat indicators, and official SDKs for five languages, followed by server-side and batch IP lookup, disposable-email detection, and impossible-travel risk comparison. The changelog lists these and later releases with their actual dates and affected endpoints.
Contact
Use the contact form for support, billing, or product questions — we reply to the email address you provide. For a suspected security issue specifically, see the security page for the dedicated reporting channel.