About WhoCalledLookup
WhoCalledLookup is an independent, free-to-use UK reverse phone lookup. We aim to give people a quick, accurate, no-signup way to answer who called me? — without surrendering personal data, paying a subscription, or wading through SEO-spam directory pages dressed up as search results.
What this site is for
The UK has more than a billion allocated phone numbers across over six hundred geographic dialling codes, dozens of mobile prefixes, and a long tail of non-geographic ranges (0800 freephone, 0345 / 0370 standard rate, 0844 / 0870 service, 09 premium-rate, 070 personal numbers). When a stranger calls, the digits on your screen are the only public clue you have. WhoCalledLookup turns those digits into something useful: the official Ofcom-allocated Range Holder, the dialling code's principal town, the number family (geographic, mobile, freephone, premium rate and so on), and the caller verdicts and community reports that other visitors have left about the exact number. It is a tool aimed at consumers, not at marketing or compliance teams; the design assumes you have ten seconds and a missed call.
Every URL on the site is a static, indexable document — there is no login wall, no captcha gate before results, no “upgrade to premium” tier. If you land on a lookup page from Google we want you to find what you came for, on that page, immediately.
Where the data comes from
Range-holder data is sourced from the official Ofcom Numbering Data feed, published weekly on Wednesdays under the Open Government Licence v3.0. We ingest the ZIP, stream-parse each CSV row, bulk-insert into a staging table inside Postgres, and atomically swap that table into production. The Range Holder, allocation status (Allocated, Reserved, Designated, Free, Quarantined), and dialling code are then surfaced on every lookup. Because the swap is atomic the site never serves a mixed snapshot of old-and-new ranges.
Area-code metadata — the principal town, region, and approximate population — is compiled from Ofcom’s National Telephone Numbering Plan and the ONS’ published mid-year population estimates. The classification engine that decides whether a number is a UK mobile, a freephone, a premium-rate number or a suspected scam uses the published numbering plan ranges as the source of truth.
Everything else on a lookup page comes from this site’s own community. Visitors can mark a number as scam, nuisance or safe in one tap, with an optional short comment, and those verdicts appear on the page for the next person the number rings. Comments are published automatically unless an automated filter rejects them (links, spam and crypto-wallet addresses are blocked). Moderated community reports — forum threads about that exact number, checked before they are published — are shown alongside. The 0–10 risk score counts a scam verdict at full weight and a nuisance verdict at half. We do not search the web, scrape other directories or send the number to any AI service.
How a number lookup actually works here
When you paste a UK number into the form, three things happen in parallel. First, the digits are normalised into E.164 format (+44...) using the same rules libphonenumber uses; this strips dashes, parentheses, leading zeros and the international prefix. Second, the normalised number is matched against our local copy of the Ofcom range table using a longest-prefix-match SQL query, so a number like 020 7946 1234 will match the most specific allocated 02079461 block before falling back to broader 020794 / 0207 / 020 prefixes. Third, the community verdicts and reports for that exact number are loaded and combined with the range-holder record into a short “What we know about this number” summary. If people have rated the number, the summary includes a 0–10 risk score based only on those verdicts; if nobody has, there is no score.
The whole page, summary included, is rendered on the server from data we already hold, so there is nothing to wait for after it loads. See database lookup vs community reports for the longer explanation.
What we don't do
- We do not buy or sell phone-number data, full stop.
- We do not store the raw IP address of visitors; the access log truncates the final octet for IPv4 and the last 80 bits for IPv6.
- We do not require you to create an account, give an email address, or confirm a phone number.
- We do not surface paid-for “premium” listings dressed as organic results.
- We do not let advertisers buy placement on individual lookup pages.
- We do not track which numbers an individual visitor has searched; analytics rolls up into per-day per-page totals only.
How we keep it accurate
Every Wednesday at 06:30 UTC our cron downloads the latest Ofcom ZIP, verifies the SHA-256 against the previous run, stream-parses the CSVs, bulk-inserts into a staging table, and atomically swaps it into production. If the archive hash hasn’t changed, we no-op and emit a metric. If parsing fails for any row we log the row, continue with the rest, and surface the parse-error count on the admin dashboard. You can see the date of the last successful ingest on the homepage footer.
Editorial pages — the long-form guides under /blog, the FAQ entries on area-code and holder pages, and this About page — are reviewed quarterly. Where a guide cites a specific Ofcom rule, statistory instrument, or third-party source, a citation link is included; if you find a citation that no longer resolves, please email the editorial address on the homepage footer.
Editorial standards
WhoCalledLookup follows three editorial principles. (1) Source the structured data from a single authoritative public dataset (Ofcom) rather than from scraped third-party sites. (2) Treat community verdicts as what other visitors have told us, not as a ruling — the verdict counts are shown next to the 0–10 risk score, the score is presented as a signal, not a label, and an unrated number gets no score rather than a reassuring zero. (3) Never publish a phone number with an editorial “suspected scam” flag unless the underlying community reports support that claim, and provide a clearly-marked correction route for callers who believe their number has been mis-categorised.
Who runs the site
WhoCalledLookup is built and operated by OmegaIT, a UK technology consultancy specialising in telecoms data, identity, and AI-powered consumer tools. Editorial direction and the lookup and community-moderation methodology are owned by Andrew Pickett, Managing Director, OmegaIT. The engineering, on-call, and content ops are split between OmegaIT’s in-house team and a small group of UK-based contributors. There is no parent media group, no venture-capital investor and no third-party data partnership behind the brand — the site is self-funded and ad-supported.
Affiliation
WhoCalledLookup is not affiliated with Ofcom, BT, EE, Vodafone, O2 / Virgin Media O2, Sky, TalkTalk, or any other UK communications provider. Ofcom’s data is published under the Open Government Licence v3.0 and is reproduced here under that licence; the OGL attribution and a link back to the Ofcom data page is preserved on every lookup result and on the SEO files index. Brand names appearing on holder pages are property of their respective owners and are used here for descriptive identification only.
Other countries
WhoCalledLookup covers UK numbers only, because the numbering data behind it is Ofcom’s. We run the same checks against each country’s own regulator elsewhere: WhoCalledLookup US (NANPA), Who Called Canada (CNAC), Wer hat mich angerufen? (Bundesnetzagentur) and Wer hat mich angerufen? Österreich (RTR). A number beginning +1, +49 or +43 will not resolve here, so those are the places to look it up.
Get in touch
For data corrections, takedown requests, press enquiries or editorial feedback, the contact details are on the OmegaIT parent-company website. Please cite the URL of the page in question and include the specific change requested; we aim to acknowledge within two working days and action verifiable corrections within ten.