Visual Raptor got its name from its ability to ask a machine (the Raptor) to ping other machines on the Raptor's network. There is one Raptor per network. Each time the net is scanned the next machine becomes the Raptor. Raptors have a green border and appear to be circling as they patrol their net. While on patrol they are asked to ping machines that failed to answer.
When network scanning became the next logical function for the program to provide, it started out as a simple ping from the machine the program was running on. However, some of the target machines could not use gateways. When pinged, they did not respond and were reported as down.
The fix was to ask a machine on the target's network to ping the target. If successful, the machine was marked as up but not reachable from other than its own network.
Which machine on the target's net should we ask to ping the target? What if it is down? And wouldn't it be nice to know that all the machines that can ping and send the answer back to the program can also see the target?
Do you remember THE movie? They said the Velociraptors were always circling. They acted in pairs. We call the machine we ask to do the ping the Raptor. And we rotate the task of being the Raptor among all the machines on the network. If there are three networks, there are three Raptors, all circulating within their networks.
On the program GUI, all the machines appear as check boxes. The machine that is the Raptor has a green border around it. This green border changes to the next machine each time that network is being pinged. The image is always circling, like a visual raptor.