METHODOLOGY
Every factual claim about a product we do not make comes from that vendor’s or project’s own published material, with the date it was read. We have not benchmarked any competitor, and no page claims we have. Every comparison lists what our own tool cannot do, in the same section as everyone else’s.
Comparison pages are written by the people selling one of the products roughly all of the time, and readers know it. The usual response is to hide that fact behind a neutral tone. We would rather do the opposite: say plainly that we make one of the tools in the table, then publish the rules that stop that from bending the result, so you can check whether we followed them.
These pages are read by people deciding what to run on a network they administer. That makes accuracy an obligation rather than a quality target, and it is why the rules below are deliberately restrictive.
A claim about another product traces to that vendor’s or project’s own publication — a documentation page, a release note, a repository. Review sites, listicles and download portals are not sources. When no source covers a point, the table says “not stated in the source we cite” instead of filling the gap from memory. A wrong statement about a competitor is not a small error; it is a trust failure and a legal risk.
Every source shows when it was last read. Platform support, licence terms and account requirements change, and a citation without a date quietly rots. Pages are re-checked quarterly and immediately when a cited product changes.
We have not installed, timed or measured any competitor to write these pages, and none of them contains a speed, accuracy or reliability comparison. This is the disclosure that costs the most traffic and buys the most trust: “fastest IP scanner” pages rank, and we are not going to write one from data we do not have. If we ever do measure another tool, the measurement gets its own page describing the method, and this paragraph changes.
Every comparison has a section listing what each tool cannot do, and the tool we build is in it, on the same terms and in the same list. Where a competitor is better, the page says so — including when the honest recommendation is to use something other than ours.
IPScanner.Pro has no public download. Signed and notarized distribution does not exist yet, so no page on this site carries a download button, an installer link or a version number. Planned capabilities are labelled planned wherever they appear.
Nothing on this site is a paid placement or an affiliate link. No page carries a star rating, an aggregate score or a “best of” badge, and the structured data behind these pages contains no review or rating entities, because we have no ratings to report. Inventing them would be a manipulation of both readers and search results.
Every link off this site carries rel="nofollow noopener". That is an owner decision with a known cost — it passes no ranking signal to the sources we cite — and it is applied through one shared component so it cannot be forgotten on a new page.
If a page here is wrong, or a product has changed, telling us is the fastest way to fix it. We would rather correct a page than defend it.
The only expertise this site asserts is narrow and checkable: the person who writes these pages writes the scanner they describe. That covers how discovery, scope enforcement, consent, retention and port scanning work in our own product, and it covers reading another project’s documentation carefully.
It does not cover how any other tool behaves in practice, how any of them performs on your network, or what your organisation’s policy permits. Where a page would need that kind of knowledge, it says what is unknown rather than filling it in. You will not find a fabricated author, a borrowed job title or a certification list on this site; an invented expert is worse than no byline at all, and it is a straightforward deception of the reader.
Two of them, both published by Google and both worth reading directly rather than through an SEO blog’s summary:
The framework they describe is experience, expertise, authoritativeness and trustworthiness. Of those, trustworthiness is the one a small project can actually earn, and the rules above are what earning it looks like in practice: sourced claims, dated citations, stated limitations, and no claims about testing we did not do.
Writes and maintains the scanning engine described on this page, including the scope, consent and Full-ports rules the desktop application enforces.
What the comparisons are based on: The vendors’ and projects’ own published documentation, and the IPScanner.Pro codebase. No benchmark, and no hands-on test of any other tool listed here.
Last reviewed 2026-09-14.
Write to support@ipscanner.pro. Out-of-date facts about another product, a claim that overstates what we build, a broken link, a page that reads badly — all of it is useful, and corrections get made. If you have found a security issue in the scanner itself, the disclosure policy is the right route and security@ipscanner.pro is the address.
The comparisons themselves, all held to the rules on this page: