Download websites that use TomTom Maps

About TomTom Maps

Nobody puts a paid mapping API on a website by accident. Web maps have a default, and that default is usually chosen for a developer by whatever tutorial was open that afternoon, so a site rendering tiles from TomTom instead has generally been through a conversation about cost per map load, about licence terms, or about who owns the underlying map data.

TomTom Maps reached the web as a Proprietary product in 2010, backed by a map database the vendor builds rather than licenses from someone else. Ownership of the base map is the commercial argument. Teams that need to redistribute geocoded results, cache tiles, or embed the same map inside a product they ship to their own customers run into clauses in the default provider's terms that a negotiated agreement is meant to solve, and that pressure is what usually puts this SDK on a page.

Our fingerprint is a front-end one. The page loads the vendor's JavaScript SDK and calls it to draw a map, and the loaded code is what we record. Server side use stays invisible to us, and server side is where much of this work actually happens. A logistics platform geocoding addresses in a batch job, or a fleet product calling routing from its backend, leaves nothing in the HTML for a crawler to find. As of October 2026 we detect it on 36 sites, a figure best read as the visible surface of a wider customer base rather than as a count of customers.

The visible surface is still the useful one for most research questions, because drawing an interactive map means the site wants a visitor to look at a place. Store locators, dealer networks, property listings, travel and venue pages, and the dashboards of companies whose product is itself about vehicles or delivery make up most of what remains after that filter. Anyone selling address validation, points of interest data, telematics or a competing mapping contract is looking for exactly that set, and knowing which provider a site already pays is worth considerably more than knowing it has a map.

Checking one domain tells you what one company decided. The downloadable list tells you how the decision distributes across an industry: which sectors settled on an alternative to the default, how those sites cluster by country and by top level domain, and which of them look like they are shipping a product rather than publishing a page. Our catalogue records the entry under Maps, which is accurate but coarse, since a locator widget on a restaurant chain and a routing SDK inside a logistics dashboard share a fingerprint and share almost nothing else. Sorting that population is where the answer lives, and sorting needs the whole file rather than a lookup box.