Site profile
bs-hjem.dk
Built with promise-polyfill 8.3.0, @googlemaps/markerclusterer, framework7 9.1.3, krds-uiux 1.1.0, anzhiyu-theme-static 1.1.10, aspnet-client-validation 0.11.1. 5 pages and 18 stored files, last crawled 2026-10-09.
rank 14,706,171 6 libraries 0 identifiers 4 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 |
|---|---|---|
| promise-polyfill | 8.3.0 | 2026-10-09 |
| @googlemaps/markerclusterer | 2026-10-09 | |
| framework7 | 9.1.3 | 2026-10-09 |
| krds-uiux | 1.1.0 | 2026-10-09 |
| anzhiyu-theme-static | 1.1.10 | 2026-10-09 |
| aspnet-client-validation | 0.11.1 | 2026-10-09 |
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 bs-hjem.dk 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 |
|---|---|---|
| dk.sms-service.dk | iframe | view source |
| maps.googleapis.com | connect | view source |
| unpkg.com | script | view source |
| www.google.com | iframe | 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
5 pages, 18 files, 401.7 KB; 6 libraries, 0 identifiers, 4 third-party hosts
6 libraries added
- promise-polyfill 8.3.0
- aspnet-client-validation 0.11.1
- krds-uiux 1.1.0
- framework7 9.1.3
- anzhiyu-theme-static 1.1.10
- @googlemaps/markerclusterer
4 third-party hosts added
18 files added
- https://bs-hjem.dk/ html
- https://bs-hjem.dk/information/om-boligselskabet-hjem/ html
- https://bs-hjem.dk/information/beboerapp/ html
- https://bs-hjem.dk/information/sms-service/ html
- https://bs-hjem.dk/information/kontakt/ html
- https://bs-hjem.dk/App_Plugins/UmbracoForms/Asse…/dist/polyfill.min.js?v=13.9.10 js
- https://bs-hjem.dk/App_Plugins/UmbracoForms/Asse…net-validation.min.js?v=13.9.10 js
- https://bs-hjem.dk/scripts/bundle.generated.js?v…6bXHdSy68-Arv5hecbfd13oIof5Lip8 js
- https://bs-hjem.dk/lib/swiper/swiper-bundle.min.…FbOVjGTu8An0iIm7Zd9o2wvNEiVWt6c js
- https://bs-hjem.dk/scripts/heroes/hero-3c.js?v=S…W2fdZN9R5wAdEWg7cLnogOM1gMIvwcY js
- https://bs-hjem.dk/scripts/components/frequently…e1tg-8RJIpVE00sstPllt26rrcsh9TU js
- https://bs-hjem.dk/scripts/components/department…y9qZAqSVvrTl4THfT621Ei5QpmuJI80 js
- and 6 more
Questions about bs-hjem.dk
- How does PageSourceSearch know what bs-hjem.dk 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 bs-hjem.dk 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 bs-hjem.dk?
- 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 bs-hjem.dk?
- 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.