Shipping daily
Nov 9SHIPPEDFull working test of the site (checks, tools, accounts, feeds, API): a saved X-ray now shows in your dashboard, project pages have a Save to my list button again, and the update feed is currentNov 9SHIPPEDSecurity hardening: pages now refuse inline script handlers, links built from third-party data cannot run scripts, the map and text-reading libraries are pinned with integrity hashes, and payment-check lookups are rate limitedNov 9SHIPPEDSpeed: the browser no longer restyles the whole page after every small change, project and developer pages are answered from an edge copy before any data is read, sections far from the screen are drawn as you get near them, and the open numbers page keeps its figures for a minuteNov 9SHIPPEDLookalike websites: a daily watch for new websites whose names resemble the developer and project websites we track, with registration and certificate dates, on developer pages and at /watch/lookalikes/Nov 9DATASanctions lists: developer company names are screened daily against the entity entries of the OFAC, UK and UN lists; developer pages show the lists and date when there is no matchNov 9DATACorporate family on developer pages: parents and subsidiaries from the GLEIF register (CC0) for 39 developers matched by exact legal name, and a new family link type in the developer graphNov 9DATATwo Birmingham project pins corrected (they sat one degree too far north); their map-based sections stay hidden until the next monthly rebuild uses the new pinsNov 9SHIPPEDProtected land near the pin on 125 project pages: Natura 2000 sites within 2 km, England green belt and other designations, the Spanish coast law easements and mapped nature reserves, with distances and layer datesNov 9SHIPPEDThe map's own history at each plot: when the buildings, roads and land use within 150 m were first drawn in OpenStreetMap and last changed, as a small timeline on 125 project pagesNov 9SHIPPEDSite check on 560 page views and 3,078 links: the two account checks merged into one, clearer tool descriptions and jump links, a country search, an accessible pricing table and a tidier free check on phonesNov 9SHIPPEDShort-let reality check on 28 project pages: Inside Airbnb listings within 1 km, median nightly price and their occupancy estimate, next to any rental yield the page we track printsNov 9DATARecorded sale prices within 1 km on 14 project pages: HM Land Registry (England), DVF (France) and NYC rolling sales, medians and price per m2 next to the developer's own headline priceNov 9SHIPPEDProject and developer pages are easier to read: identical price copies merged into one row, the overdue date sits next to the date it is about, correct singular wording, Arabic names no longer flip punctuation, and the website-health method is translatedNov 9SHIPPEDAny plot from space: pin any spot and get one clear Sentinel-2 picture per quarter since 2017, made on demand, and turn it or a project's time machine into a shareable time-lapse GIFNov 8DATASatellite images back to January 2017: the monthly Sentinel-2 series on 125 project pages now covers almost ten yearsNov 8SHIPPEDSee the site: open street-level photos within 200 m of the pin on 59 project pages, and a 3D view with terrain and 12,328 mapped buildings on 125
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. It also reads the file's Content Credentials (C2PA) and metadata for what they say about how the picture was made.

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 the reuse check makes is downloading that list. If the file carries Content Credentials, your browser also downloads the official open-source C2PA library (c2pa-web 0.15.3, its code from this site and its 2.7 MB WebAssembly file from jsDelivr, checked against a pinned SHA-256 before it runs) and the C2PA trust lists. Your image is never sent anywhere. Site analytics are masked on this tool: they never see your image or the results.

Progress photos from the developer: when, where, and reused?

Drop the construction photos you were sent. For each one we read the date, camera, editing software and GPS position stored in the file, measure how far it was taken from the project's market, and compare it with the images of every project we track and with the other photos in the batch. The photos stay on this device.

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.

Where the image came from

Content Credentials and metadata, read honestly

Content Credentials (C2PA)

Some cameras, phones, editors and AI generators attach a signed record of how a file was made: the tool, the edits and a declared source such as "created by a generative AI model". We verify it with the official open-source C2PA library, in your browser: the signature, the certificate chain and the hashes that tie the record to these exact pixels.

Who signed it

We check the signer against two public trust lists, copied to this site: the official C2PA Trust List (copy) and the older Content Credentials interim list (copy). An intact record from a signer on neither list is shown as "signer unknown".

Metadata signals

We also read EXIF, XMP and PNG text fields: the IPTC digital source type (for example trainedAlgorithmicMedia), the creator tool, the edit history, and generator settings that Stable Diffusion or ComfyUI write into PNG files. We list what we find with the field it came from. Metadata is not signed: anyone can add, change or strip it.

What this is not

  • Not an AI detector. We do not guess from the pixels, because no detector we know of is reliable enough to publish an accuracy for.
  • No credentials and no metadata proves nothing: most websites strip both, and a screenshot removes them.
  • A render is computer-made by design. The question that matters is whether something sold as a site photo was generated.
Check a PDF for editsCheck a payment account
Protect my purchase