All free tools Looked up on the VPSLake server

IP Lookup

Find out which network owns an IP address or domain, where it is roughly located, its reverse DNS name and who holds the block at the registry. Paste up to 100 addresses for a bulk report.

Look up an IP or domain

IPv4 + IPv6
IPv4, IPv6 or a hostname. A domain is resolved to its A and AAAA records and each address is looked up.

Lookups run on the VPSLake server and nothing you enter is saved. Network and location come from a database on our own server; the server only resolves domain names and asks public DNS and the regional registries about the address. Private and reserved addresses are explained without any lookup.

Trace an address in four steps

Works for a single suspicious IP from a log line or a whole list exported from your firewall.

  1. 1

    Choose single or bulk

    Use Single for one IP or a domain name. Use Bulk to paste a list straight from last, fail2ban-client status, an access log or a firewall export.

  2. 2

    Run the lookup

    The server matches each address against its routing and location database and asks public DNS for the reverse DNS name.

  3. 3

    Read the network and location

    The AS name tells you whether traffic comes from a home ISP, a mobile operator, a cloud provider or a hosting company. Select the AS number to see every range that network announces.

  4. 4

    Act on it

    Copy the table or download CSV, then block the prefix, report abuse to the registry contact, or allow-list a partner's network.

What each field means

Network and AS number identify the autonomous system announcing the address in BGP, which is the company actually routing it. Prefix is the announced block it sits in. Reverse DNS is the PTR name the owner set; servers and mail hosts usually have a meaningful one.

Registered owner comes live from the regional internet registry (ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC). When it differs from the network, the block is usually leased or sub-allocated.

Investigating brute-force and bot traffic

Paste the top offenders from /var/log/auth.log, the Windows Security event log (event 4625) or your web server log. If most of them share one AS or one prefix, a single firewall rule for that range is cleaner than hundreds of single-IP bans.

Hosting and cloud networks rarely send human visitors, so a login page hammered from data-centre ranges is almost always automated.

Looking up a domain

Enter a hostname and the tool resolves its A and AAAA records the way a browser would, then shows the network behind each address. A site on Cloudflare or another CDN returns the CDN's edge addresses, not the origin server, so the network shown will be the CDN.

How accurate the location is

Country is right for the vast majority of addresses. City is an estimate based on where the provider registers or uses the block, so mobile and residential addresses can show a regional hub. Data-centre ranges are usually placed in the right city.

Use the results carefully

An IP address identifies a network, not a person. Shared addresses (carrier-grade NAT, VPN exits, corporate proxies) can put many innocent users behind one address, so test a block on a short timer before you make it permanent, and keep your own management address on an allow-list.

IP Lookup FAQ

The network (AS name and number) that routes the address, the announced prefix it belongs to, an approximate country and city, the reverse DNS hostname, and for single lookups the organisation and address range registered at the regional internet registry.
Type the domain into the single lookup box. The server resolves its IPv4 (A) and IPv6 (AAAA) records and shows the network and location of each. Private addresses in a public DNS answer are counted but not shown.
Up to 100 per bulk lookup. Paste them one per line or separated by spaces or commas. Duplicates are merged, invalid entries are listed separately, and the result can be copied or downloaded as CSV.
Ranges such as 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 100.64.0.0/10 and IPv6 fc00::/7 or fe80::/10 only exist inside local or provider networks and are reused everywhere. They have no public owner or location, so the tool explains the range instead of looking it up.
Reverse DNS is optional and set by whoever controls the address block. Home connections often have none or a generic name. If you run a VPS and need a PTR record for mail delivery, set it in your provider's panel; the change can take time to appear because answers are cached.
Yes, to keep the service quick for everyone: roughly 40 lookup credits per visitor every 10 minutes, where a single lookup costs 1 and a bulk lookup of 100 addresses costs 6. If you hit the limit, wait a few minutes.
AS numbers and prefixes come from iptoasn.com, built from global BGP routing tables. Locations come from the free DB-IP City Lite database (CC BY 4.0). Both are rebuilt weekly on our server. Registry owner data is fetched live over RDAP and cached briefly.