contact
Contact NetChecks
The fastest channel is email at hhammoud@inovisum.com. The maintainer reads every message; most non-urgent threads are answered within two to three business days. Security-related reports are prioritized ahead of feature requests. There is no phone, ticket portal, or social DM channel for support — keeping correspondence in writing lets us cite a packet capture, an RFC section, or an upstream API response.
Reporting a lookup bug
For a tool that returned a wrong or stale result, include the tool name, the exact input (domain, IP, MAC, CIDR, host:port), the result the page returned, the result you expected, and the authoritative source you checked it against (a dig output, a curl response, a registry record, an IEEE OUI assignment). The tool either has a real bug, an upstream API has changed behavior, or the propagation gap is doing what propagation gaps do; the four data points let the maintainer figure out which.
Categories
- Bug reports: wrong lookup output, broken layout, browser-specific quirk.
- Tool requests: a single-purpose diagnostic you would like added (CIDR aggregator, IP range expander, reverse-DNS batch, etc.).
- Privacy and data: questions about which third-party APIs receive a request when a tool runs, or about analytics and advertising on the site.
- Editorial: a documentation or reference-text correction next to a tool.
- Partnership and embedding: using a NetChecks tool inside a runbook, an internal status page, or a knowledge base.
What we will not do
NetChecks does not provide individualized incident-response consulting, security audits, or active testing against systems you do not own. We will not look up information about a third party on your behalf, and we will not run a tool against a target you have not been authorized to test. Use the appropriate professional services for those needs.
Commitments
We read every message. We do not add you to a mailing list, share your email, or send unsolicited marketing. We fix reproducible lookup bugs quickly and we credit reporters in the release notes if they want it.