Haryana Jamabandi: How to Use jamabandi.nic.in (2026 Guide)

What the Jamabandi Nakal Module Actually Shows You

The portal's homepage is organised around six core service areas: Property Registration, Jamabandi Nakal, Mutation, Query, Revenue Collection, and a Knowledge Base of reference material — a genuinely unusual design for a land-record system, since it means registration, mutation tracking, and record retrieval all sit inside one connected portal rather than being scattered across separate departmental websites, which is exactly the fragmented experience a buyer dealing with Uttarakhand or Himachal Pradesh's systems often runs into instead.

The document you're actually after is the Jamabandi Nakal (नकल) — a certified-format extract of the Jamabandi (जमाबंदी), the village-wide Record of Rights. A clean Nakal pull tells you three things the state revenue department currently has on record: who holds a given khewat/khasra entry, what its recorded classification and area are, and what — if anything — is noted against it as an encumbrance. It does not, by itself, confirm that a recent sale's mutation has actually completed, which is exactly why this guide treats the Mutation module as a separate, mandatory step rather than an optional extra — see Checking Mutation Status below.

For Farmland India's own mandate footprint specifically, this portal matters more than most: Palwal and Gurugram sit squarely inside Haryana's revenue system, and a Jamabandi Nakal pulled and cross-checked directly from jamabandi.nic.in is the baseline every serious parcel check in that corridor starts from — not a description relayed by a local contact.

Step-by-Step: Pulling a Jamabandi Nakal

The documented search flow for the Jamabandi Nakal module follows this sequence:

1. Open jamabandi.nic.in and select "Jamabandi Nakal" from the homepage's six main service categories, rather than Mutation or Query, which serve different purposes covered further down.
2. Select district, then tehsil, then village from the cascading dropdowns — the same three-level drill-down used across every corridor state, since a khewat or khasra number is only unique within one village.
3. Choose the Jamabandi year you want to view. Haryana's system lets you pull historical years, not only the current one — genuinely useful for seeing how an entry has changed across recent revision cycles rather than only its present state.
4. Pick your search method — by owner name, by khewat number, or by khasra number, depending on what reference you already have. A khewat number (the family/joint-ownership grouping specific to Haryana and Punjab) is useful when you're checking an entire holding; a khasra number is more precise when you're checking one specific plot against a sale deed.
5. Enter the relevant value and submit the search. Allow your browser to open a pop-up window if prompted — several accounts of this portal note the results display in a secondary window, which a browser's default pop-up blocker can silently suppress, making a genuine result look like no result at all.
6. Review the returned Nakal for the khatedar name(s) and share, khasra detail and area, land classification, and the encumbrance ("बोझ"/Bojh) column — read that last column most carefully, since it's the field most likely to be stale on an older printout.

One practical note worth carrying into this search: the portal's own stated technical guidance still references optimisation for Internet Explorer 6.0 at 800×600 resolution — a sign of a genuinely long-running system built well before mobile-first design was a consideration. If a dropdown won't populate, a pop-up doesn't appear, or a result page renders oddly on a phone, switching to a desktop browser is worth trying before assuming the record itself is unavailable.

Checking Mutation Status Before You Trust the Nakal

A Jamabandi Nakal only reflects whatever mutation has already been entered into the record — and registering a sale deed at the Sub-Registrar's office is a separate step, at a separate office, from mutating the Jamabandi itself. A buyer can hold a validly registered deed while the Nakal still shows the previous owner's name for weeks or months, which is exactly why checking mutation status directly, rather than assuming a recent transaction is already reflected, matters as much as the Nakal pull itself. This two-step gap is explained in full in our companion guide, Jamabandi and Fard Explained.

1. Navigate to the Mutation section of jamabandi.nic.in, separate from the Jamabandi Nakal module you just used.
2. Select district and tehsil, then the relevant identifying detail — commonly the registry number and registry date of the transaction you're checking, or the khewat/khasra reference, depending on which search option the module presents.
3. Complete the captcha where prompted, and submit the search.
4. Review the mutation's status — whether it's sanctioned (completed), still pending, or has been objected to by a co-sharer or other interested party. "Pending" or "objected" are not necessarily red flags on their own — mutation is a genuine administrative proceeding with a notice period — but either status means the Jamabandi Nakal you pulled does not yet reflect the transaction in question, and that's a fact worth putting directly to the seller.

In Haryana and Punjab specifically, mutation is sometimes referred to as intkal (इंतकाल) rather than the Hindi-belt term dakhil-kharij — the same underlying process, just a regionally different name for it. Either term, the practical point is identical: don't treat a clean-looking Nakal as proof a recent transaction has been fully absorbed into the record until you've separately confirmed its mutation status.

Registered Deed Search and Getting a Certified Copy

Because jamabandi.nic.in bundles Property Registration into the same portal as the land-record modules, it also supports a registered-deed search — useful for confirming that a sale deed a seller has shown you was, in fact, registered, rather than relying solely on their copy of it. The general pattern mirrors the Nakal and Mutation searches: select district and tehsil, then search by the registration details available to you (registry number and date are the most commonly used reference).

One distinction worth being precise about: what you view and print directly from the Jamabandi Nakal module online is explicitly a reference copy, not a certified document with the legal standing a bank, court, or Sub-Registrar's office will expect for a formal transaction. For a certified Nakal that carries that evidentiary weight, the established route is a request through the patwari or tehsil office directly — not a browser printout from the portal, even though the portal shows you the same underlying data. Treat the online pull as the verification step you do yourself, quickly and for free, and the certified copy as the separate document you obtain when the transaction actually requires one.

Common Issues: Legacy Interface, Pop-Up Blockers, and "Reference Only"

• Pop-up blockers suppressing results. As noted above, several documented accounts of this portal describe results opening in a secondary browser window. A modern browser's default pop-up blocker can silently prevent that window from appearing, which looks identical to "no record found" unless you know to check for a blocked pop-up first.
• A visibly dated interface. The portal's own technical notes reference Internet Explorer 6.0 and an 800×600 display — genuine evidence of how long this system has been running continuously, and a practical reminder that a desktop browser, rather than a phone, is the more reliable way to use it if anything behaves unexpectedly.
• Mistaking the free online view for a certified copy. Covered above, but worth repeating: the portal view is explicitly for reference. Anything requiring legal standing — a bank loan application, a court filing, a formal registration step — still needs a certified copy obtained through the patwari or tehsil.
• A mutation that looks stalled. A pending or objected mutation isn't automatically a dealbreaker, but it means the current Nakal doesn't yet reflect whatever transaction you're checking. Treat "mutation pending" as a specific, answerable question to put to the seller — has an application actually been filed, and what's the holdup — not as background noise to work around.
• Portal downtime during peak hours. A legacy government system serving an entire state's land records can be genuinely slower or briefly unresponsive at busy times. If a search times out, retrying — including on a different browser — is a reasonable first step before assuming the record itself is unavailable.
• Assuming the exact menu wording here matches today's live screen precisely. Government portal interfaces change without notice. Treat the steps in this guide as "expect something very close to this," and confirm current field labels live rather than assuming an option has been removed just because its exact wording has shifted.

Frequently Asked Questions