WHOIS Lookup

What this checks

• For domains: registrar, registrant (if public), creation and expiry dates, name servers, and abuse contact.
• For IP addresses: network name, RDAP handle, CIDR/allocation range, country, allocation date, status, and abuse contact.
• Input type is auto-detected — IP literals run an IP RDAP query, everything else runs a domain query.

How to interpret results

• An imminent expiry date on a domain can explain outages or hijack risk.
• The IP network name and abuse contact show which organization controls an address block and where to report misuse.
• An IP allocation far from the expected country can indicate a proxy, VPN, or relocated hosting.

Common issues

• Registrant and contact fields are frequently redacted for privacy and may show as not available.
• Some ccTLDs and legacy IP ranges expose limited RDAP data.

WHOIS and RDAP for domain and IP lookups

This lookup accepts either a domain or an IP address and routes the query to the correct registration workflow automatically. Domains return registrar, dates, name servers, and public ownership fields when available. IP addresses return allocation range, registry, owner, RDAP handle, status, and abuse contact information.

The data comes from RDAP-first sources wherever possible. RDAP is the modern, structured replacement for older WHOIS text responses, which makes it better for parsing ownership, contact, and event fields consistently across domain and IP records.

How to interpret domain registration data

Creation, expiry, registrar, and name-server data are useful for establishing who controls a domain and whether its registration is healthy. Near-term expiry dates, unexpected registrar changes, or mismatched name servers can explain outages, hijacks, or stale DNS behavior.

Public registrant details are often redacted, so a missing name is not unusual. The most useful surviving fields are usually the registrar, dates, name servers, and abuse or contact channel.

• Use name servers and registrar data to confirm operational ownership.
• Treat redaction as normal privacy policy, not as proof the data is wrong.

How to interpret IP ownership data

An IP WHOIS lookup identifies the organization responsible for the address block, not the person using one address inside it. The CIDR range, RDAP handle, registry, and abuse contact help you understand which provider owns the space and where incident reports should go.

This is especially useful for IPv6 and large cloud allocations because a single network can represent many subnets and services. Cross-check the result with ASN Lookup, Reverse DNS Lookup, and IP Owner Lookup when you need more routing or hosting context.

• Owner and abuse fields usually describe an ISP, cloud provider, or enterprise network.
• Allocation country can differ from the apparent geolocation of traffic using the address.

Privacy note

WHOIS/RDAP queries run server-side against public registries and the entered domain or IP is not stored beyond serving the request.

Frequently Asked Questions

Can I look up both domains and IP addresses?

Yes. Enter a domain (example.com) for registrar, registrant, creation/expiry dates, and name servers, or an IPv4/IPv6 address for the network name, CIDR allocation, country, and abuse contact.

How do I run a WHOIS IP lookup?

Enter a public IPv4 or IPv6 address and the tool will switch from domain registration mode to IP registration mode automatically. The IP result focuses on the network owner, allocation range, registry, RDAP handle, status, and abuse contact instead of registrar fields.

Why is the registrant or owner redacted?

Since GDPR, most registries redact personal registrant details in public WHOIS/RDAP. Registrar, dates, name servers, and abuse contacts usually remain visible.

What is the difference between WHOIS and RDAP?

RDAP is the structured successor to legacy WHOIS. It uses machine-readable JSON, standardized contacts, and bootstrap discovery, which makes it better for modern domain and IP registration lookups while still serving the same core ownership and allocation purpose.

Can WHOIS identify a private person behind an IP?

Usually no. IP WHOIS and RDAP identify the organization or ISP responsible for the address block. They do not reveal the private subscriber or street address behind a normal consumer connection.