Free Tools
Ten tools answer a question about an address, a domain or a network without an account and without a key. They run the same checks the paid integrations run, against the same data, and they are the quickest way to see what ReportedIP knows before writing a line of code. Every one of them is also a REST endpoint, documented under Tools API.
Which tool answers which question
| Question | Tool | Input |
|---|---|---|
| What does DNS return for this domain, worldwide? | DNS Checker | Domain |
| Can someone send mail as my domain? | Email Security Check | Domain |
| Is this address on a blacklist, and which one? | DNSBL Blacklist Check | IPv4, IPv6 or domain |
| Why is my mail server refused at the door? | Reverse DNS | IPv4, IPv6 or hostname |
| Where do I report an attacker so it lands? | Abuse Contact | IP or domain |
| Was that really Googlebot? | Bot Verification | IP, optional User-Agent |
| Should I block one address or the whole range? | ASN Report | IP or AS number |
| How is this site hardened? | Security Headers | Domain or URL |
| What does a website learn about me? | What We Know About You | Nothing, it reads the request |
| What is attacking systems right now? | Honeypot Server | A host you run yourself |
All of them are listed at reportedip.com/tools.
The daily limit
The nine browser tools share one budget. It is counted per identity and per calendar day, and it resets at midnight in the server's timezone:
| Caller | Checks per day | Counted against |
|---|---|---|
| No account | 30 | Client IP address |
| Signed in | 100 | User ID |
| Administrator or editor | Unlimited | Not counted |
Two details matter when a tool is used from a script. A check counts when it runs, not when it
succeeds, so a malformed request that reaches the validator still costs one. And results are
cached for 90 seconds per query, so repeating the same lookup inside that window returns the
stored answer and costs nothing. Exceeding the budget returns HTTP 429 with the error code
rate_limit_exceeded; the counter is a daily one, so there is no Retry-After to wait
out beyond midnight.
The limit is shared across all tools on purpose. It exists to keep the tools usable for people troubleshooting a problem, not to meter them. Anything that needs volume belongs on the main API, where a key raises the daily quota to 1,000 checks and above.
What is stored
- The query is not stored against you. The rate limit keeps a counter under a hash of your address or your user ID, and the counter holds a number, not a list of what was looked up.
- Results are kept for 90 seconds in a shared cache keyed by the query itself, so a second person asking the same question inside that window gets the same answer without a second lookup.
- Nothing is sent to the address you look up. The tools read DNS, the public registries and, for the header check, the site you name. An address in the input field is never contacted, and no report is filed on your behalf.
- The privacy tool stores nothing at all. What We Know About You shows the request back to you and keeps none of it.
- Check results feed the usage statistics, aggregated by check type. Which domain or address was checked is not part of that record.
Where the community data comes from
Three tools, the blacklist check, the abuse contact lookup and the ASN report, enrich their answer with what the community database holds about an address. That data is the same set the API serves: reports from Hive installations, honeypot servers and fail2ban actions, scored by the method described under Confidence Score.
The tools never expose more than the API does. The ASN report in particular is aggregate only: it states how many addresses of a network appear in the data and how often they are reported, and it does not list them. A single address is looked up on its own page.
Next
- Tools API for the seventeen endpoints behind these pages, with parameters and response shapes.
- Verification Methods for how the checks actually work, and where a naive implementation goes wrong.
- Tool Scoring for every weight behind the email and header scores and the network ranking.
Last updated: · Maintained by the ReportedIP team