One Search, Fifteen Portals: How Automated Government Land Record Checks Work Across Indian States

If you have ever tried to verify a property across two Indian states, you already know the problem. The records exist. They are even online. But each state keeps them on its own portal, with its own login, its own search form, and its own name for the same document. A buyer checking land in Telangana uses Dharani. The same buyer, looking at a plot in Uttar Pradesh, has to learn Bhulekh. Karnataka means Kaveri and Bhoomi. Tamil Nadu means TNREGINET and TSLR. Nobody designed this maze on purpose. It is the byproduct of how land records are governed in India.

This article walks through why the fragmentation exists, which portal holds which record in which state, and what a unified search across those portals actually does. The harder question sits underneath all of it: when software searches fifteen government sites on your behalf, how do you know what it actually checked? Most automated tools do not tell you. That is the part worth fixing.

Why India's land records are split across so many systems

Land is a State subject. Under the Seventh Schedule of the Constitution of India, "land" and "rights in or over land" sit on the State List, which means each state legislates and administers its own land records. There is no single national land registry, and there was never meant to be one.

That single constitutional fact cascades into everything else. Each state runs its own revenue department, its own registration offices under the Registration Act, 1908, its own RERA authority under the Real Estate (Regulation and Development) Act, 2016, and its own court system feeding the eCourts platform. A property's full legal picture is scattered across four or five separate government systems, and those systems do not talk to each other even within one state, let alone across state lines.

So when you verify a title, you are not visiting one office. You are reconstructing a chain of evidence from revenue records, the sub-registrar's encumbrance data, the local body's tax and circle-rate tables, RERA registration data if the project is regulated, and pending litigation across district and high courts. Each lives somewhere different.

Which government portals should you check before buying property in India?

You should check, at minimum, the registration portal (for the encumbrance certificate), the revenue portal (for the record of rights), the local circle or guideline value table, the state RERA registry if the project is under a developer, and the eCourts system for pending cases tied to the property or its owners. The exact portal name changes with every state.

Here is what that looks like in practice, mapped state by state. The same document type carries a different name and lives on a different site depending on where the land sits.

That is ten states and already three different names for the encumbrance certificate, two for the record of rights, and a half-dozen valuation systems. Push the list to all 28 states and the naming chaos multiplies.

What each record type actually proves

The portal names are noise. The record types underneath are what matter, and there are only a handful that carry the legal weight.

An encumbrance certificate is a document issued by the sub-registrar's office that lists every registered transaction on a property over a stated period, including sales, mortgages, gifts, and liens. A clean EC tells you no registered charge sits against the property. It does not capture unregistered or oral transactions, which is why it is necessary but never sufficient on its own.

A record of rights, called pahani, RTC, jamabandi, khatauni, or 7/12 depending on the state, is the revenue department's running record of who holds the land, the extent, the crop, and the mutation history. It establishes possession and revenue-side ownership, which often differs from registered ownership when mutation lags behind a sale.

Circle rate or guideline value is the government's minimum valuation for a locality, used to calculate stamp duty. It will not tell you market price, but a sale registered below it is a flag. RERA registration, under the 2016 Act, confirms a regulated project is filed with the state authority and lets you pull its declared land status and approvals. Court records, surfaced through the eCourts system across roughly 18,000 courts, expose pending litigation that no revenue or registration portal will ever show you.

The black-box problem in automated title verification

Here is where automation usually goes wrong. Once a tool starts searching government portals for you, it becomes very tempting to hide the work. The user uploads a sale deed, clicks a button, and a report appears. Clean and fast. But what did the tool actually search?

This is not a hypothetical worry. If an automated verifier guesses the village name wrong, queries the neighbouring taluka, or silently skips a portal that was down that morning, the report still comes back looking complete. A missing search and a clean search produce the same green checkmark. The buyer cannot tell the difference, and neither can the bank ops team relying on the file for a loan decision.

For anyone in lending or due diligence, that is a real audit gap. A title report is evidence. Evidence you cannot trace back to its source is worth very little when a dispute surfaces two years later and someone asks which encumbrance certificate, for which survey number, on which date, the verification actually pulled.

The fix is not to slow automation down. It is to make every search visible. The user should see each portal the system intends to query, the exact location and survey parameters it resolved, and a chance to correct any of it before the report begins. Confirmation before execution, not a summary after the fact.

Unified government search, and why the transparency matters

