No IP addresses. No ports. No knowing which path to test. You name what you're protecting, in plain English — and the product asks your network every reachability question for you.
Knowing which path to test is the very expertise the product replaces. So it inverts: you declare the target once — the system generates and runs every question.
One plain sentence. The system resolves the name to the real subnet from IP Fabric’s discovered inventory — and can even propose it: “these look like your servers, confirm?”
Every end-of-support, KEV, or otherwise risky box — enumerated straight from IP Fabric’s own inventory. No input. The threat context picks the devices, not you.
A read-only path-lookup per pair — the four you ran by hand at the demo, but all of them — returned as plain-English verdicts, worst-first.
The right question to ask your network is “what am I protecting?” — not “test 10.64.128.9 to 10.66.123.110 on 443.” You bring the business context. The product brings the questions.