Site profile
1881.no
Built with @finsweet/attributes 2.7.1, gtm, @clerk/clerk-js 6.33.0, @clerk/ui 1.34.0, @wix/design-system 1.328.0, jquery-ui 1.14.2, leaflet 1.9.4, d3 19.3.0-canary-3f0b9e61-20260317, @blotoutio/providers-blotout-consent-sdk 1.73.0, tooltipster 4.2.8, fomantic-ui 2.9.4, dashjs 5.2.1 and more. 5 pages and 46 stored files.
rank 48,718 36 libraries 2 identifiers 0 third-party hosts 0 crawls 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 |
|---|---|---|
| @finsweet/attributes | 2.7.1 | 2026-09-24 |
| gtm | 2026-09-24 | |
| @clerk/clerk-js | 6.33.0 | 2026-09-24 |
| @clerk/ui | 1.34.0 | 2026-09-24 |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| jquery-ui | 1.14.2 | 2026-09-24 |
| leaflet | 1.9.4 | 2026-09-24 |
| d3 | 19.3.0-canary-3f0b9e61-20260317 | 2026-09-24 |
| @blotoutio/providers-blotout-consent-sdk | 1.73.0 | 2026-09-24 |
| tooltipster | 4.2.8 | 2026-09-24 |
| fomantic-ui | 2.9.4 | 2026-09-24 |
| dashjs | 5.2.1 | 2026-09-24 |
| @eka-care/medassist-widget | 0.1.131 | 2026-09-24 |
| @inkeep/cxkit-js | 0.5.119 | 2026-09-24 |
| @reachfive/identity-core | 1.42.0 | 2026-09-24 |
| @reachfive/identity-ui | 2.1.0 | 2026-09-24 |
| jspdf | 4.2.1 | 2026-09-24 |
| sa-sdk-javascript | 1.27.14 | 2026-09-24 |
| kore-web-sdk | 11.28.1 | 2026-09-24 |
| jquery-ui-dist | 1.13.3 | 2026-09-24 |
| leaflet.markercluster | 1.5.3 | 2026-09-24 |
| selectric | 1.13.0 | 2026-09-24 |
| reverie-stt-sdk | 0.24.0 | 2026-09-24 |
| mdbootstrap | 4.20.0 | 2026-09-24 |
| react-big-calendar | 1.20.0 | 2026-09-24 |
| cross-storage | 1.0.0 | 2026-09-24 |
| spectorjs | 0.9.33 | 2026-09-24 |
| jquery-ui-1-11-4 | 1.11.4 | 2026-09-24 |
| mt-boost | 1.0.46 | 2026-09-24 |
| universalviewer | 4.4.4 | 2026-09-24 |
| videojsadx | 4.1.2 | 2026-09-24 |
| @ideal-postcodes/address-finder-bundled | 5.0.14 | 2026-09-24 |
| jquery.fancytree | 2.38.5 | 2026-09-24 |
| @moveo-ai/web-client | 0.117.0 | 2026-09-24 |
| jquery.browser | 0.1.0 | 2026-09-24 |
| dzxstatic | 3.4.20211231 | 2026-09-24 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Google Tag Manager container (Google) | GTM-NHZ8MD | view source |
| Google Tag Manager container (Google) | GTM-WD5JGQ | view source |
Third-party hosts
The stored pages and scripts reference no host outside 1881.no.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about 1881.no
- How does PageSourceSearch know what 1881.no 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 1881.no 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 1881.no?
- 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 1881.no?
- 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.