Sorry Tiger..now that I reread your post, you were perfectly clear

Here's the results of the no risk scan:




3. Vulnerability Category Summary


The vulnerability category summary shows how the various issues that were reported are distributed across the different test categories.


Category High Med Low Other
CGI abuses
Windows
Denial of Service
Gain root remotely
General 1
Misc. 1
FTP
Gain a shell remotely
Remote file access
SMTP problems
Backdoors
CISCO
RPC
Default Unix Accounts
Firewalls
Windows : User management
Useless services
Peer-To-Peer File Sharing
SNMP
Finger abuses
Settings
Netware
Port scanners
NIS
Totals: 0 0 1 1



Low Risk Vulnerabilities
10287 Misc. : Traceroute
Other Items to be Considered
12053 General : Host FQDN


general/udp
For your information, here is the traceroute to xxxxxxxxxxx :
69.28.227.212
69.28.226.193
216.187.68.5
216.187.68.69
216.187.68.229
216.187.68.58
208.174.225.229
208.175.10.97
208.175.10.94
1x.123.6.666
1x.122.2.991
1x.728.2.297
1x.719.5.165
1x.xx.1x.1xx
?
?
?


Makes a traceroute to the remote host.

Risk factor : Low

Additional Information:
Traceroute is only a problem if the route shown above is revealing sensitive IP addresses internal to your network. If the addresses shown are all upstream to you, then you have no risk associated with this test. If, on the other hand, we are showing private addresses on the traceroute, you should consider filtering ICMP Destination Unreachable (Code 3) and ICMP Time Exceeded (Code 11) messages.

This implementation of traceroute works by sending UDP packets with a source port of 1025 and a destination port of 32768 with increasing TTL values.


general/tcp
xxxxxxxx5 resolves as xxxxxxx.client.mchsi.com.


This plugin writes the host FQDN as it could be resolved in the report.
There is no security issue associated to it.

Risk factor : None

That's still encouraging....