Network

IP Address Lookup Guide: Read Address Scope, Reverse DNS and PTR Results

·

ToolMellow’s IP address lookup inspects one address you supply. It shows its normalized spelling, IPv4 or IPv6 family, address scope and generated reverse-DNS query name. When its policy classifies the address as public, it also requests PTR records from Cloudflare or Google Public DNS and displays the returned names and TTL values.

Use these results to understand an address in a configuration or log and decide what to investigate next. This workspace does not locate a person, identify an ISP, list every website on a server or test whether the address is reachable. A classification and a DNS answer each describe a specific piece of information; neither proves who is behind a connection.

IP address lookup

Start with one address and choose a DNS provider

Enter a bare IPv4 or IPv6 address in IP address. Cloudflare is selected initially; choose Google Public DNS if you want that provider’s view. Select Look up address to submit the request. The field does not automatically detect your connection’s address. Use What Is My IP first if discovering the address seen by the website is your task.

Read the normalized address, family and scope before interpreting reverse DNS. For an eligible public address, the results also show DNS status and any PTR records. For a private or special-use address, the page shows a notice explaining that no public-resolver query was made. Its generated reverse name still appears, but that name is a query address, not evidence that a PTR record exists.

  • Supply one address without a URL, hostname, CIDR prefix, port or zone identifier.
  • Choose one provider and run the lookup; selecting another provider alone does not submit a query.
  • Read status alongside the returned names, and use DNS Checker for a separate forward-DNS check.

RFC 1035: PTR records, reverse zones and TTLRFC 3596: IPv6 reverse lookup under ip6.arpa

Use a literal address rather than a URL or network range

IPv4 input uses four decimal octets, such as 192.0.2.1. Leading-zero octets such as 192.000.2.1 are rejected. IPv6 can use compressed or expanded hexadecimal notation, including uppercase letters. Do not add square brackets, a hostname, a URL scheme, a CIDR suffix such as /64, or a zone identifier such as %eth0. A bare IPv6 address ending in :80 can itself be a valid address; those digits are not automatically treated as a port.

The field accepts at most 80 UTF-16 code units. The server checks that submitted length before trimming surrounding whitespace and parsing the address. Spaces therefore still consume the allowance even when trimming would leave a valid address. Valid address characters are ASCII, so one such character occupies one unit; the allowance does not make arbitrary Unicode text a valid IP. Submit one literal rather than a list or a padded string.

Use a literal address rather than a URL or network range
Input exampleInterpretation hereUseful action
192.0.2.1Valid IPv4 documentation address; special-use scopeUse it to inspect classification without a public PTR query.
2001:0DB8:0:0:0:0:0:1Valid IPv6; normalized to 2001:db8::1Different spellings can represent the same address.
::ffff:192.0.2.1Mapped address normalized to IPv4 192.0.2.1Expect IPv4 family and an in-addr.arpa reverse name.
https://192.0.2.1/ or 192.0.2.1:443URL or IPv4 address with port; rejectedRemove the surrounding URL or port.
2001:db8::/64 or fe80::1%eth0Network prefix or zone-qualified address; rejectedSupply a single unqualified address when appropriate.

Node.js: IP address parsing and leading-zero restrictionsRFC 4291: IPv6 text forms and IPv4-mapped addressesRFC 5952: Canonical IPv6 text representation

Understand why the displayed spelling can change

Normalization makes equivalent IPv6 text easier to compare: hexadecimal letters become lowercase and eligible zero runs are compressed. The expanded example 2001:0DB8:0:0:0:0:0:1 therefore appears as 2001:db8::1. This changes the written representation, not the underlying address. It does not convert an IPv6-only endpoint into an IPv4 endpoint or test its network configuration.

