Site profile
monitoring-plus.jp
Built with jquery 1.8.3, gtm, bxslider 4.2.17, jssocials 1.5.0, semantic-ui 2.5.0, jquery.maskedinput 1.4.1, recaptcha, block-ui 2.70.1, jquery-inview 1.1.2, layui-src 2.6.8, jquery-blockui 2.7.0, yasgui-yasqe 2.11.22 and more. 5 pages and 21 stored files, last crawled 2026-10-02.
rank 584,548 15 libraries 3 identifiers 9 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 |
|---|---|---|
| jquery | 1.8.3 | 2026-10-02 |
| gtm | 2026-10-02 | |
| bxslider | 4.2.17 | 2026-10-02 |
| jssocials | 1.5.0 | 2026-10-02 |
| semantic-ui | 2.5.0 | 2026-10-02 |
| jquery.maskedinput | 1.4.1 | 2026-10-02 |
| recaptcha | 2026-10-02 | |
| block-ui | 2.70.1 | 2026-10-02 |
| jquery-inview | 1.1.2 | 2026-10-02 |
| layui-src | 2.6.8 | 2026-10-02 |
| jquery-blockui | 2.7.0 | 2026-10-02 |
| yasgui-yasqe | 2.11.22 | 2026-10-02 |
| x-editable-bs5 | 1.5.8 | 2026-10-02 |
| oauthio-web | 0.6.2 | 2026-10-02 |
| jquery-menu-aim | 1.1.0 | 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.
| What | Value | Found in |
|---|---|---|
| Facebook app id (Meta) | 1653983094907850 | view source |
| Google Tag Manager container (Google) | GTM-WRGGL83 | view source |
| reCAPTCHA site key (Google) | 6LdgfhQUAAAAAM_TYMgo3AOWhjo2kTl7I9Y8yY9Z | view source |
Third-party hosts
Hosts outside monitoring-plus.jp 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 |
|---|---|---|
| ajax.googleapis.com | script | view source |
| b.hatena.ne.jp | connect | view source |
| html5shim.googlecode.com | script | view source |
| line.me | connect | view source |
| plus.google.com | connect | view source |
| twitter.com | connect | view source |
| www.facebook.com | connect | view source |
| www.google.com | script | view source |
| www.googletagmanager.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, 21 files, 455.4 KB; 14 libraries, 3 identifiers, 9 third-party hosts
14 libraries added
- gtm
- recaptcha
- semantic-ui 2.5.0
- bxslider 4.2.17
- jssocials 1.5.0
- layui-src 2.6.8
- oauthio-web 0.6.2
- yasgui-yasqe 2.11.22
- jquery-inview 1.1.2
- jquery.maskedinput 1.4.1
- x-editable-bs5 1.5.8
- block-ui 2.70.1
- and 2 more
3 identifiers added
- GTM-WRGGL83 Google Tag Manager container
- 1653983094907850 Facebook app id
- 6LdgfhQUAAAAAM_TYMgo3AOWhjo2kTl7I9Y8yY9Z reCAPTCHA site key
9 third-party hosts added
21 files added
- https://monitoring-plus.jp/ html
- https://www.monitoring-plus.jp/auth/login/ html
- https://www.monitoring-plus.jp/pricing/ html
- https://www.monitoring-plus.jp/about/ html
- https://www.monitoring-plus.jp/help/contact/ html
- https://www.monitoring-plus.jp/assets/js/lightbox-plus-jquery.min.js js
- https://www.monitoring-plus.jp/assets/js/jquery.inview.js js
- https://www.monitoring-plus.jp/assets/js/footerFixed.js js
- https://www.monitoring-plus.jp/assets/js/new_pages.js js
- https://www.monitoring-plus.jp/assets/js/jquery.simpleTicker.js js
- https://www.monitoring-plus.jp/assets/js/jquery-1.8.3.min.js?1485900737 js
- https://www.monitoring-plus.jp/assets/js/recaptcha.js js
- and 9 more
Questions about monitoring-plus.jp
- How does PageSourceSearch know what monitoring-plus.jp 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 monitoring-plus.jp 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 monitoring-plus.jp?
- 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 monitoring-plus.jp?
- 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.