PageSourceSearch

Site profile

sabellifioretti.it

Built with flickity 2.0.2, addtoany, google-apis, @vitest/utils 5.0.2, @flarehr/savings-rego-app 0.0.2. 5 pages and 8 stored files, last crawled 2026-10-02.

rank 888,460 5 libraries 0 identifiers 12 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
flickity 2.0.2 2026-10-02
addtoany 2026-10-02
google-apis 2026-10-02
@vitest/utils 5.0.2 2026-10-02
@flarehr/savings-rego-app 0.0.2 2026-09-25

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 sabellifioretti.it 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
apis.google.com script view source
c0.wp.com script stylesheet view source
codicebusiness.shinystat.com script view source
codicepro.shinystat.it script view source
linkshare.clarence.com script view source
pagead2.googlesyndication.com script view source
rpc.blogrolling.com script view source
s10.histats.com script view source
static.addtoany.com script view source
stats.wp.com script view source
w.skipintro.org script view source
www.facebook.com iframe 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://apis.google.com/js/plusone.js js library not fetched 2026-10-02 current
https://static.addtoany.com/menu/page.js js library not fetched 2026-10-02 current
https://www.sabellifioretti.it/wp-content/plugin…/addtoany.min.js?ver=1.1 js 129 B 2026-10-02 current
https://www.sabellifioretti.it/all/17-11.htm html 10 KB 2026-10-02 current
https://www.sabellifioretti.it/all/spec_sanremo2006.htm html 166 KB 2026-10-02 current
https://www.sabellifioretti.it/all/spec_sanremo.htm html 44.8 KB 2026-10-02 current
https://www.sabellifioretti.it/ html 130.6 KB 2026-10-02 2026-10-02
https://www.sabellifioretti.it/caterraduno/caterraduno.htm html 10.4 KB 2026-10-02 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, 8 files, 361.9 KB; 4 libraries, 0 identifiers, 12 third-party hosts

    4 libraries added
    • @vitest/utils 5.0.2
    • flickity 2.0.2
    • addtoany
    • google-apis
    13 third-party hosts added
    8 files added

Questions about sabellifioretti.it

How does PageSourceSearch know what sabellifioretti.it 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 sabellifioretti.it 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 sabellifioretti.it?
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 sabellifioretti.it?
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.