IPv4-mapped IPv6 is handled separately. Both ::ffff:192.0.2.1 and its hexadecimal equivalent ::ffff:c000:201 become 192.0.2.1 here. The result then uses IPv4 family, IPv4 scope rules and an IPv4 reverse name. That behavior applies to the mapped form; it is not a promise that every IPv6 address containing an embedded IPv4 value will be reduced to IPv4.

RFC 4291: IPv6 text forms and IPv4-mapped addressesRFC 5952: Canonical IPv6 text representation

Treat scope as a lookup policy, not a reachability test

The scope labels distinguish public, private, shared, loopback, link-local and special-use addresses. For example, 10.0.0.1 is private, 100.64.0.1 belongs to shared address space, 127.0.0.1 is loopback and 169.254.1.1 is link-local. Documentation addresses such as 192.0.2.1 are special-use. Being outside the familiar private IPv4 ranges does not automatically make an address publicly usable.

ToolMellow uses a conservative policy to decide whether to send a public PTR query. Its labels are not an exhaustive reproduction of every IANA allocation or a routing test. For IPv6, it excludes entire special parent ranges such as 2001::/23, including some more-specific assignments with different registry properties. Public means eligible under this tool’s policy; it does not guarantee a route, a responding host, an open port or a usable service.

IANA: IPv4 special-purpose address registryIANA: IPv6 special-purpose address registry

Keep private DNS questions within the right network

Every submitted address reaches ToolMellow’s server, including a private address. When the scope is not public, that server returns the classification and reverse name without sending the reverse query to Cloudflare or Google. The workspace shows its private-or-special-use notice rather than a DNS status line. This is a decision not to query; it is not an answer saying that no local PTR record exists.

A home router, business network or VPN can have its own private DNS records. A public resolver does not provide the same view as that network’s configured resolver, and this workspace does not query your local resolver. If you are troubleshooting an internal host, use the approved DNS tools and resolver for that network. A local administrator may be able to explain a private reverse zone that a public lookup cannot assess.

IANA: IPv4 special-purpose address registryIANA: IPv6 special-purpose address registryRFC 1035: PTR records, reverse zones and TTL

Separate the generated reverse name from a returned hostname

An IPv4 reverse query reverses the four octets and appends in-addr.arpa. For 192.0.2.1, the generated name is 1.2.0.192.in-addr.arpa. This is a worked naming example, not a live PTR result: the documentation address is special-use and is not sent to a public resolver by this tool. The name can be constructed even when no corresponding DNS record exists.

IPv6 uses a different namespace. Expand the address to 32 hexadecimal digits, reverse those individual digits, separate them with dots and append ip6.arpa. Reversing whole hextets would be incorrect. A PTR answer is a hostname stored at the resulting reverse-DNS name; it is distinct from that generated query name. The workspace displays PTR answer rows, not every record or authority detail present in the provider’s response.

RFC 1035: PTR records, reverse zones and TTLRFC 3596: IPv6 reverse lookup under ip6.arpa

Read the status before deciding why no PTR appeared

A missing PTR list has several possible explanations. NXDOMAIN concerns the queried DNS name or a final alias target, not whether the IP is assigned or a host is online. NODATA describes a successful DNS response without the requested record type; it is not a separate DNS response code. Here that label is used when a response with code zero contains no PTR answer and includes an SOA authority record.

For other code-zero responses without a PTR, this implementation uses ALIAS_ONLY when it receives a CNAME answer, REFERRAL when authority contains NS records, and EMPTY_ANSWER otherwise. These are application interpretation labels, not additional standard DNS response codes. Check the status even when the page also says that no PTR record was returned. An HTTP failure, malformed reply or timeout does not establish the absence of a DNS record.

