API documentation

GET/POST interfaces

To get a list of domains for a given IP using a GET request:

https://www.dns-osint.net/reverse/your-token/ip-address

You might want to use regular POST queries and basic HTTP authorization instead. For that use application/x-www-form-urlencoded format for the request. The token must be encoded using Authorization: Bearer *token* header. For example:

curl -X POST -d "ip=8.8.8.8" -H "Authorization: Bearer your-token" "https://www.dns-osint.net/reverse"

Return values and codes

The returned response is always a JSON file, which contains the response or the error code. The response looks like:

{
  "status": "success",
  "data": ["example.com", "example.net"]
}
In case of an error the data field is missing and status comes with a reason field with a human readable error message:
{
  "status": "error",
  "reason": "quota exceeded"
}
HTTP error codes are used to better signal such errors. You might want to use them to detect certain situations in an automated way (without having to parse the status code or try to read the reason field.

Error codes
  • 200 No error
  • 400 The request is somehow malformed
  • 402 The token is no longer valid, needs to be renewed
  • 403 The token is valid but unknown
  • 429 There has been too many requests in the current window
Rate limiting is performed using a one hour window. Once you hit the limit you need to wait for the next hour for the rate limit to clear. You might consume all the quota in a few seconds or minutes or instead spread out the queries over the course of an hour.