DEV Community

IP99
IP99

Posted on

An IP Timezone Is Not a Traveler's Clock: Reading geo.tz on IP99

An IP lookup that returns a time zone can feel like you have the user's clock. You do not. IP99 sets geo.tz from the geolocation of the address block: an IANA time zone name the address is expected to be in, not a reading from the device, the browser, or NTP. A rule that compares a client's timezone to geo.tz and fires on any mismatch is comparing a user setting to the documentation of a network. The same free, no-key call that returns risk also returns geo. JSON samples were verified on 18 November 2026 UTC, using the free profile only. Notes: IP99, API, IP location, free geolocation and risk API.

One curl, the tz field

curl https://ip99.com/v1/ip/8.8.8.8
Enter fullscreen mode Exit fullscreen mode

No API key, no registration. Verified 18 November 2026 UTC (computed_at 2026-11-18T13:11:20Z):

{
  "ip": "8.8.8.8",
  "computed_at": "2026-11-18T13:11:20Z",
  "evidence_state": "none",
  "geo": {
    "continent": "NA",
    "country": "US",
    "region": "California",
    "city": "Mountain View",
    "district": "",
    "lat": 37.38605,
    "lon": -122.08385,
    "tz": "America/Los_Angeles"
  },
  "network": { "asn": 15169, "usage_type": "IDC" },
  "risk": { "score": 0, "level": "none", "signals": ["hosting"] }
}
Enter fullscreen mode Exit fullscreen mode

geo.tz is an IANA name, here America/Los_Angeles. The six string keys — continent, country, region, city, district, tz — are always present on a successful lookup. A name the database does not have is an empty string, never a missing key and never a 0. Official field docs: tz is empty only for a rare block with no timezone in the database.

hosting and usage_type: "IDC" describe the network scene, not a fraud verdict — official guidance is not to block on hosting or mobile alone. Score 0 with evidence_state: "none" means IP99 holds no current risk evidence, not that the address is safe. risk.score is the freshness and strength of verifiable evidence, not attacker probability. Google Public DNS is anycast; Los Angeles time is a reasonable zone for the registered block, not the clock of the person who just logged in.

Compare the zone, not only the city

Official guidance on how IP location works already treats the timezone as a check, not as a second pin on the map:

  1. Check for a VPN or proxy first. It is the most common reason a location "looks wrong," and the fix is not in the geolocation database — it is in risk.signals.
  2. Compare geo.tz, not just the city. A wrong city with a correct time zone usually means "registered at the regional equipment, used elsewhere." A timezone that is wrong as well is a stronger hint of a genuinely stale record.
  3. Then check network.usage_type. MOB or GTW means the address is shared, and its city is approximate by construction.
  4. Then treat the result as an estimate. Use city-level location to pick a language, a currency, or a legal region — not to decide that a specific person is in a specific place.

That is the point of geo.tz: ask whether the block is still in the right zone, not whether a laptop set to UTC, a traveler who left the timezone unchanged, or a VPN exit should be rejected.

The geolocation database is IP99's own. As of data version 20261118 it covers 244 countries and regions for IPv4 block attribution, operator, ASN, and usage type, and it is rebuilt daily (geo 20261118; risk 20261118211156 the same day). The risk database is separate and updates every 10 seconds.

Two addresses, one ASN, two IANA zones

Anycast and sibling addresses in the same network do not share a single clock. Verified the same day:

curl https://ip99.com/v1/ip/1.1.1.1
curl https://ip99.com/v1/ip/1.0.0.1
Enter fullscreen mode Exit fullscreen mode

1.1.1.1 (computed_at 2026-11-18T13:11:24Z):

{
  "ip": "1.1.1.1",
  "computed_at": "2026-11-18T13:11:24Z",
  "evidence_state": "none",
  "geo": { "continent": "OC", "country": "AU", "region": "Queensland", "city": "Brisbane", "district": "", "lat": -27.4679, "lon": 153.0281, "tz": "Australia/Brisbane" },
  "network": { "asn": 13335, "usage_type": "IDC" },
  "risk": { "score": 0, "level": "none", "signals": ["hosting"] }
}
Enter fullscreen mode Exit fullscreen mode

1.0.0.1 (computed_at 2026-11-18T13:11:32Z):

