Site profile
ndnv-electionmap.vercel.app
Built with jquery 3.6.0, axios, leaflet, @turf/turf, papaparse 5.3.0, proj4js 2.7.5, leaflet-search 3.0.4. 1 page and 11 stored files, last crawled 2026-10-03.
7 libraries 0 identifiers 7 third-party hosts 1 crawl open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| jquery | 3.6.0 | 2026-10-03 |
| axios | 2026-10-03 | |
| leaflet | 2026-10-03 | |
| @turf/turf | 2026-10-03 | |
| papaparse | 5.3.0 | 2026-10-03 |
| proj4js | 2.7.5 | 2026-10-03 |
| leaflet-search | 3.0.4 | 2026-10-03 |
Tracking, tag and verification IDs
No analytics property, tag manager container, pixel or site-verification token was found in the stored source.
Third-party hosts
Hosts outside ndnv-electionmap.vercel.app that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
| Host | Loaded as | Found in |
|---|---|---|
| cdnjs.cloudflare.com | script stylesheet | view source |
| nominatim.openstreetmap.org | connect | view source |
| osm.org | connect | view source |
| services1.arcgis.com | connect | view source |
| stackpath.bootstrapcdn.com | stylesheet | view source |
| unpkg.com | script stylesheet | view source |
| www.sos.nd.gov | connect | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
1 page, 11 files, 30.2 KB; 7 libraries, 0 identifiers, 7 third-party hosts
7 libraries added
- @turf/turf
- jquery 3.6.0
- axios
- papaparse 5.3.0
- proj4js 2.7.5
- leaflet
- leaflet-search 3.0.4
9 third-party hosts added
11 files added
- https://ndnv-electionmap.vercel.app/ html
- https://ndnv-electionmap.vercel.app/index.js js
- https://ndnv-electionmap.vercel.app/constants.js js
- https://ndnv-electionmap.vercel.app/eventListeners.js js
- https://unpkg.com/@turf/turf/turf.min.js js
- https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.0/jquery.min.js js
- https://unpkg.com/axios/dist/axios.min.js js
- https://cdnjs.cloudflare.com/ajax/libs/PapaParse/5.3.0/papaparse.min.js js
- https://cdnjs.cloudflare.com/ajax/libs/proj4js/2.7.5/proj4.js js
- https://unpkg.com/leaflet/dist/leaflet.js js
- https://cdnjs.cloudflare.com/ajax/libs/leaflet-s…/3.0.4/leaflet-search.min.js js
Questions about ndnv-electionmap.vercel.app
- How does PageSourceSearch know what ndnv-electionmap.vercel.app is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of ndnv-electionmap.vercel.app go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from ndnv-electionmap.vercel.app?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as ndnv-electionmap.vercel.app?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.