Banglarbhumi CAPTCHA not working — why, and what to do

Why there's a CAPTCHA on every single search

Banglarbhumi asks for a CAPTCHA on searches, not just on sign-in. That surprises people, because on most websites a CAPTCHA guards the login form and then leaves you alone. Here it sits in front of the lookup itself, so checking five plots means solving five CAPTCHAs.

The department has not published its reasoning, and we are not going to guess at it. What matters practically is that the placement is deliberate rather than a bug: it is where the portal puts it, and no amount of troubleshooting on your side will remove it.

What troubleshooting can do is stop it failing when you have entered it correctly — which is a different and much more solvable problem.

The five reasons a correct CAPTCHA gets rejected

If you are confident you read the image right and the portal still refuses, one of these is almost always the cause.

• Case sensitivity. Treat the code as case-sensitive unless you know otherwise. A code shown as `aB7kQ` will not accept `AB7KQ`. On phones this is the single biggest cause of failure, because most Android keyboards auto-capitalise the first character of an empty field.
• Expiry. CAPTCHA codes are typically tied to a session and stop being accepted after a while. If you opened the page, went to find your Khatian number, and came back, the CAPTCHA on screen is no longer the one the server expects — even though it still looks perfectly valid.
• Ambiguous characters. Capital I, lowercase l and the digit 1 are frequently indistinguishable in the rendered image, as are O and 0. There is no way to tell them apart from the picture alone. Refresh rather than guess.
• Stale submission after a back-button. Returning to a search form with the browser's back button often restores a cached page showing a CAPTCHA the server has already consumed. Reload the page properly instead of going back.
• Autofill and paste. Password managers and keyboard suggestion bars sometimes insert a trailing space or a previously typed value into the CAPTCHA field. The space is invisible and the rejection looks inexplicable.

Browser, zoom and rendering problems

Sometimes the CAPTCHA is not wrong — it is unreadable, or not there at all.

The image is generated server-side and served as a separate request. If that request fails, you get a blank space or a broken-image icon where the code should be, and no amount of typing will help. Reloading the page usually fixes it; if it persists, the portal itself is likely under load.

Browser zoom is an underrated culprit. Heavy zoom can push the CAPTCHA image and its input box out of alignment on narrow screens, and can leave the refresh control underneath another element so taps land on the wrong thing. Reset zoom to 100% before deciding the CAPTCHA is broken.

• Reset browser zoom to 100% and reload before troubleshooting anything else.
• Use the portal's own refresh control next to the CAPTCHA rather than reloading the whole page — a full reload can clear the district and mouza selections you already made.
• Disable ad blockers and privacy extensions for banglarbhumi.gov.in. Aggressive blockers occasionally drop the CAPTCHA image request.
• Try requesting the desktop site on mobile if the image is rendering at an unreadably small size.
• If the image never loads at all across several reloads, the problem is portal-side rather than yours.

Accessibility: what the portal does and doesn't offer

Banglarbhumi provides a SCREEN READER ACCESS link, a বাংলা / English language toggle, and A+ / A / A- text-sizing controls in its header. The text sizing is genuinely useful here — enlarging the page text does not enlarge the CAPTCHA image itself, but it makes the surrounding form easier to work with, and the language toggle helps if the error messages are the part you can't parse.

What the portal does not offer is an audio CAPTCHA or an alternative challenge. If the image is unreadable to you, there is no built-in accessible path around it. In practice that leaves two options: ask someone to read the code, or visit your local BL&LRO office, where staff can perform the lookup for you.

The CAPTCHA is on the search form, and it is not the only gate

A common misconception is that the CAPTCHA belongs to the sign-in form, so a lookup should be free of it. It isn't. Know Your Property, RS-LR Plot Information, Mutation Case Status, Conversion Case Status, Mouza Information, Query Search and Public Grievance all put a CAPTCHA in front of the query itself, which is why checking several plots means solving several codes.

It is worth being clear that the CAPTCHA is one of two things standing between you and a record. You will also need to be signed in. The portal is misleading on this point: the menus open while you are signed out and the District, Block and Mouza dropdowns populate normally, so the search feels like it is working — right up to the moment you ask for the record, which returns the sign-in page instead.

That matters for diagnosis. If you are solving CAPTCHAs correctly and still not reaching a record, check whether you are actually signed in before you conclude the CAPTCHA is at fault. Register on banglarbhumi.gov.in, sign in, then work the CAPTCHA advice on this page.

What an app changes — and what it honestly can't

Bhumir Tathya is a free, unofficial Android app for West Bengal land records, built by us — so weigh this section accordingly. Records you have already looked up are kept on the device and stay readable offline, which matters when the portal is slow or you are standing in a field with one bar of signal. The interface is bilingual, and the screens are built for a phone rather than a desktop page shrunk down.

It is equally important to be clear about the limits. The app cannot bypass government authentication. Anything that requires a banglarbhumi.gov.in account — a Mutation or Warish application, a Khajna payment, an ROR Request, an eChallan — still goes through your own login on the official portal, with whatever verification the government requires at that point. No third-party app can or should change that.