Read the status before deciding why no PTR appeared
Displayed statusWhat it supportsUseful next step
NOERROR with PTR rowsThe accepted response contains PTR answer dataRead the names and TTL; separately verify any forward mapping you need.
NXDOMAINThe DNS response reports a nonexistent nameCheck the literal address and consult the responsible DNS operator if a record is expected.
NODATACode zero, no PTR answer and an SOA authority record hereTreat the missing requested type separately from a failed request.
ALIAS_ONLY / REFERRAL / EMPTY_ANSWERAn accepted reply did not contain a PTR under these parser rulesInvestigate DNS data separately; the tool does not perform its own follow-up chain.
SERVFAIL / REFUSEDThe resolver reports a DNS failure or refusalRetry later or compare the other provider without assuming the address is invalid.
HTTP_ERROR / TIMEOUT / MALFORMED_RESPONSE / UPSTREAM_ERRORThe request or response could not produce usable DNS resultsCheck connectivity and retry later; absence of PTR has not been established.

RFC 1035: PTR records, reverse zones and TTLRFC 2308: Negative DNS answers and cachingCloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Use TTL and provider comparison carefully

Each PTR row shows the TTL supplied in the accepted DNS response, in seconds. A recursive resolver can return a remaining cache lifetime rather than the original value set by the operator. TTL is not the age of the record, the duration of an address lease, lookup latency or a guarantee that a hostname is accurate. The displayed number does not count down automatically while you watch it.

Cloudflare and Google can have different cached answers or encounter different upstream conditions. After changing provider, select Look up address again; the selection clears the previous result and error without submitting a request. Compare the same address and record type, and record when you checked. A difference alone does not identify the correct answer or prove that a recent DNS change has finished propagating everywhere.

RFC 1035: PTR records, reverse zones and TTLRFC 2308: Negative DNS answers and cachingCloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Verify forward DNS separately when it matters

A PTR hostname is data maintained in the reverse-DNS hierarchy. Forward A and AAAA records are maintained separately and can disagree with it. A returned hostname therefore does not prove that its forward records point back to the original address, that the hostname’s operator owns that address, or that a particular person used it.

If your task requires agreement, take the returned hostname to DNS Checker and inspect its A records for IPv4 or AAAA records for IPv6. Compare the resulting addresses with the original normalized address. That is a separate observation; IP Lookup does not perform forward-confirmed reverse DNS automatically. Even agreement is DNS consistency evidence, not authentication or a complete email-delivery assessment.

RFC 1035: PTR records, reverse zones and TTLRFC 3596: IPv6 reverse lookup under ip6.arpa

Recover from invalid input or an interrupted request

During a request, the address field and provider selection are disabled and Cancel is available. The provider request has an eight-second timeout, while the browser request has a twelve-second deadline. Cancel stops waiting for the current request and makes the controls available again; it cannot undo a query that has already reached the server or provider. A later attempt is a new request.

An invalid-input response asks for an IPv4 or IPv6 address. Other HTTP failures, including a temporary service or request-limit response, use the generic lookup-failed message. Some accepted DNS failure results also show that alert alongside the classification and DNS status. Editing the address or changing provider clears the old result and error. Do not repeatedly resubmit a failing request without first checking its input and the displayed status.

Recover from invalid input or an interrupted request
ObservationCheckNext action
Look up address is disabledThe field may be blank or a request may be runningEnter a nonblank literal, or wait for or cancel the current request.
The page asks for IPv4 or IPv6The input may contain a URL, port, prefix, zone or invalid octetUse one bare address and keep the full submitted input within 80 units.
A private-or-special-use notice appearsPublic lookup is intentionally withheld for that scopeUse an appropriate local resolver for an internal DNS question.
No PTR record was returnedRead the accompanying DNS statusDistinguish missing DNS data from a timeout, refusal or failed response.
Changing provider removes the resultChanging a control resets the previous observationSelect Look up address to query the new provider.
A lookup fails repeatedlyInput, connectivity, provider failure or service limits may be involvedPause, verify the input and retry later; compare providers when useful.

Cloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Choose a different source for a different question

