The path database contains one line per target network, and is divided into fields separated by white space. The first field is the target network, in a familiar form:
135.104.0.0/16
The filters assume that all four octets are present.
The remaining fields are in the form:
<name>=[<date>:]valuewhere <date> has the form yyyymmdd, suitable for sorting (although not Y10K compliant).
The field types are listed below. Only the first four appear in current databases--the rest are deprecated and have not been used since fall 1998. Some fields may appear more than once, representing data collected at different times. They are usually sorted by date.
| Name | Date | Value | Description |
| Path | yes | see below | path to target |
| Probe | yes | (none) | date of last test |
| Target | yes | IP addr | host on target net |
| Whiner | yes | email addr | don't scan this net |
| Asnpath | no | unused | deprecated |
| Name | no | net owner | not used |
| Complete | no | (none) | deprecated |
| Pathdate | no | date | deprecated |
The path field contains a comma-separated list of IP numbers, possibly followed by a completion code. If no code is present, the path reached the target. The other completion codes are:
| ? | same as !? | deprecated |
| !F | ICMP filtered | firewall encountered |
| !H | ICMP host unreach. | bad guess for the target |
| !N | ICMP net. unreach. | firewall, filtered, etc |
| !R | routing loop, deprecated | |
| !L | routing loop | |
| !Z | incomplete | deprecated |
| !! | incomplete | deprecated |
| !? | incomplete | no response |