PageSourceSearch

Site profile

depay.com

Built with react, react-dom, @lottiefiles/lottie-player, scheduler, @hotwired/stimulus, medium-zoom, countup.js, highlight.js, react-countup, @depay/web3-blockchains. 5 pages and 6 stored files, last crawled 2026-10-02.

rank 517,153 10 libraries 0 identifiers 57 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
react 2026-10-02
react-dom 2026-10-02
@lottiefiles/lottie-player 2026-10-02
scheduler 2026-10-02
@hotwired/stimulus 2026-10-02
medium-zoom 2026-10-02
countup.js 2026-10-02
highlight.js 2026-10-02
react-countup 2026-10-02
@depay/web3-blockchains 2026-10-02

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 depay.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.

HostLoaded asFound in
1rpc.io connect view source
480.rpc.thirdweb.com connect view source
arb1.arbitrum.io connect view source
arbiscan.io connect view source
arbitrum-one.publicnode.com connect view source
arbitrum.rpc.thirdweb.com connect view source
assets.trustwalletapp.com connect view source
avalanche-api.flare.network connect view source
avalanche-c-chain-rpc.publicnode.com connect view source
avalanche-c-chain.publicnode.com connect view source
base-rpc.publicnode.com connect view source
base.lava.build connect view source
base.rpc.thirdweb.com connect view source
basescan.org connect view source
bsc-dataseed1.bnbchain.org connect view source
bsc-rpc.publicnode.com connect view source
bsc.blockrazor.xyz connect view source
bscscan.com connect view source
cdn.sushi.com connect view source
coin-images.coingecko.com connect view source
endpoints.omniatech.io connect view source
eth.rpc.blxrbdn.com connect view source
eth1.lava.build connect view source
ethereum-optimism.github.io connect view source
ethereum.publicnode.com connect view source
etherscan.io connect view source
fantom.publicnode.com connect view source
ftmscan.com connect view source
github.com connect view source
gnosis-rpc.publicnode.com connect view source
gnosisscan.io connect view source
hoprnet.org connect view source
img.raydium.io connect view source
lottiefiles.com connect view source
optimism.publicnode.com connect view source
optimism.rpc.thirdweb.com connect view source
optimistic.etherscan.io connect view source
player.vimeo.com connect view source
polygon-bor-rpc.publicnode.com connect view source
polygon-bor.publicnode.com connect view source
polygon.lava.build connect view source
polygonscan.com connect view source
raw.githubusercontent.com connect view source
react.dev connect view source
rpc.fantom.network connect view source
rpc.gnosis.gateway.fm connect view source
rpc.gnosischain.com connect view source
rpc2.fantom.network connect view source
snowtrace.io connect view source
solana-rpc.publicnode.com connect view source
solscan.io connect view source
traderjoexyz.com connect view source
user-images.githubusercontent.com connect view source
worldchain-mainnet.g.alchemy.com connect view source
worldscan.org connect view source
www.w3.org connect view source
www.youtube-nocookie.com connect view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 6) }. 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://depay.com/assets/application-f30bf80f.js js 3.5 MB 2026-10-02 current
https://depay.com/pricing html 91.9 KB 2026-10-02 current
https://depay.com/blog html 23 KB 2026-10-02 current
https://depay.com/examples/uniswap-merch-shop--b…p-wallet-5VZg1e9zGQHYfHwNiabfH3 html 20.8 KB 2026-10-02 current
https://depay.com/products/payments html 36.7 KB 2026-10-02 2026-10-02
https://depay.com/ html 38.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, 6 files, 3.7 MB; 10 libraries, 0 identifiers, 57 third-party hosts

    10 libraries added
    • react
    • scheduler
    • react-dom
    • highlight.js
    • countup.js
    • react-countup
    • @hotwired/stimulus
    • @lottiefiles/lottie-player
    • @depay/web3-blockchains
    • medium-zoom
    57 third-party hosts added
    6 files added

Questions about depay.com

How does PageSourceSearch know what depay.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 depay.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 depay.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 depay.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.