PageSourceSearch

Site profile

paymark.co.nz

Built with gtm, bromcom-ui 2.12.3, c2pa 0.30.17, onetrust, facebook-pixel, @partslogic/ui 2.0.7, @yandex/ymaps3-default-ui-theme 0.0.25, reverie-stt-sdk 0.24.0, mdbootstrap 4.20.0, universalviewer 4.4.4. 5 pages and 13 stored files.

rank 92,590 10 libraries 2 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.

LibraryVersionSeen
gtm 2026-09-24
bromcom-ui 2.12.3 2026-09-24
c2pa 0.30.17 2026-09-24
onetrust 2026-09-24
facebook-pixel 2026-09-24
@partslogic/ui 2.0.7 2026-09-24
@yandex/ymaps3-default-ui-theme 0.0.25 2026-09-24
reverie-stt-sdk 0.24.0 2026-09-24
mdbootstrap 4.20.0 2026-09-24
universalviewer 4.4.4 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
Meta pixel id (Meta) 2369409283344638 view source
Google Tag Manager container (Google) GTM-NQ3D8XW6 view source

Third-party hosts

The stored pages and scripts reference no host outside paymark.co.nz.

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 13) }. 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://cdn.cookielaw.org/scripttemplates/otSDKStub.js js library not fetched 2026-09-24 current
https://www.paymark.co.nz/_Incapsula_Resource?SW…&ns=6&cb=515219024 js 86.9 KB 2026-09-24 current
https://www.paymark.co.nz/_Incapsula_Resource?SW…&ns=5&cb=1739085834 js 79.2 KB 2026-09-24 current
https://www.paymark.co.nz/_Incapsula_Resource?SW…&ns=4&cb=1289273375 js 85.1 KB 2026-09-24 current
https://www.paymark.co.nz/_Incapsula_Resource?SW…&ns=3&cb=903671612 js 85 KB 2026-09-24 current
https://www.paymark.co.nz/_Incapsula_Resource?SW…&ns=2&cb=1416759861 js 81.6 KB 2026-09-24 current
https://www.paymark.co.nz/_resources/themes/worl…/app.js?id=1046847dc75b2224874b js 122.7 KB 2026-09-24 current
https://www.paymark.co.nz/_resources/themes/worl…?id=82ee4b2108855fcc692e js 248.8 KB 2026-09-24 current
https://www.paymark.co.nz/support/contact-us html 65.4 KB 2026-09-24 current
https://www.paymark.co.nz/about-us/who-we-are html 69.4 KB 2026-09-24 current
https://www.paymark.co.nz/blog html 78.9 KB 2026-09-24 current
https://www.paymark.co.nz/products/eftpos html 77.5 KB 2026-09-24 current
https://www.paymark.co.nz/ html 77.2 KB 2026-09-24 current

Timeline

No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.

Questions about paymark.co.nz

How does PageSourceSearch know what paymark.co.nz 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 paymark.co.nz 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 paymark.co.nz?
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 paymark.co.nz?
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.