Legal

Attributions & Data Licences

Last updated: 6 June 2026

This is a plain-language legal document written for clarity. It does not constitute legal advice. Defined terms are used consistently across our legal pages.

GeoQ is built on a mix of our own work and high-quality third-party and public data. We're required — and glad — to credit our sources. If you use GeoQ on the Free tier, you must preserve the attribution described below (see the Acceptable Use Policy).

Required attribution

IP geolocation data by DB-IP (https://db-ip.com), licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Datacenter and satellite detection uses publicly published IP ranges from AWS, Google Cloud, Microsoft Azure and network operators; Tor detection uses the Tor Project public exit list. Drop-list data © The Spamhaus Project; recent-abuse data from Emerging Threats; routing data from the RouteViews and RIPE RIS projects; allocation data from the Regional Internet Registries' published delegated statistics; relay-range data from Apple's published iCloud Private Relay egress ranges.

Details

IP geolocation — DB-IP (CC BY 4.0)

Country, region, city, latitude/longitude and timezone data is provided by DB-IP under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. CC BY 4.0 requires that attribution be preserved. The site footer carries a "Powered by DB-IP" link for this reason.

Datacenter & satellite detection — published operator ranges

Datacenter and cloud detection uses publicly published IP ranges from major providers, including Amazon Web Services, Google Cloud and Microsoft Azure. Satellite detection (the connection_type === "satellite" value) uses publicly published operator ranges. These ranges are published by the providers themselves and are used to set connection_type and attribute a provider where possible.

Tor detection — Tor Project public exit list

Tor exit-node detection uses the Tor Project's publicly published exit list. We are grateful to the Tor Project for maintaining this public resource.

Drop-list detection — Spamhaus DROP

The is_drop_listed signal uses the Spamhaus DROP (Don't Route Or Peer) lists. DROP data is © The Spamhaus Project and used under Spamhaus's published terms for the DROP lists. We retain only the current published DROP ranges and refresh them on each update; we do not redistribute the lists. See spamhaus.org/drop.

Recent-abuse detection — Emerging Threats & CINS

The beta recent_abuse signal draws on the Emerging Threats open rule/IP lists and the CINS Army list. The Emerging Threats open ruleset is distributed under a BSD-style licence: redistribution and use, with or without modification, are permitted provided the copyright notice and disclaimer are retained, and the data is provided "as is" without warranty. We honour that notice. See rules.emergingthreats.net.

Routing health — RouteViews & RIPE RIS

The routing signals (is_announced, is_bogon and the rpki validation state) are derived from public BGP data published by the University of Oregon RouteViews project and the RIPE NCC Routing Information Service (RIS), validated against RPKI data. We credit both projects for making this data openly available.

Allocation data — RIR delegated statistics

The allocation_date, allocation_age_days and registration_country fields are derived from the publicly published delegated-statistics files of the five Regional Internet Registries (ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC). These files are published by the RIRs for public use.

Relay detection — Apple iCloud Private Relay

The is_relay signal (with relay_provider: "icloud") uses Apple's publicly published list of iCloud Private Relay egress IP ranges. Apple publishes these ranges specifically so that operators can recognise relay traffic. We use them only to identify relay exits — a benign network kind that reduces, never raises, the risk score.

Using GeoQ on the Free tier

On the Free tier you must display a visible attribution that preserves the credit above (a "Powered by GeoQ & DB-IP" link to this page is sufficient). Paid plans remove the visible-attribution requirement, but the underlying third-party licences (e.g. CC BY 4.0) still apply to the data.

Questions

For licensing questions, contact support@geoq.io.