
| Discovery type | Condition | Nmap Usage |
Auto Discovery | Automatic discovery is enabled during the initial startup of Applications Manager (standalone) for servers discovered through AD, and in the APM Plugin for servers shared from OpManager | Perform an openport scan using the ports configured in the following file: AppManager\working\conf\discovery\defaultPorts.properties |
Perform Application Discovery | Enabled while adding/updating Windows/Linux server monitor | Perform an openport scan using the ports configured in the following file: AppManager\working\conf\discovery\defaultPorts.properties |
Network Discovery | If No credentials supplied or authentication fails. | Performs openport scanning on target server with the ports configured for the discovery profile and discovers Applications. To view or modify the configured ports, navigate to Discovery Profile → Edit → Select Application (the second page of the Network Discovery profile). Prerequisite: Enable "Discover unknown devices during ADDM discovery" under Settings → Add/Discover → Discovery → Discovery Settings. Refer to the ADDM help page |
| Protocol | Windows Server | Linux Server |
ICMP | Windows tracert | System traceroute command |
TCP | tracetcp.exe (bundled with APM) | System traceroute command |
UDP | Nmap (bundled with APM) | System traceroute command |


Method | Nmap script(s) | What it finds |
DNS brute force | dnsbrute | Subdomains of the root domain, by querying a wordlist of common host names. |
Certificate SAN | sslcert | Host names listed in the Subject Alternative Name of the certificate served on the monitored TLS port. This is the only source of sibling (related) domains. |
DNS zone walk | dnsnsecenum, dnszonetransfer | Subdomains obtained from the domain's authoritative name servers through DNSSEC NSEC enumeration or an AXFR zone transfer, where the zone permits it. |
Web page crawl | (none does not use Nmap) | Subdomains referenced by links, scripts, images, iframes and forms on the monitored page. |


Applications Manager continues discovery without filtering the configured ports through Nmap.
As a result, more ports may need to be checked individually.
This can lead to:
Less efficient application identification
If both credentialbased discovery methods fail and Nmap is unavailable, Applications Manager may not be able to identify applications through their open ports.
The device may therefore be discovered without the expected list of applications.
If Nmap cannot identify the operating system, Applications Manager may not correctly determine that the target is a Windows system for Server discovery.
As a result, the discovery process may proceed with an inappropriate discovery method.
If Nmap is unavailable, SSL/TLS cipher and vulnerability information cannot be collected.
The following information may therefore be unavailable:
Protocol/cipher details
Weak cipher information
SSL/TLS vulnerability indicators
Overall SSL/TLS security grade
However, certificaterelated functionality such as certificate expiry checking can continue independently.
