Site profile
fantasticservicesgroup.com.au
Built with gtm, webpack, @inkeep/cxkit-js 0.5.119, typesense-instantsearch-adapter 3.0.2, tableexport.jquery.plugin 1.33.0, reverie-stt-sdk 0.24.0, paymob-pixel 1.2.7, jsxgraph 1.13.3, botframework-webchat 4.19.1, webex 3.12.0, leanplum-sdk 1.14.0, @xano/js-sdk 3.0.1 and more. 5 pages and 27 stored files.
rank 8,041,061 31 libraries 3 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 |
|---|---|---|
| gtm | 2026-09-29 | |
| webpack | 2026-09-29 | |
| @inkeep/cxkit-js | 0.5.119 | 2026-09-29 |
| typesense-instantsearch-adapter | 3.0.2 | 2026-09-29 |
| tableexport.jquery.plugin | 1.33.0 | 2026-09-29 |
| reverie-stt-sdk | 0.24.0 | 2026-09-29 |
| paymob-pixel | 1.2.7 | 2026-09-29 |
| jsxgraph | 1.13.3 | 2026-09-29 |
| botframework-webchat | 4.19.1 | 2026-09-29 |
| webex | 3.12.0 | 2026-09-29 |
| leanplum-sdk | 1.14.0 | 2026-09-29 |
| @xano/js-sdk | 3.0.1 | 2026-09-29 |
| vue3-sfc-loader | 0.9.5 | 2026-09-29 |
| jquery.flipster | 1.1.6 | 2026-09-29 |
| @mezereon/bigcommerce-stencil | 1.0.30 | 2026-09-29 |
| @vitest/utils | 5.0.2 | 2026-09-29 |
| javascript-obfuscator | 5.8.0 | 2026-09-29 |
| @ckeditor/ckeditor5-build-classic | 44.3.0 | 2026-09-29 |
| @machi-pla/ai-chatbot | 0.1.25 | 2026-09-29 |
| @formio/js | 5.6.1 | 2026-09-29 |
| @descope/web-components-ui | 3.21.0 | 2026-09-29 |
| cil-dropin-components | 1.2.10 | 2026-09-29 |
| @ant-design/x | 2.9.0 | 2026-09-29 |
| mori-chat-widget | 2.0.49 | 2026-09-29 |
| @wangeditor/editor | 5.1.23 | 2026-09-29 |
| prometix | 1.7.0 | 2026-09-29 |
| @percy.ai/hvs-funnel-overlay | 0.5.13 | 2026-09-29 |
| @grigorov-it/mazer | 2.2.0 | 2026-09-29 |
| vf-widgets | 0.2.48 | 2026-09-29 |
| @wix/image | 1.454.0 | 2026-09-29 |
| syzoj-public-cdn | 1.2.0 | 2026-09-29 |
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-KFBLW9 | view source |
| Google Tag Manager container (Google) | GTM-W5PWW8J6 | view source |
| reCAPTCHA site key (Google) | 6Lelo3MUAAAAAPtmVVXCt7cvU2HULMLt2KATQBxr | view source |
Third-party hosts
The stored pages and scripts reference no host outside fantasticservicesgroup.com.au.
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 fantasticservicesgroup.com.au
- How does PageSourceSearch know what fantasticservicesgroup.com.au 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 fantasticservicesgroup.com.au 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 fantasticservicesgroup.com.au?
- 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 fantasticservicesgroup.com.au?
- 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.