Disputing a FoxTrust listing
FoxTrust publishes IP reputation verdicts in signed snapshot files that are read by the sites and services using them. This page explains what a listing means, how to find out why an address is listed, when a listing changes, and how to have a wrong listing removed. Every snapshot and its manifest link to this page.
What a listing means
A listing is a statement about an address, not about a person. It says one of two things:
- Network category: the address belongs to a kind of network, for example a hosting provider,
a Tor exit relay or space that should not appear on the internet (
bogon). Categories describe the network, not its users. - Observed behaviour: the address was seen doing something, for example SSH brute-force attempts. Behaviour fades over time: every day without a new sighting lowers its weight, and a reason leaves the record once it adds less than half a risk point. For SSH brute force that is about 19 days after the last report.
Each verdict has a risk from 0 to 100 and a level (low, medium or high). Whether a request
is allowed, challenged or blocked is decided by the site using FoxTrust, not by FoxTrust.
Why is my address listed?
Look the address up in the current snapshot with any MaxMind DB reader, for example:
mmdblookup --file f20261001.mmdb --ip 203.0.113.7
The record lists reasons. Each reason has:
| Field | Meaning |
|---|---|
code | what the address was seen as or doing, for example hosting, tor_exit, ssh_bruteforce, hijacked_netblock |
last_seen | when it was last seen (Unix time, UTC) |
contribution | how much this reason adds to the risk |
The snapshot does not say who reported an observation. FoxTrust keeps that record internally. Once you have shown that you control the address, we tell you which source lists it and how that source removes listings.
When a listing changes
FoxTrust corrects what is not true of the address now. It does not remove a true record because the listed party asks.
- A wrong category (for example "this is a residential line, not hosting"): we check the registry records and the network ourselves. If the category is wrong, we remove it for the range and report the error to the list it came from. You do not need to prove anything.
- The address changed hands ("this range was assigned to us on 2026-09-01"): once the source no longer lists it, we remove behaviour seen before that date. Behaviour seen after it stays.
- The behaviour report was wrong (the address never did this): once the source no longer lists the address, we check its record and remove the reason when the explanation holds.
- The behaviour was real and is fixed (a compromised server was cleaned): we do not remove it. It fades and leaves the record as described above. Fixing the cause is what stops new reports.
- A hijacked range: when the list of hijacked ranges no longer lists it, we remove the reason. While it does, only the network's provider of record can ask that list to remove it.
- A shared address (carrier-grade NAT, a university, a VPN): a report may come from another user of the same address. We explain the listing; a provider can send us its shared ranges.
- An objection to a true behaviour reason: we keep it while its source still lists the address, or while it can still change the level or adds 5 risk points or more, because it then still protects others. After that we remove it.
If new activity is reported after a removal, the address is listed again at once.
How to dispute a listing
Email disputes@foxtrust.dev with:
- the address or prefix;
- the snapshot version you looked at (for example
f20261001) and thecodeyou dispute; - why the listing is wrong, as in the cases above.
You do not need to prove who you are to ask why an address is listed. Before we change a behaviour reason, or hide a reason while we check it, you show that you control the address or range: we give you a token to publish in one of these places.
| Proof | What it covers |
|---|---|
| the reverse DNS name (PTR) of the address, or a TXT record at it | that address |
| a TXT record at every reverse DNS zone that covers the range | the range |
| a remark in the range's object at its regional internet registry (inetnum, inet6num, route) | the range |
Letters of authorisation and screenshots are not accepted. Corrections are always free.
Response time: we answer within 5 working days and decide within one month.
What happens next
- The dispute is accepted: the next hourly release reflects it, usually within one hour, and we tell you its version. While we check, we may hide the disputed reason once you have proved control, unless the source still lists the address.
- The dispute is refused: we tell you why, which reasons still apply and when each was last seen. You can complain to a data protection supervisory authority.
Snapshots that were already published stay in the one-year archive, because they record what was published at the time. Whether a correction should also withdraw archived files is under review. The archive index shows when each file was replaced.