Changelog
Changes to the API answers and the snapshot records, newest first. FoxTrust is pre-alpha: until the first public release a change may break /v1, and each such change is listed here, with what replaces it.
2026-11: batch lookup and keys for FoxAuth servers
- New:
POST /v1/ip/batchanswers the AS, region and city of up to 100 addresses in one request, one lookup of the quota per distinct address. See API. - New: FoxAuth servers can register for their own API key, once their daily usage reports show a key pair for at least 7 days. See API.
- The terms now say how FoxTrust processes the addresses you look up: only to answer, never stored or logged, as your processor.
GET /v1/ip/{ip}and the snapshots do not change.
2026-11: AS and location only through the API
- Breaking: snapshot records no longer carry
network(asn,org,as_country). Without it the full snapshot is about half the size (24 MB → 13 MB), and so are the hourly deltas.risk,level,categories,reasonsandcountrydo not change. - Breaking: the location file is no longer published. The manifest no longer lists
location, and the files underv1/location/are removed. - Replacement:
network,subdivisionsandcityinGET /v1/ip/{ip}, with the same fields and rules as before. The API answer does not change. - /verify reports no longer count decisions per AS; your account shows them per country.
2026-11: attacker list for FoxAuth
- New: a small signed text file of the addresses seen guessing passwords in the last 7 days,
v1/attackers/1/, listed underattackersin the manifest and rebuilt every hour. Its signed header says when it was built and until when it is valid, so an old copy cannot be passed off as current. See snapshots. - When its format changes, the old format stays published next to the new one for at least 4 weeks. The snapshots and the API did not change with it.
2026-10: region and city
- New: API answers have
subdivisions(the region, ISO 3166-2) andcitynext tocountry, in the GeoIP2 shape:subdivisionsis[]andcitynullwhen unknown. Nothing else changes in the answer. - New: a separate signed location file next to the snapshots,
v1/location/, listed underlocationin the manifest and shaped like a GeoIP2 City record. The snapshots do not change. See snapshots. - Region and city never change the risk. Keep the DB-IP notice where you show them.
2026-10: /verify reports to your account
- New: with
FOXTRUST_ACCOUNT_KEYset to a key of your account, /verify sends counts of its decisions once a minute toPOST /v1/verify/report, and your account shows them under Analytics. Reports carry no visitor address.FOXTRUST_REPORTING=offstops them. Nothing changes without a key. - /verify log lines now name a visitor by the
/24or/48network;FOXTRUST_LOG_FULL_ADDRESSES=1restores full addresses.
2026-10: more accurate locations
countryis more accurate for some addresses. No field changes. Where it comes from is listed on data sources.
2026-10: where an address is located
- Breaking:
network.countryis removed from/v1answers and from snapshot records. Its value was the country where the holder of the AS is registered, which is often not where the address is. The same value is nownetwork.asCountryin the API andnetwork.as_countryin snapshots. - New:
countryis where the address is located:country.isoCodein the API (nullwhen unknown) andcountry.iso_codein snapshots (absent when unknown), as in GeoIP2 Country records. The data comes from IP Geolocation by DB-IP, CC BY 4.0. Keep that notice where you showcountry. - The two can differ, for example for a leased block or a VPN server. Neither changes the risk.