A phone lookup can bring together several kinds of information, but they answer different questions. A valid number format does not identify a caller. A report describes somebody’s experience. A business source can establish a published association without authenticating the person contacting you.
This page explains those distinctions so you can judge a result on its evidence, rather than on how complete or confident it looks.
What the different sources mean
Scroll across to read all columns.
| Information | What it can tell you | What it cannot establish |
|---|---|---|
| Numbering metadata | A recognized number format and its numbering country; available type or regional context | Current ownership, a person’s whereabouts, or whether the number is active |
| Reviewed public business source | A business association supported by an identified public reference | That the person contacting you represents that business |
| Published community report | What a contributor says happened during a call or message | That every detail was independently verified or applies to later calls |
| Quick vote | A user’s brief safe/spam choice | A detailed account, verified rating, or substantive review |
| RevealNames search activity | Searches recorded by this website | Calls received, unique callers, or the number’s reputation |
Names or comments present in a private upstream cache are not automatically public evidence. They must not be read as another category of verified result simply because they exist in a source database.
How a number is matched
We use a phone-number parser to recognize supported numbering patterns and produce consistent formats. The international format helps distinguish numbers from different countries, while the national format may be easier to read locally.
Formatting differences do not necessarily mean two entries refer to different numbers. Spaces, brackets and country-code notation can change how the same number appears. Conversely, the country matters: entering a national number under the wrong country can point to a different record or produce an invalid input.
Parser validity is limited to numbering rules. It does not prove that a number has been assigned, is currently reachable, or belongs to a particular person. A mobile or fixed-line classification can also be uncertain; where the available classification covers both, a result should preserve that uncertainty.
Carrier, area and time zone information
Number pages resolve carrier and geographic context from the complete number using the installed libphonenumber metadata, through its PHP implementation. Coverage varies by number and country. The data release is identified on the page; loading a page does not perform a live carrier or subscriber check.
A carrier name, when available, describes the original number-range allocation. It does not confirm the network currently serving a number that has moved between providers. A missing carrier name means that our available source does not supply one; it does not mean that the number has no service provider. We do not infer a carrier from a city, an area code, or a private saved-contact label.
Geographic descriptions relate to a numbering range. Additional North American area-code information comes from a stored snapshot of the NANPA NPA database, with source links and a review date. An overlay means multiple area codes share coverage. The coverage and time zone do not identify a street address or a caller’s actual location. We do not use estimated population figures or an arbitrary major city as the location of an individual number.
Time zones describe the available geographic mapping. For mobile ranges without a local assignment, a mapping may cover the full international calling-code region; the page labels this broader scope. Nongeographic services such as toll-free numbers may have no useful local time zone. Named time zones can account for daylight-saving changes, whereas a fixed UTC offset may not.
Number type is also a range classification. Some ranges can be used for either fixed-line or mobile service, and the digits cannot distinguish them. A valid format or type does not prove that an individual number is active or supports a particular feature such as text messaging.
Business information and reported names
A published business association needs an identified public source, an observation date and publication review. The source and date help you inspect the basis for the association yourself. A business website may later change, and an older reference may no longer describe the current use of a number.
Names mentioned inside reports have a different meaning. A contributor might describe the name a caller used, the organization the caller claimed to represent, or a name the contributor recognized. Such a statement remains part of that report. It does not become a verified ownership record.
Neither form of name matching proves the origin of a particular call. Caller ID can be spoofed, and numbers can change users. Check an unexpected request through a trusted contact route rather than relying on a matching name alone.
Private imported information and stored copies
Some lookup information may be obtained through the WhoseNo upstream service or existing records associated with that service. The source chain can include saved-contact labels, imported number records and imported comments. A saved-contact label can be a nickname, a mistaken entry or an old association. It is not a carrier-verified identity.
A cached result is a stored copy of source information, not a new independent confirmation. The cache retains source details and retrieval information where available. An unknown original observation date remains unknown; fetching a record today does not make its underlying name current today.
Raw imported names, addresses, social links and comments are not automatically republished on number pages. Access to another service’s information is not, by itself, permission to publish it. Public business evidence and reports have their own review requirements. Imported view and vote counts also remain distinct from activity recorded by RevealNames.
Community reports and quick votes
A narrative report should describe a specific call or message in enough detail to be useful. New submissions wait for review. Before publication, review considers relevance, unnecessary personal information, advertising, duplicate content and unsupported allegations. An edited report needs review again.
Published reports are accounts from contributors. Review is a publication check, not identity authentication or proof that we witnessed the event. The category is the writer’s assessment, and readers should consider the circumstances and date alongside it.
Each approved narrative report counts once in its selected category. Where totals are displayed, the page identifies the sample and time period; number-page report totals cover all available dates. Quick safe/spam votes are separate. They do not contribute to narrative report totals or qualify a number for public search discovery.
No reports means there is not enough report evidence to make an assessment. It does not mean a number is safe, harmful, unused or unknown to everybody. Likewise, repeated searches can reflect curiosity, a missed call or a legitimate business interaction; a search count is not a complaint count.
Which records appear in public directories?
Public discovery requires useful information about the particular number. Suitable evidence can be a reviewed public business source or a substantive reviewed report. A name by itself, one quick vote, a popular search or a completed data retrieval is not sufficient.
A sparse record may remain available to somebody looking up that number while staying out of public directories and search listings. Records that are removed or suppressed should not continue exposing the withdrawn information through feeds or number pages. A private person’s name or address is never a requirement for making a page useful.
Being suitable for search publication is also different from appearing in Google. A search engine decides what to crawl and index; adding more generic text to a sparse number page does not create evidence about that number.
How to read dates and request a correction
The date of a search, a source observation, a data retrieval and a report submission can all differ. A review date tells you when publication review occurred. A substantive page update reflects a meaningful change in public content, rather than another page view.
If a source is missing, an association is outdated or a report needs context, request a correction. Identify the page and the disputed detail, and explain what should be checked. Our editorial policy describes the possible outcomes; the privacy policy covers data handling and retention.