IP lookup services can offer very different kinds of data. Some combine geolocation databases, allocation records or ASN information. ToolMellow’s workspace provides address classification and reverse DNS; it does not include those databases, WHOIS, ISP identification, port scanning or a precise-location map. A geographical word in a PTR hostname is not a verified location measurement.

Reverse DNS also does not enumerate every website hosted on an address. Shared hosting, load balancers and other configurations can serve many names without listing them in PTR records. For ownership, routing, service availability or an application incident, identify the separate source and method your question requires. Keep the exact address, time, provider and status with any lookup observation so another investigator can understand its limits.

IANA: IPv4 special-purpose address registryIANA: IPv6 special-purpose address registryRFC 1035: PTR records, reverse zones and TTL

Understand where the request goes and how long the view lasts

This lookup is a server-backed network operation. ToolMellow receives the submitted literal; for a public-classified address, the selected resolver receives the generated reverse name, which represents that address. The request comes from ToolMellow’s server rather than your local DNS resolver. DNS over HTTPS protects that transport, but it does not hide the query from either service or establish a data-retention promise.

The workspace has no account requirement, saved lookup history, dedicated result-copy control or export. The current result lasts until another action clears or replaces it, or the page reloads. The page also loads normal site assets and analytics. If you need a record, capture the relevant displayed facts yourself; do not treat the absence of a history button as a guarantee that no server or provider can retain request data.

Cloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Frequently asked questions

What does this IP address lookup show?

It shows the normalized address, IPv4 or IPv6 family, scope and generated reverse-DNS name. Addresses classified as public are also queried for PTR records through the selected provider. It does not show geolocation, WHOIS or ISP data.

Can I enter a domain name or URL?

No. Supply one bare IPv4 or IPv6 address. Remove URL syntax, ports, brackets, CIDR suffixes and zone identifiers. Use DNS Checker for a hostname’s forward records.

Why did my IPv6 address become an IPv4 address?

An IPv4-mapped IPv6 form such as ::ffff:192.0.2.1 is normalized to 192.0.2.1. It then uses IPv4 family, scope and reverse-name rules. Other IPv6 forms are not all converted this way.

Why is a private address not sent to the public resolver?

The policy withholds public PTR queries for nonpublic scopes. The submitted address still goes to ToolMellow’s server for classification. A private network may have local DNS records that this public-provider workspace cannot inspect.

Does public scope mean the host is reachable?

No. Public is a conservative query-eligibility label here. The tool does not test routing, open ports or service availability, and its scope policy is not a complete mirror of every registry exception.

Is the reverse DNS name the same as a PTR hostname?

No. The generated in-addr.arpa or ip6.arpa name is the DNS name being queried. A PTR hostname is data returned for a reverse name. Constructing the query name does not establish that a PTR exists.

Does NXDOMAIN mean the IP address does not exist?

No. It reports a nonexistent DNS name or final alias target in the response. It does not prove that the address is unassigned, the host is offline or a connection never occurred.

What does the TTL beside a PTR record mean?

It is the returned cache lifetime in seconds and may be the remaining lifetime at the recursive resolver. It is not record age, latency or an address lease. The displayed TTL does not automatically count down.

Why do Cloudflare and Google return different results?

Their caches or upstream outcomes can differ. Compare the same normalized address and status at a recorded time. Changing the provider clears the result; select Look up address to run a fresh request.

Does a PTR record prove that a domain points back to the address?

No. Query the returned hostname’s A or AAAA records separately and compare the addresses. Forward and reverse zones can disagree. Even agreement does not identify a person or authenticate a service.

Does Cancel erase an already submitted query?

No. It stops the current browser request and restores the controls. A server or provider may already have received the query. Cancellation is not a deletion or retention guarantee.

Can I save a result or find every website on the address?

The workspace has no saved history or dedicated export, and PTR lookup does not enumerate hosted websites. Record the displayed address, provider, time, status and relevant names separately when you need an investigation note.

Sources and further reading

Put it into practice.

Related guides