Site profile
mairie-ange.com
Built with cloudflare-email-decode. 5 pages and 6 stored files, last crawled 2026-10-02.
rank 1,383,608 1 library 1 identifier 5 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 |
|---|---|---|
| cloudflare-email-decode | 2026-10-02 |
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 site verification (Google) | fo_fPqjm_qRUfRDWqR6n2cEtgyRzYNU0c2rfRhil8rM | view source |
Third-party hosts
Hosts outside mairie-ange.com 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 |
|---|---|---|
| assets.jimstatic.com | script stylesheet | view source |
| googledrive.com | stylesheet | view source |
| u.jimcdn.com | stylesheet | view source |
| www.google.com | iframe | view source |
| www.tameteo.com | script | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://www.mairie-ange.com/cdn-cgi/scripts/5c5d…/email-decode.min.js | js | 1.2 KB | 2026-10-02 | current |
| https://www.mairie-ange.com/vie-municipale/conseil-municipal/ | html | 56.7 KB | 2026-10-02 | 2026-10-02 |
| https://www.mairie-ange.com/vie-municipale/ | html | 53 KB | 2026-10-02 | 2026-10-02 |
| https://www.mairie-ange.com/contact/ | html | 55.3 KB | 2026-10-02 | 2026-10-02 |
| https://www.mairie-ange.com/about/ | html | 65.9 KB | 2026-10-02 | 2026-10-02 |
| https://www.mairie-ange.com/ | html | 80 KB | 2026-10-02 | 2026-10-02 |
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, 6 files, 312.1 KB; 1 library, 1 identifier, 5 third-party hosts
1 library added
- cloudflare-email-decode
1 identifier added
- fo_fPqjm_qRUfRDWqR6n2cEtgyRzYNU0c2rfRhil8rM Google site verification
6 third-party hosts added
6 files added
- https://www.mairie-ange.com/ html
- https://www.mairie-ange.com/about/ html
- https://www.mairie-ange.com/contact/ html
- https://www.mairie-ange.com/vie-municipale/ html
- https://www.mairie-ange.com/vie-municipale/conseil-municipal/ html
- https://www.mairie-ange.com/cdn-cgi/scripts/5c5d…/email-decode.min.js js
Questions about mairie-ange.com
- How does PageSourceSearch know what mairie-ange.com 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 mairie-ange.com 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 mairie-ange.com?
- 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 mairie-ange.com?
- 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.