IP Address & ISP Lookup
Enter an IP address, domain or ASN to see who operates the network, where it is registered, how to report abuse, and whether the address belongs to a VPN, Tor or a datacenter — with every finding labelled by source.
🔒 Privacy: lookups run in your browser. The IP or domain you enter is sent directly from your browser to the public sources listed below; IGRS's own server never receives or logs your queries. Do not enter data you are not authorised to look up.
What this IP lookup tells you
Every public IP address is allocated by one of the five Regional Internet Registries (APNIC for India and the Asia-Pacific, ARIN, RIPE NCC, LACNIC and AFRINIC) to an organisation, and is announced on the internet by an Autonomous System (AS). This tool joins those public records into one view, so a single query answers the questions an investigator, SOC analyst or fraud team asks first:
| Field | What it means | How to use it |
|---|---|---|
| ISP / AS holder | The organisation that announces the address on the internet | The company to which a data request or abuse report goes |
| ASN and routed prefix | The network number and the block the address sits in | Pivot to other addresses in the same block or AS |
| Registry range and netname | The WHOIS allocation, sometimes naming a sub-customer | Shows when a block is leased to a hosting client or reseller |
| Abuse contact | The registry's abuse mailbox for the range | Where phishing, scanning or spam reports should be sent |
| Reverse DNS | The hostname the network owner set for the address | Often reveals server roles, VPN node names or ISP pool names |
| Approximate location | The city or region the network is associated with | A lead about the network, never a person's address |
| VPN / Tor match | Whether the IP is a published VPN server or a Tor relay | Explains why the trail stops at a provider rather than a subscriber |
How to read the verdict
Each finding is labelled so that it can be used carefully in a report. CONFIRMED means the address appears in a first-party list: a VPN provider's own published server list, or the Tor Project's relay directory. INDICATOR means a reasoned signal that needs corroboration, such as a network owned by a cloud or hosting company, or a name containing “VPN” or “proxy”. INFO is context, such as the address belonging to an Indian telecom operator. A clean result does not prove that a user was not hiding behind a VPN: lists are daily snapshots, smaller VPN brands are not covered, and residential-proxy services deliberately use ordinary home connections.
IP addresses in Indian investigations
- Mobile carriers share addresses. Indian mobile networks use Carrier-Grade NAT, so thousands of subscribers can share one public IPv4 address at the same moment. To identify a subscriber, the service provider needs the IP address, the source port and the exact timestamp with time zone. Ask platforms for all three.
- Lawful process. Subscriber details behind an address are obtained from the ISP or telecom operator by a notice under S.94 of the Bharatiya Nagarik Suraksha Sanhita, 2023, through the provider's nodal officer. Records produced for court need a certificate under S.63 of the Bharatiya Sakshya Adhiniyam, 2023.
- Log retention. CERT-In's directions of 28 April 2022 require service providers to keep ICT system logs for 180 days, and require VPN, VPS and cloud service providers to keep subscriber registration details for five years. Move quickly: older logs may no longer exist.
- Datacenter addresses. Fraud call centres, phishing kits and bots often run on rented servers. When the result shows a hosting company, the hosting company — not a telecom operator — holds the customer record.
Recording the result as evidence
Use Download report to save a plain-text report that records the query, the result, every source and the time of the lookup in IST and UTC. The page also shows the SHA-256 hash of that report so it can be noted in a case diary. Registration and routing data change over time, so the lookup time matters: an address can move between customers or providers within weeks.
Open data sources (all free, keyless)
| Data | Source | Terms |
|---|---|---|
| ASN, routed prefix, WHOIS, abuse contact, RIR | RIPEstat Data API — RIPE NCC | Free public API; IGRS identifies itself with sourceapp=igrs-xyz |
| Approximate location (city/region/timezone) | GeoJS (open-source project) and MaxMind GeoLite2 via RIPEstat | Free, no key |
| Reverse DNS, domain → IP | Cloudflare DNS-over-HTTPS | Free public resolver |
| Tor relays and exit nodes | Tor Project Onionoo | Free public API |
| VPN server IPs (NordVPN, Proton VPN, Mullvad, PIA, Surfshark, Windscribe, AirVPN, IVPN, OVPN, RiseupVPN) | open-source-vpn-ip-lists, built from data each provider publishes itself, refreshed daily | CC0 public domain |
The engine, iplookup.js, is plain JavaScript released under the MIT licence — read it, audit it, or reuse it in your own OSINT tooling. If you maintain an open dataset that would improve these checks, tell us and we will credit it here.
Frequently Asked Questions
For lawful investigation, security operations, research and awareness. Public network data describes networks, not people; confirm findings through official process before any action.
Step by step: from an IP in a log to a request
- Copy the IP and the exact timestamp with time zone from the log; IPs are reassigned, so the time matters as much as the address.
- Run the lookup and note the ASN and network owner — that organisation is who holds subscriber or customer records.
- Check the VPN, Tor and hosting findings. A datacenter or VPN result means the real user is one step further away.
- For Indian ISPs, request subscriber details for that IP and time through a notice under Section 94 of the BNSS; for hosting providers, request customer and access records.
- Correlate with other evidence — device identifiers, user-agents, login times — before attributing activity to a person.
Limits of IP geolocation
Geolocation databases estimate location from registration and routing data. City-level results are often wrong for mobile networks, which route many users through a few gateways, and for corporate networks that exit through a head office. Treat location as a lead, never as proof of where a person was.
Related: CIDR calculator · Email header analyzer · IOC lookup dashboard