Shipping daily
Nov 1DATAAll 646 projects re-verified: 6,419 developer claims tested against registers, courts and pressNov 1DATAMalaysia TEDUH and Philippines DHSUD licence checks: expired licences and approved delays foundNov 1DATAThailand ONEP register: 2 condos found selling before environmental approvalNov 1DATAMexico PROFECO contract register checks: one sales registration belonged to a laundryNov 1DATAAbu Dhabi ADREC inspections and RAK RERA permit list added: % built straight from the regulatorNov 1SHIPPEDNew stage filter: completed but still sellingNov 1SHIPPEDPublic database page: verification levels, disclosure distribution, every marketNov 1DATA+212 projects in one day, round 3: USA, Caribbean, Gulf, Africa, Japan, AustraliaNov 1SHIPPEDStage on every case: off-plan or under constructionOct 31SHIPPEDVerification level per check on every case card: registry, independent, developer, contradicted
Changelog →

Kolaboro / Tools / Image check

Is this render used by another project?

Drop the render or photo from a brochure or listing. Your browser turns it into a 64-bit fingerprint and compares it with every image on the project pages we track.

Your image never leaves this device. The fingerprint is computed in your browser (kdh.js) and compared with a public list of fingerprints (image-hashes.json). The only request this check makes is downloading that list. Site analytics are masked on this tool: they never see your image or the results.

How it works

A fast first check, with known blind spots

The fingerprint

The image is decoded at full size, turned into brightness values, and split into a grid of 9 by 8 cells. Each of the 64 bits says whether a cell is darker than its right-hand neighbour. Resizing, recompression and small colour changes keep most bits; a different picture flips about half of them.

The index

Every week our render-reuse job downloads the images on each tracked project page (logos, icons, small images and site decoration left out) and stores the same fingerprint, the project's public id and the image address. The browser and the weekly job run the same function; a test checks that both give identical bits on the same files.

Reading the distance

  • 0 to 5 bits: near-identical.
  • 6 to 10: very likely the same picture, resized or lightly edited.
  • 11 to 14: shown only as "close", check by eye.

We also compare the centre 70% of each image and a mirrored version, which catches simple crops and flips.

What this cannot catch

  • Heavier crops, rotations, added text or reframed renders change the fingerprint.
  • Images from sites we do not track.
  • A match is evidence to ask about, not proof: portals and sister brands share renders legitimately.

For deeper matching (CLIP embeddings confirmed by keypoint geometry) see the weekly render-reuse detector.

Check a PDF for editsCheck a payment account
Protect my purchase