Nmap Development mailing list archives

inconsistent results from nmap v7.30 when scanning the same IP twice


From: Cedric MICHEL <dr.cedric.michel () gmail com>
Date: Fri, 14 Oct 2016 14:38:35 +0200

Hi,
I found a strange behaviour on the latest version of nmap ()on Windows 7
when scanning the same IP twice.

Command :
*$ nmap.exe -p 80,443,8080,8443 -Pn -sT www.google.com
<http://www.google.com> www.google.com <http://www.google.com>*




















*Starting Nmap 7.30 ( https://nmap.org <https://nmap.org> ) at 2016-10-14
14:14 Paris, Madrid (heure d?été)Nmap scan report for www.google.com
<http://www.google.com> (216.58.208.196)Host is up (0.031s latency).rDNS
record for 216.58.208.196 <http://216.58.208.196>:
par10s21-in-f196.1e100.net <http://par10s21-in-f196.1e100.net>PORT
STATE    SERVICE80/tcp   open     http443/tcp  open     https8080/tcp
filtered http-proxy8443/tcp filtered https-altNmap scan report for
www.google.com <http://www.google.com> (216.58.208.196)Host is up.rDNS
record for 216.58.208.196 <http://216.58.208.196>: par10s21-in-f4.1e100.net
<http://par10s21-in-f4.1e100.net>PORT     STATE    SERVICE80/tcp   filtered
http443/tcp  filtered https8080/tcp filtered http-proxy8443/tcp filtered
https-altNmap done: 2 IP addresses (2 hosts up) scanned in 3.88 seconds*


I tried a previous version of Nmap (v7.10) and it behaves correctly :
*$ nmap.exe -p 80,443,8080,8443 -Pn -sT www.google.com
<http://www.google.com> www.google.com <http://www.google.com>*




















*Starting Nmap 7.10 ( https://nmap.org <https://nmap.org> ) at 2016-10-14
14:15 Paris, Madrid (heure d?été)Nmap scan report for www.google.com
<http://www.google.com> (216.58.208.196)Host is up (0.040s latency).rDNS
record for 216.58.208.196 <http://216.58.208.196>: par10s21-in-f4.1e100.net
<http://par10s21-in-f4.1e100.net>PORT     STATE    SERVICE80/tcp   open
http443/tcp  open     https8080/tcp filtered http-proxy8443/tcp filtered
https-altNmap scan report for www.google.com <http://www.google.com>
(216.58.208.196)Host is up (0.038s latency).rDNS record for 216.58.208.196
<http://216.58.208.196>: par10s21-in-f4.1e100.net
<http://par10s21-in-f4.1e100.net>PORT     STATE    SERVICE80/tcp   open
http443/tcp  open     https8080/tcp filtered http-proxy8443/tcp filtered
https-altNmap done: 2 IP addresses (2 hosts up) scanned in 3.15 seconds*

Could you please investigate on that problem ?

Best regards,
Cédric Michel.
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Current thread: