Your monitoring system reports a switch as down, but the switch forwards traffic just fine. A new firewall rule was supposed to let your NMS poll a remote router, and nothing changed. A device moved to SNMPv3 and the graphs stopped. In all these cases the question is the same: does the device answer SNMP from outside, with these credentials?
The new SNMP Diagnostic answers it from the NetTools server: a read-only SNMP test with clear results for SNMPv1, SNMPv2c and SNMPv3.
What the test does
You enter the device's address (and port, if it is not 161), choose the SNMP version and fill in the community string or the SNMPv3 settings — security level, username, authentication and privacy protocol and passwords. Then Test SNMP runs:
- SNMPv3 engine discovery (v3 only): the agent reports its engine ID, boot count and clock, which the security model needs.
- 1–3 probes: GET requests for
sysUpTimethat measure the response time. - One read of the system group from SNMPv2-MIB: sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation and sysServices.
That is all. The tool only sends GET requests. There is no SET, no walk, no bulk request — and no guessing of community strings, users or OIDs. If you need one more value, the Read-only OID query box reads exactly one OID you enter.
A real example
For testing, the PySNMP project runs a public SNMP agent, demo.pysnmp.com, with documented test credentials. A test with SNMPv3, SHA authentication and AES privacy, run from the NetTools server on 23 October 2026, looked like this:
- SNMP Reachable — 5 of 5 requests answered (discovery, three probes and the system read), 113.8–114.2 ms per probe.
- Protocol status: network ✓, SNMP ✓, authentication "SHA + AES verified" ✓, system MIB 7 of 7 objects ✓.
- Device: sysDescr "#SNMP Agent on .NET Standard", sysServices 72 (decoded as end-to-end and application layers), and an uptime of about two and a half hours, shown as a duration together with the raw TimeTicks.
The technical details below the result list every exchange — the discovery report, each probe, the system read — with PDU types, OIDs, error status and timing. The SNMPv3 engine ID and boot count are shown; the keys and passwords are not.
When it does not answer
SNMP over UDP is quiet when something is wrong, and the tool is careful not to over-interpret that silence. A device that does not answer gets:
No SNMP Response — No SNMP response received within the configured timeout.
The explanation is deliberately precise: SNMPv1/v2c agents ignore requests with a wrong community string, access lists drop requests from unknown addresses, and firewalls drop UDP without an answer. From outside these all look the same, so the tool never claims the port is "closed".
Where the device or the network does say something, you get a specific result instead: UDP port unreachable (nothing listens on that port), network unreachable, authentication failed (an SNMPv3 agent reported a wrong digest), unknown SNMPv3 user, access denied, security level not supported, decryption failed, or malformed response. With SNMPv3 there is one more useful hint: if the agent answered the engine discovery but not the authenticated request, the tool tells you that SNMP is running and the credentials or protocols are the problem.
Built for credentials
SNMP credentials are passwords to your infrastructure, and the tool treats them that way:
- community strings and SNMPv3 passwords are masked in the form and sent only in the request body;
- they are never put in the URL, never written to the logs (the request log records the target only), never stored and never included in exports;
- they are cleared when you leave the page;
- SNMPv3 keys are derived on the server for the single test and discarded.
For SNMPv3 the tool supports HMAC-MD5, SHA-1 and SHA-224/256/384/512 authentication and AES-128 privacy. Responses must carry a valid authentication code before their content is trusted. DES is not available because the server's crypto library (OpenSSL 3) no longer provides it — a good moment to move devices to AES anyway.
Only your own devices
SNMP can reveal a lot about a device, so the tool is meant for devices you manage, and you confirm that before each test. It also enforces limits so it cannot be turned into a scanner:
- only public addresses — private networks, localhost and cloud metadata addresses are refused, and hostnames are resolved once and pinned;
- port 161 or a port from 1024 to 65535, not other well-known service ports;
- at most 15 tests per device per 10 minutes, 6 different devices per visitor per hour, and 4 different credential sets per device per hour — which rules out guessing community strings.
To test a device behind an access list, allow the NetTools probe server's address temporarily. The test runs from the internet, so devices on your local network cannot be reached, and IPv6 targets are refused for now because the probe server has no IPv6 connectivity yet.
Exports and the rest of the toolbox
Results can be copied or exported as JSON, CSV or a print-friendly report — target, version, result, response times, system information, OID reads and the exchanges, without any credentials. From the result, Ping, Traceroute, MTR and the Port Checker are one click away for the layers below SNMP.
Try it
Open the SNMP Diagnostic and test a device you manage, or try the public PySNMP test agent first. The guide explains every option, limit and result in detail.