PageSourceSearch

Site profile

newyorkgenealogy.org

Built with jquery-ui 1.14.2, core-js-bundle 3.50.0, jquery-migrate 3.4.1, jquery-ui-dist 1.13.3, dygraphs 2.2.2, jsxgraph 1.13.3, jquery.fancytree 2.38.5, jquery.flipster 1.1.6, @recogito/annotorious 2.7.14, hyperformula 3.4.0, @grigorov-it/mazer 2.2.0. 5 pages and 19 stored files, last crawled 2026-10-06.

rank 11,655,664 11 libraries 1 identifier 7 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
jquery-ui 1.14.2 2026-10-06
core-js-bundle 3.50.0 2026-10-06
jquery-migrate 3.4.1 2026-10-06
jquery-ui-dist 1.13.3 2026-10-06
dygraphs 2.2.2 2026-10-06
jsxgraph 1.13.3 2026-10-06
jquery.fancytree 2.38.5 2026-10-06
jquery.flipster 1.1.6 2026-10-06
@recogito/annotorious 2.7.14 2026-10-06
hyperformula 3.4.0 2026-10-06
@grigorov-it/mazer 2.2.0 2026-10-06

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
AdSense publisher id (Google) ca-pub-2661054029950069 view source

Third-party hosts

Hosts outside newyorkgenealogy.org 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
github.com connect view source
pagead2.googlesyndication.com script view source
schema.org connect view source
stats.wp.com script view source
subscribe.wordpress.com connect view source
www.adobe.com connect view source
www.w3.org connect view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 19) }. 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://newyorkgenealogy.org/wp-content/litespee…2f6b8beb469021d04e.js?ver=e0e6c js 6.8 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…82efa343a33ce2d960.js?ver=02774 js 24.8 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…99ce14ef7008bc9e79.js?ver=81135 js 2.9 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…ce8c315626ebb56330.js?ver=aea19 js 5.2 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…ea4e3b323bed20afa6.js?ver=ca422 js 29 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…96e1942cab7bc3729c.js?ver=e356f js 859 B 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…5a57f1913231cece11.js?ver=0cfe0 js 7.2 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…77564ec10c9acb2754.js?ver=46aa0 js 4.3 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…185ae7b7f0a5973c56.js?ver=ec2db js library 6.1 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…4febc56264eeeff53c.js?ver=d868f js library 18.2 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…8b60af6d2d50df27eb.js?ver=8aac4 js 619 B 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…69b8e41cce95a51013.js?ver=2b004 js 12.1 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-content/litespee…da591bda4da02afbeb.js?ver=c0462 js 13.3 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/washington/washington-county-new-york-genealogy.htm html 218.5 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 js library 85.5 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/suffolk/suffolk-county-new-york-genealogy.htm html 156.9 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/jefferson/jefferson-county-new-york-genealogy.htm html 232.8 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/orange/index.htm html 129.3 KB 2026-10-06 2026-10-06
https://newyorkgenealogy.org/ html 123.3 KB 2026-10-06 2026-10-06

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, 19 files, 1.1 MB; 11 libraries, 1 identifier, 7 third-party hosts

    11 libraries added
    • jquery.flipster 1.1.6
    • @grigorov-it/mazer 2.2.0
    • jsxgraph 1.13.3
    • jquery-migrate 3.4.1
    • jquery.fancytree 2.38.5
    • jquery-ui-dist 1.13.3
    • jquery-ui 1.14.2
    • dygraphs 2.2.2
    • hyperformula 3.4.0
    • core-js-bundle 3.50.0
    • @recogito/annotorious 2.7.14
    1 identifier added
    7 third-party hosts added
    19 files added

Questions about newyorkgenealogy.org

How does PageSourceSearch know what newyorkgenealogy.org 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 newyorkgenealogy.org 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 newyorkgenealogy.org?
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 newyorkgenealogy.org?
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.