Site profile
petrobras.com.br
Built with webpack, @clerk/ui 1.34.0, dompurify 3.2.4, @wix/design-system 1.328.0, @findify/bundle 7.1.108, cdn4script 2.2.4, tesseract.js 7.0.0, fomantic-ui 2.9.4, swagger-ui-dist 5.33.0, @feathery/react 2.96.0, @reachfive/identity-ui 2.1.0, kore-web-sdk 11.28.1 and more. 5 pages and 9 stored files.
rank 11,020 17 libraries 0 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.
| Library | Version | Seen |
|---|---|---|
| webpack | 2026-09-24 | |
| @clerk/ui | 1.34.0 | 2026-09-24 |
| dompurify | 3.2.4 | 2026-09-24 |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| @findify/bundle | 7.1.108 | 2026-09-24 |
| cdn4script | 2.2.4 | 2026-09-24 |
| tesseract.js | 7.0.0 | 2026-09-24 |
| fomantic-ui | 2.9.4 | 2026-09-24 |
| swagger-ui-dist | 5.33.0 | 2026-09-24 |
| @feathery/react | 2.96.0 | 2026-09-24 |
| @reachfive/identity-ui | 2.1.0 | 2026-09-24 |
| kore-web-sdk | 11.28.1 | 2026-09-24 |
| @cognigy/webchat | 3.50.0 | 2026-09-24 |
| clientjs | 0.2.1 | 2026-09-24 |
| pushfeedback | 0.1.85 | 2026-09-24 |
| @adalong/widget | 7.15.1 | 2026-09-24 |
| vis-timeline | 8.5.4 | 2026-09-24 |
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
The stored pages and scripts reference no host outside petrobras.com.br.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://canalcliente.petrobras.com.br/s/sfsites/…iewType%22%3A%22Published%22%7D | js | 2.3 MB | 2026-09-24 | current |
| https://petrobras.com.br/documents/d/f3a44542-11…/main-e5eb64a9?t=1790142076302 | js | 374.8 KB | 2026-09-24 | current |
| https://canalcliente.petrobras.com.br/s/sfsites/…&rv=1788970908000 | js | 51.2 KB | 2026-09-24 | current |
| https://canalcliente.petrobras.com.br/s/sfsites/…NC4xOTIuODM4ODYwOA/aura_prod.js | js | 935.9 KB | 2026-09-24 | current |
| https://petrobras.com.br/sustentabilidade/dados-abertos | html | 585.6 KB | 2026-09-24 | current |
| https://petrobras.com.br/sustentabilidade/mudancas-climaticas | html | 729.9 KB | 2026-09-24 | current |
| https://petrobras.com.br/transicao-energetica | html | 1.2 MB | 2026-09-24 | current |
| https://canalcliente.petrobras.com.br/s/ | html | 466 KB | 2026-09-24 | current |
| https://petrobras.com.br/ | html | 658.1 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 petrobras.com.br
- How does PageSourceSearch know what petrobras.com.br 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 petrobras.com.br 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 petrobras.com.br?
- 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 petrobras.com.br?
- 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.