HELP · FEEDBACK · CORRECTIONS
Support
Write to support@ipscanner.pro. It is read by the people who build the scanner, not a ticket queue, so a short message with your operating system, what you expected and what actually happened is usually enough to get somewhere.
Write to support@ipscanner.pro
What to include
Most reports that go nowhere are missing one of these. None of it takes long, and together it is usually the difference between a fix and an exchange of guesses.
- Your operating system and version — for example macOS 15.2 on an M2, or Windows 11 23H2 x64.
- What you were doing: the scan profile, the range you entered, and whether it was a fresh scan or restored history.
- What you expected to happen, and what happened instead.
- The exact wording of any message you saw. A screenshot of the whole window beats a cropped one.
- Whether it happens every time or occasionally, and anything that makes it more likely.
Please leave out anything you would not want in an email: credentials, a full inventory export of a network that is not yours, or the contents of a device you were investigating. We do not need them, and asking for them would be a bad habit for a tool built around keeping your data local.
Which channel to use
| What you found | Where it goes | Why |
|---|---|---|
| A crash, a wrong result, a device that should have appeared, an interface that confused you | support@ipscanner.pro | This is ordinary product feedback and the fastest way to get a fix into the next build. |
| Anything that looks like a security problem: unexpected traffic, a permission the app did not need, a path that runs code you did not choose | Security reporting | Use the disclosure process so it is handled properly and not discussed in the open before it is fixed. |
| A question about what the scanner does with your data | support@ipscanner.pro | The privacy page answers most of it, and anything it does not answer is worth telling us about. |
| Something wrong on this website — a broken link, an out-of-date claim, a page that reads badly | support@ipscanner.pro | Corrections are welcome. We would rather fix a page than leave it wrong. |
Before you write, these may answer it
- Where each platform stands — if your question is when you can install it.
- Why a website cannot scan your network — if you expected the scan to run in this browser tab.
- Portable scanning on Windows — if you cannot run installers on your machine.
- Data and privacy — what is stored, where, and for how long.
Common questions
How long will it take to get a reply?
We do not publish a response-time commitment, because a commitment we cannot keep is worse than none. Messages are read by the people building the product, and a clear, reproducible report gets attention faster than a general one.
Should I send my scan results?
Only if they are needed, and only after you have looked at them. An export lists private addresses, hostnames and MAC addresses from your network, which is information about you. A screenshot of the single row that misbehaved is usually more useful and shares far less.
The scanner cannot see a device I know is there. Is that a bug?
Sometimes, and sometimes it is the device. A machine can be configured not to answer, a firewall can drop probes, and guest or client isolation on a router deliberately hides devices from each other. Tell us what the device is and how it is connected and we can usually say which it was.
Can you help me scan a network I do not administer?
No. The product is for networks you own or are authorised to test, and that is a line we hold in the interface as well as in an answer here.
Is there a forum or a chat channel?
Not yet. Email is the only channel today, which keeps every report in one place while the product is small. If that changes it will be announced on this page.
Found something that looks like a security problem rather than a bug? It has its own process, so that it is handled properly and not discussed in public before there is a fix.