Unified government search is a single interface that runs record searches across many state portals at once, while showing the user every search it plans to run and letting them edit and confirm each one before anything executes. The point is not just convenience. The point is that the convenience does not come at the cost of an audit trail.

This is the approach we took when building LegiScore's Unified Government Search. We had shipped automated title verification that searched the portals fast, but it had a black box problem. We removed it. The system now resolves every search in front of the user. It checks 15+ government portals spanning record-of-rights, encumbrance, valuation, RERA, and revenue-court data across states including Madhya Pradesh, Tamil Nadu, Uttar Pradesh, Rajasthan, Haryana, Karnataka, Gujarat, Telangana, and Andhra Pradesh, and it surfaces each intended query as an editable, confirmable step before the report starts.

One piece that mattered more than expected was fuzzy location matching. Indian place names are a nightmare to type exactly. "Dahisar (E)" and "Dahisar Borivali" should resolve to the same place, and a buyer should not have to know the portal's internal spelling. The matcher tokenizes what you type and ranks the closest village, taluka, and district combination first, so a partial or suffixed entry still lands on the right record instead of failing silently or, worse, matching the wrong village.

How async search and history reuse cut the repeat work

The other thing that breaks at scale is waiting. Government portals are slow, sometimes down, and occasionally geo-blocked. If a unified search runs every portal one after another and blocks the screen until all of them return, a single stalled portal holds the whole report hostage.

So the searches run asynchronously. Each portal query is submitted as its own job, runs independently, and reports back when it finishes, while a durable ledger records what was searched and what came back. A slow Haryana Jamabandi lookup no longer freezes a fast Gujarat 7/12 pull. From experience, this is the difference between a verification that completes in minutes and one that times out and forces a restart.

Search history is the quiet workhorse. Every search is stored with its human-readable parameters, so the next time you verify a property in the same village or for the same owner, you select from previous searches instead of retyping a survey number you have already resolved once. For a bank ops team running dozens of files in the same district, that reuse compounds fast.

Where this fits in a full title opinion

A unified portal search is the evidence-gathering layer. It is not the legal opinion. The opinion is the lawyer-grade reading of that evidence: whether the chain of title holds, whether the encumbrances are cleared, whether any pending case threatens the property, and whether the buyer should proceed.

LegiScore stitches the two together. The platform pulls government records across 15+ portals and 18,000+ courts across 28 states, then produces a full title opinion in under 15 minutes, at Rs.199 per title search. The unified search makes the inputs transparent and auditable; the opinion turns them into a decision. For an NRI buyer who cannot walk into a sub-registrar's office in Hyderabad, or a lending team clearing files across three states before lunch, that combination is the whole job.

Frequently asked questions

Is there one national portal to check land records across all Indian states? No. Because land is a State subject under the Seventh Schedule of the Constitution, each state runs its own record portals. Dharani (Telangana), Bhulekh (UP), Bhoomi/Kaveri (Karnataka), and AnyROR (Gujarat) are separate systems with separate logins and no shared search. A unified search tool queries them on your behalf, but the underlying records still live state by state.

What is the difference between an encumbrance certificate and a record of rights? An encumbrance certificate, issued by the sub-registrar, lists registered transactions like sales and mortgages over a period and proves whether registered charges exist. A record of rights, called pahani, RTC, jamabandi, or 7/12 depending on the state, is the revenue department's record of who holds and possesses the land. They often disagree when a mutation has not caught up to a registered sale, which is exactly why you check both.

Why does it matter that automated searches are user-confirmed? Because a skipped search and a clean search look identical in a final report. If you cannot see which portals were queried and with what parameters, a title report becomes evidence you cannot audit. User-confirmed searches let buyers and bank teams verify the inputs before the report runs, which matters when the file later has to defend a loan or a purchase decision.

Can I check pending court cases against a property online? Yes, through the national eCourts platform, which covers roughly 18,000 courts. Pending litigation will not appear on any revenue or registration portal, so court records are a separate and necessary check. LegiScore includes court-case search across 28 states as part of its title verification.

How fast and how much is a LegiScore title search? A unified government search across 15+ portals feeds into a full title opinion delivered in under 15 minutes, priced at Rs.199 per title search.

Related reading

• Dharani portal: how to check Telangana land records online
• Encumbrance certificate in India: a complete guide for property buyers
• Revenue records explained: pahani, 7/12, and khatauni
• RERA verification: check project registration state by state
• Check pending court cases on a property through eCourts
• Inside the AI title search engine: a 30-minute TSR