Fifteen Portals, One Query: Inside Automated Land Record Search in India

Anyone who has checked a property in two Indian states knows the trouble. The records are there, and they are online. Yet each state publishes its records on a portal of its own, where you find a different login, a different search form and a different word for the same document. In Telangana, you use Dharani. For a plot in Uttar Pradesh, you must learn Bhulekh instead. Karnataka splits the job between Kaveri and Bhoomi, and Tamil Nadu between TNREGINET and TSLR. No one planned this maze. It follows from the way India governs land.

This piece covers why the records are split, the portal that holds each kind of record in each state, and what a single search across many of those portals actually does. Beneath it lies a harder question. If software queries fifteen government sites for you, how do you learn what it checked? Most automated tools never say, and that gap is what needs fixing.

Reasons Land Records Are Scattered Across Systems

The Constitution of India lists "land" and "rights in or over land" under the State List in its Seventh Schedule. So land is a State subject: each state makes its own laws and keeps its own records. No single national land registry exists, and the system was never meant to have one.

The rest follows from this. A state has a revenue department of its own and registration offices that work under the Registration Act, 1908. It also has a RERA authority set up under the Real Estate (Regulation and Development) Act, 2016, and courts that supply the eCourts platform. A property's complete legal position is thus spread over four or five government systems. Even in one state they do not share data, and across states they certainly do not.

Verifying a title therefore means going to more than one office. You assemble a chain of evidence from revenue records, encumbrance data held by the sub-registrar, the tax and circle-rate tables of the local body, RERA data when the project is regulated, and pending cases in district courts and high courts. All of these are kept in different places.

Portals to Check Before You Buy Property in India

The minimum list is as follows. Use the registration portal to get the encumbrance certificate, and the revenue portal to get the record of rights. Look up the circle or guideline value for the locality. Where a developer is behind the project, add the state RERA registry. Last, search eCourts for cases that involve the property or its owners. Portal names change in every state.

The table below shows how this looks state by state. The same type of document has a different name, and a different website, depending on where the land lies.

• Telangana · Primary portal(s): Dharani along with the urban EC service · Core record type: Combined land and encumbrance data · What it proves: Chain of ownership and registered charges
• Andhra Pradesh · Primary portal(s): Meebhoomi site · Core record type: Adangal and 1-B (the record of rights) · What it proves: Whether the land is cultivated and who possesses it
• Uttar Pradesh · Primary portal(s): Bhulekh, plus circle-rate tables · Core record type: Khatauni and circle rate · What it proves: Share of ownership and the government's valuation
• Karnataka · Primary portal(s): Bhoomi and Kaveri · Core record type: RTC (also called pahani) and mutation records · What it proves: Who holds the land, the crop, and transfers of ownership
• Tamil Nadu · Primary portal(s): TNREGINET, TSLR and the guideline value site · Core record type: Patta and chitta, EC, and guideline value · What it proves: Title, survey extent and valuation
• Madhya Pradesh · Primary portal(s): Bhu-Abhilekh, RCMS and RERA · Core record type: Khasra and khatauni, plus revenue cases · What it proves: Records of holdings and revenue disputes still pending
• Haryana · Primary portal(s): the Jamabandi site · Core record type: The record of rights · What it proves: Ownership and the history of mutations
• Maharashtra · Primary portal(s): MahaBhulekh and IGR · Core record type: The 7/12, the property card, and the EC · What it proves: Ownership in rural and urban areas, and encumbrances
• Rajasthan · Primary portal(s): Apna Khata, RIICO and RERA · Core record type: Jamabandi and industrial allotment · What it proves: Holdings, and whether an industrial plot has been allotted
• Gujarat · Primary portal(s): AnyROR and e-Milkat · Core record type: The 7/12, 8A and the property card · What it proves: Holding records for rural and urban land

Ten states already give us three names for the encumbrance certificate, two for the record of rights and half a dozen valuation systems. Extend the list to all 28 states and the confusion only grows.

What Each Type of Record Establishes

Portal names do not matter much. A handful of record types carry the legal weight, and those are what you should understand.

An encumbrance certificate comes from the sub-registrar's office. For a stated period it lists each registered dealing in the property, including sales, mortgages, gifts and liens. A clean one means no registered charge stands against the property. Oral and unregistered dealings are missing from it, so the EC is always necessary and never sufficient on its own.