{
  "ip": "1.0.0.1",
  "computed_at": "2026-11-18T13:11:32Z",
  "evidence_state": "none",
  "geo": { "continent": "OC", "country": "AU", "region": "New South Wales", "city": "Sydney", "district": "", "lat": -33.86785, "lon": 151.20732, "tz": "Australia/Sydney" },
  "network": { "asn": 13335, "usage_type": "IDC" },
  "risk": { "score": 0, "level": "none", "signals": ["hosting"] }
}
Enter fullscreen mode Exit fullscreen mode

Both are Cloudflare addresses in AS13335, both IDC with hosting, both in Australia — and they are not the same IANA zone. Australia/Brisbane and Australia/Sydney do not always share an offset: Queensland does not observe daylight saving; New South Wales does. Collapsing the country into one "AEST" zone would already be wrong; treating either city as "where the user is" would be worse. These are registration and routing facts about the blocks. The resolver is anycast; Brisbane or Sydney is not the node that answered you, and it is not a traveler's clock.

IPv4 and IPv6 exits can disagree as well. A lookup of 2606:4700:4700::1111 the same day (computed_at 2026-11-18T13:11:45Z) returned San Francisco and America/Los_Angeles, not Australia/Brisbane. A dual-stack client may present a different egress family on different requests, so a "client timezone versus IP timezone" rule can fire on one family and stay quiet on the other, for the same person.

When a mismatch is the expected answer

A consumer address still describes a block, not a person. Official docs use 27.22.66.200 as the China example. Live on 18 November 2026 UTC:

curl https://ip99.com/v1/ip/27.22.66.200
Enter fullscreen mode Exit fullscreen mode
{
  "ip": "27.22.66.200",
  "computed_at": "2026-11-18T13:11:27Z",
  "evidence_state": "active",
  "geo": { "continent": "AS", "country": "CN", "region": "Hubei", "city": "Xiangyang", "district": "Fancheng", "lat": 32.04482, "lon": 112.13546, "tz": "Asia/Shanghai" },
  "network": { "asn": 4134, "usage_type": "DYN" },
  "risk": { "score": 10, "level": "low", "signals": ["dialup_pool", "hijacked_proxy", "proxy"] }
}
Enter fullscreen mode Exit fullscreen mode

Asia/Shanghai matches the country and the region. That does not mean a specific person is in Fancheng, and a browser set to Asia/Shanghai does not "confirm" the login. This address also carries current risk evidence (dialup_pool, hijacked_proxy, proxy) at score 10 / low — a separate reading from geo. Official guidance: check those signals before you argue with the city or the zone, and do not hard-ban an account on hijacked_proxy alone; the holder is often a victim.

A timezone mismatch is often expected. A VPN or proxy exit is reported in the exit's zone — look at risk.signals first. MOB or a shared GTW address serves a wide area. Anycast, hosting, and corporate headquarters egress describe the server or the registered block, rarely the user. And the client timezone is a setting: laptops stay on the home zone during travel, some systems are set to UTC, and a VM inherits the image default.

None of that is a reason to skip the field. It is a reason not to treat disagreement as proof of account takeover. If the city looks off but geo.tz is consistent with the region, prefer "registered elsewhere, used in-zone" over "stale data." If the zone is also implausible, discount the record and add a check — a step-up challenge, not an automatic ban. Combine it with evidence state and signals.

Try it

curl https://ip99.com/v1/ip/8.8.8.8
curl https://ip99.com/v1/ip/1.1.1.1
curl https://ip99.com/v1/ip/1.0.0.1
curl https://ip99.com/v1/ip/2606:4700:4700::1111
curl https://ip99.com/v1/ip/27.22.66.200
curl https://ip99.com/v1/me
Enter fullscreen mode Exit fullscreen mode

Anonymous quota is 500 lookups/day per client IP (60/min); a free logged-in key raises it to 5,000/day. Check remaining with GET https://ip99.com/v1/me. OpenAPI: https://ip99.com/openapi.json. Pricing: https://ip99.com/en/pricing.

Do not treat IP99 scores or geo as identical to other ThreatHunter datasets. This article only claims what free /v1/ip and the cited product pages document.

IP99 is a ThreatHunter product. An IP timezone is the IANA zone of a network block, not a traveler's clock and not a person. Start at https://ip99.com; the field contract is on IP location, the free geolocation and risk API, and https://ip99.com/api.

Top comments (0)