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

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 co.pt?

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.

Site profile

co.pt

Built with jquery 1.3.2, cloudflare-insights, @vitest/utils 5.0.2, @unhead/vue 3.4.1. 5 pages and 8 stored files, last crawled 2026-10-02.

rank 584,625 4 libraries 4 identifiers 4 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.3.2	2026-10-02
cloudflare-insights		2026-10-02
@vitest/utils	5.0.2	2026-10-02
@unhead/vue	3.4.1	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
Bing site verification (Microsoft)	CDB372E406AA26DCCBA33046EFD2ACEB	view source
Bing site verification (Microsoft)	EFF25332C3F8448F9AB8873DEAC32F28	view source
Google site verification (Google)	hZVNXrhNtBFedKMtJ3Uca0TBQ2aS4u4M0dUTuQ4QReM	view source
Google site verification (Google)	z64iu27WSQ39Bj4id4N3Zni6l6YDExNR9_DhpcqYL7M	view source

Third-party hosts

Hosts outside co.pt 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
static.cloudflareinsights.com	script	view source
static.getclicky.com	script	view source
toolbar.aeiou.pt	script	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 8) }. 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.

File	Kind	Size	Collected	Versions
http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js	js library	not fetched	2026-10-02	current
https://static.cloudflareinsights.com/beacon.min…cfa3763df669d7439c1639079717194	js library	not fetched	2026-10-02	current
https://www.co.pt/include/consulta.js	js	8.1 KB	2026-10-02	current
https://www.co.pt/precos_pagamentos	html	49.1 KB	2026-10-02	2026-10-02
https://www.co.pt/termos_condicoes	html	40.6 KB	2026-10-02	current
https://www.co.pt/como_funciona	html	51.9 KB	2026-10-02	2026-10-02
https://www.co.pt/dominios	html	48.6 KB	2026-10-02	2026-10-02
https://www.co.pt/	html	48.6 KB	2026-10-02	2026-10-02

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.

2026-10-02 first crawl

5 pages, 8 files, 246.9 KB; 3 libraries, 4 identifiers, 4 third-party hosts
3 libraries added
- @vitest/utils 5.0.2
- jquery 1.3.2
- cloudflare-insights
4 identifiers added
- hZVNXrhNtBFedKMtJ3Uca0TBQ2aS4u4M0dUTuQ4QReM Google site verification
- z64iu27WSQ39Bj4id4N3Zni6l6YDExNR9_DhpcqYL7M Google site verification
- EFF25332C3F8448F9AB8873DEAC32F28 Bing site verification
- CDB372E406AA26DCCBA33046EFD2ACEB Bing site verification
4 third-party hosts added
8 files added

Questions about co.pt

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