Depending on the state, the record of rights is called pahani, RTC, jamabandi, khatauni or 7/12. The revenue department keeps it up to date with the holder, the area, the crop and the history of mutations. It reflects possession and ownership from the revenue side. If the mutation has not caught up with a sale, it can name someone other than the registered owner.

For stamp duty, the government fixes a minimum value for each locality, called the circle rate or guideline value. It is not the market price, yet a sale registered under it is a warning sign. RERA registration under the 2016 Act confirms that a regulated project is filed with the state authority, and its declared land status and approvals can be pulled. Court records arrive through eCourts, which covers around 18,000 courts, and they expose litigation that neither the revenue nor the registration portal reveals.

The Black-Box Problem in Automated Title Checks

This is where automation usually goes wrong. After a tool starts searching the portals on your behalf, it is tempting to conceal the work. The user uploads a sale deed and clicks, and a neat report appears quickly. What did the tool actually search, though?

The worry is real. Suppose it guesses the wrong village name, queries the neighbouring taluka, or silently passes over a portal that happened to be down. The finished report still appears complete. A search that never ran and a search that came back clean both produce the same green tick. The buyer cannot tell them apart, and neither can the bank operations team that relies on the file for a loan decision.

Lenders and due-diligence teams face a real audit gap here. A title report is evidence, and evidence with no traceable source is worth little. A dispute may surface two years later, when someone asks which encumbrance certificate was fetched, for which survey number, and on what date.

Slowing the automation is not the answer. Making each search visible is. The user should see, before the report starts, which portals the system plans to query and what location and survey parameters it settled on, and should be free to correct any of them. Confirmation belongs before the run and not in a summary written afterwards.

Why Transparent Unified Search Matters

By unified government search, we mean one interface that runs record searches on many state portals at the same time. It lists every search it plans, and the user edits and confirms each before anything runs. Convenience is not the only aim. The convenience must also leave the audit trail intact.

This is the thinking behind LegiScore's Unified Government Search. Our earlier automated title verification searched the portals fast, but it worked as a black box, and we took that out. Now every search is resolved while the user watches. The system reaches 15+ government portals holding record-of-rights, encumbrance, valuation, RERA and revenue-court data, in states such as Madhya Pradesh, Tamil Nadu, Uttar Pradesh, Rajasthan, Haryana, Karnataka, Gujarat, Telangana and Andhra Pradesh. Before the report begins, each intended query is shown as a step to edit and confirm.

Fuzzy location matching proved more important than we had thought. Indian place names are hard to type exactly. "Dahisar (E)" and "Dahisar Borivali" ought to resolve to one place, and nobody should have to know a portal's own spelling. The matcher splits what you type into tokens and puts the closest village, taluka and district combination at the top. Even a partial or suffixed entry finds the correct record. It does not fail quietly or, worse, pick the wrong village.

Async Searches and Reuse of Past Searches

Waiting time also breaks things at scale. Government portals can be slow, are sometimes down, and are occasionally blocked by location. A unified search that visits portals in sequence and locks the screen until every one answers lets a single stalled portal hold up the whole report.

For that reason the searches are asynchronous. A portal query is sent as its own job, works independently and reports back when finished, and a durable ledger keeps a record of what was searched and returned. A slow Haryana Jamabandi lookup does not delay a quick Gujarat 7/12 pull. From what we have seen, this decides whether a verification ends in minutes or times out and has to restart.

Search history does much of the quiet work. Every search is stored with readable parameters. Next time you verify a property in the same village or for the same owner, you choose from earlier searches rather than retyping a survey number already resolved. For a bank operations team with dozens of files in one district, the saving adds up quickly.

Place in a Complete Title Opinion

Unified portal search is the layer that collects evidence, and it is no substitute for the legal opinion. A lawyer reads the evidence and answers whether the chain of title holds, whether the encumbrances are cleared, whether a pending case endangers the property, and whether the buyer should proceed.

LegiScore links the two steps. It gathers government records from 15+ portals and 18,000+ courts in 28 states, then delivers a full title opinion in under 15 minutes at Rs.199 per title search. The unified search keeps inputs open to audit, and the opinion converts them into a decision. Consider an NRI who cannot visit a sub-registrar's office in Hyderabad, or a lending team clearing files from three states before lunch. This pairing is the whole job for each of them.