Quote:
Originally Posted by masraum
|
I ran an nmap scan against the server. Inbound is definitely hitting the proxy.
Code:
nmap scan report - scan @ May 26, 2010 - 05:47scan summary | scan info | 192.208.27.6 / www.wapa.gov | runstats scan summarynmap was initiated at May 26, 2010 - 05:47 with these arguments:
nmap -T4 -A -v -PE -PA21,23,80,3389 www.wapa.gov
The process stopped at . Debugging was disabled, the verbosity level was 1.
192.208.27.6 / www.wapa.gov(online)ping results
address192.208.27.6 (ipv4)
hostnameswww.wapa.gov (PTR)
portsThe 998 ports scanned but not shown below are in state: filtered
Port State Service Reason Product Version Extra info
80 tcp open http-proxy syn-ack BlueCoat SG-400 http proxy
443 tcp open http-proxy syn-ack BlueCoat SG-400 http proxy
remote operating system guessused port 80/tcp (open)
os match: Blue Coat SG200 proxy server (SGOS 4.2.2.8 - 4.2.6.1)
accuracy: 87%
reference fingerprint line number: 3912
os match: Blue Coat SG810 proxy server (SGOS 4.2.3.26)
accuracy: 86%
reference fingerprint line number: 3929
system uptimeuptime: 402275 sec
last reboot: (null)
tcpsequenceindex: 255
difficulty: Good luck!
values: 58EE6935,2E21BDD,1A24EBB5,62D9428F,2468D4B6,4AF9CF25
ipidsequenceclass: Incremental
values: EC5B,EC5C,EC5D,EC5E,EC5F,EC60
tcptssequenceclass: 2HZ
values: C46C2,C46C2,C46C2,C46C2,C46C3,C46C3
tracerouteport: 21
proto:
Hop Rtt IP Host
1
runstats32 sec. scanned
1 host(s) scanned
1 host(s) online
0 host(s) offline