Reverse IP API — /api/v1/ip/reverse

Same as `/api/v1/domain/reverse` but exposed under the IP namespace for discoverability. Returns the PTR record or a graceful 'no record' message.

• Method GET
• Path /api/v1/ip/reverse
• Stability STABLE
• Version v2026-05-15
• Summary PTR lookup for an IP address.

Pass these as query-string parameters (or, where indicated, in the request headers). Required params marked required.

• ip (required) — string IPv4 or IPv6 address.

All successful responses follow the standard `{ success: true, data: {...} }` envelope. Notable fields on the data object for this endpoint:

• data.data[] — array<object> PTR records when present.
• data.message — string Set when no record exists (`No RDNS … records found`).
• data.error — string Set when no record exists (`ENODATA`).

Truncated but representative example for a real lookup:

{
  "success": false,
  "data": {
    "message": "No RDNS 8.8.8.8 records found",
    "error": "ENODATA"
  }
}

Errors return HTTP status codes paired with stable machine-readable codes. Match on the code field rather than the human-readable message.

• 400 INVALID_IP Not a valid IP.

Patterns we recommend when integrating this endpoint:

• Treat the `error: 'ENODATA'` shape as an expected outcome, not a failure.