Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--script=safe on port 53 displays "too short" 5 times #1774

Reelix opened this issue Oct 7, 2019 · 0 comments


Copy link

commented Oct 7, 2019

nmap -sC -sV -p53 --script=safe -vvv
Starting Nmap 7.80 ( ) at 2019-10-07 02:43 Egypt Standard Time
NSE: Loaded 362 scripts for scanning.
NSE: Script Pre-scanning.
NSE: Starting runlevel 1 (of 3) scan.
Initiating NSE at 02:43
NSE: [targets-xml] Need to supply a file name with the targets-xml.iX argument
NSE: [mrinfo] Nsock connect failed immediately
NSE: [broadcast-sonicwall-discover] No network interface was supplied, aborting.
NSE: [mtrace] A source IP must be provided through fromip argument.
NSE: [url-snarf] no network interface was supplied, aborting ...
NSE: [shodan-api] Error: Please specify your ShodanAPI key with the shodan-api.apikey argument
NSE: [broadcast-ataoe-discover] No interface supplied, use -e
too short
too short
too short
too short
too short
Completed NSE at 02:44, 30.46s elapsed
NSE: Starting runlevel 2 (of 3) scan.
Initiating NSE at 02:44
Completed NSE at 02:44, 0.00s elapsed
NSE: Starting runlevel 3 (of 3) scan.
Initiating NSE at 02:44
Completed NSE at 02:44, 0.00s elapsed
Pre-scan script results:
| broadcast-dns-service-discovery:
*Regular output here*

The 5 "too short" lines appear in a --script=safe scan even without -v with no description as to where they come from or what they mean. I'm assuming it's from one of the scripts that runs, but am unsure which.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.