PageSourceSearch

Site profile

hfs-berlin.de

Built with intersection-observer, regenerator-runtime, flickity, object-fit-images, process, core-js, ev-emitter, get-size, desandro-matches-selector, fizzy-ui-utils, unipointer, unidragger and more. 5 pages and 8 stored files, last crawled 2026-10-02.

rank 668,705 20 libraries 2 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.

LibraryVersionSeen
intersection-observer 2026-10-02
regenerator-runtime 2026-10-02
flickity 2026-10-02
object-fit-images 2026-10-02
process 2026-10-02
core-js 2026-10-02
ev-emitter 2026-10-02
get-size 2026-10-02
desandro-matches-selector 2026-10-02
fizzy-ui-utils 2026-10-02
unipointer 2026-10-02
unidragger 2026-10-02
path-browserify 2026-10-02
tiny-date-picker 2026-10-02
@bmlt-enabled/croutonjs 4.3.3 2026-10-02
owl.carousel 2.3.4 2026-09-24
fomantic-ui 2.9.4 2026-09-24
mdbootstrap 4.20.0 2026-09-24
mt-boost 1.0.46 2026-09-24
jsxgraph 1.13.3 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.

WhatValueFound in
Google site verification (Google) WLQXWDAd211gcxskkZAhHBFLor6J8CIkOrJ6lJ61aH8 view source
Matomo site id (Matomo) matomo.hfs-berlin.de#1 view source

Third-party hosts

Hosts outside hfs-berlin.de 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.

HostLoaded asFound in
any.url connect view source
bit.ly connect view source
player.podigee-cdn.net script view source
player.vimeo.com connect view source
www.betterplace.org script view source
www.w3.org connect view source
www.youtube.com connect view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 8) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

FileKindSizeCollectedVersions
https://cms.hfs-berlin.de/scripts/scripts.1d74c6be.js js 1.5 MB 2026-10-02 2026-10-02
https://www.hfs-berlin.de/typo3temp/assets/compr…028241e74440d9c0d.js?1789116406 js 742.2 KB 2026-10-02 current
https://www.hfs-berlin.de/dgs/ html 40.1 KB 2026-10-02 current
https://cms.hfs-berlin.de/app/ html 8 KB 2026-10-02 2026-10-02
https://www.hfs-berlin.de/en/ html 31.7 KB 2026-10-02 current
https://www.hfs-berlin.de/ html 74.8 KB 2026-10-02 2026-10-02
https://www.hfs-berlin.de/aktuelles/news/ html 45.9 KB 2026-10-02 2026-10-02
https://cms.hfs-berlin.de/scripts/scripts.e12ac71a.js js 1.5 MB 2026-09-24 current

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.

  1. first crawl

    5 pages, 7 files, 2.4 MB; 15 libraries, 2 identifiers, 7 third-party hosts

    15 libraries added
    • @bmlt-enabled/croutonjs 4.3.3
    • core-js
    • desandro-matches-selector
    • ev-emitter
    • fizzy-ui-utils
    • flickity
    • get-size
    • intersection-observer
    • object-fit-images
    • path-browserify
    • process
    • regenerator-runtime
    • and 3 more
    2 identifiers added
    7 third-party hosts added
    7 files added

Questions about hfs-berlin.de

How does PageSourceSearch know what hfs-berlin.de 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 hfs-berlin.de 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 hfs-berlin.de?
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 hfs-berlin.de?
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.