Screenshots lie.
Network traffic doesn't.
Anyone can alter a webpage in 5 seconds using browser Developer Tools[1]. ProofCore captures the raw server response, extracts the SSL/TLS certificate[2], records the DNS state, and bundles the entire HAR network log[3] into a blockchain-anchored evidence package.
The "Inspect Element" Vulnerability
Flat screenshots are frequently challenged in modern disputes because they lack forensic metadata. Without capturing the underlying network traffic and cryptographic signatures of the server, a screenshot is just a picture that anyone could have drawn.
SUBMIT URL
Send any HTTP/HTTPS link to our Telegram bot. Our isolated headless Chromium worker securely navigates to the target.
RENDER & LOG
We render a full-page PDF & WebP, while simultaneously recording the raw DOM and all network requests into a standard W3C HAR archive.
EXTRACT PKI
We extract the target server's SSL/TLS certificate fingerprint, Cipher Suite, and active DNS routing records.
ANCHOR
The entire bundle is hashed and anchored to the TON Blockchain, creating an immutable timestamp.
3 Free Proofs / mo ยท Send any URL to the bot
Forensic Demonstration
A Web Page, Dissected
We notarized our own website. This specimen demonstrates the deep network forensics captured to prove exactly what our servers received.
Proof that survives the system that created it.
Trust you can't delete. Forward once. Prove forever.
Network Forensics Extracted
Level 1: Network & PKI Authentication
Level 2: Raw Forensic JSON Envelope โผ
{
"type": "Web Page Notarization",
"target_url": "https://proofcore.org/en/",
"resolved_ip": "104.21.34.28",
"ssl_fingerprint": "6f281ad82cca0daafb7e89b10c6294c0c859ac78641e23673b9cc996601d71df",
"ssl_issuer": "Google Trust Services",
"ssl_subject": "proofcore.org",
"ssl_valid_period": "2026-08-19 to 2026-11-17",
"ssl_tls_version": "TLSv1.3",
"ssl_cipher_suite": "TLS_AES_256_GCM_SHA384",
"http_headers": {
"content-type": "text/html",
"date": "Wed, 16 Sep 2026 11:35:05 GMT",
"server": "cloudflare"
},
"dns_records": {
"A": ["172.67.167.213", "104.21.34.28"],
"NS": ["ryan.ns.cloudflare.com.", "serena.ns.cloudflare.com."]
},
"geoip_asn": {
"country": "Canada",
"isp": "Cloudflare, Inc.",
"as": "AS13335 Cloudflare, Inc."
}
}
Level 3: Standalone Evidence Package
Contains the generated PDF/WebP, the raw HAR network log, the HTML source, forensic JSON, and offline Python/HTML verifiers.
OSINT & Legal Scenarios
Where Flat Screenshots Fall Short
Websites change dynamically. Terms of service are updated silently. ProofCore captures the underlying network reality.
Terms of Service & Pricing Changes
Companies often update their public Terms or pricing tables silently, causing disputes with legacy customers.
IP Infringement & Plagiarism
Competitors steal your design, code, or copy. When they receive a cease-and-desist, they quickly delete the stolen content.
Defamation & Public Statements
Public figures or publications post defamatory statements and delete them shortly after the backlash begins.
OSINT & Cyber Threat Intelligence
Investigating phishing sites, malware domains, or fraudulent shops before the hosting provider takes them offline.
Epistemic Clarity
Clear mathematical boundaries for OSINT investigators and legal professionals.
๐ข What ProofCore Establishes
- The exact byte stream returned by the server to our data center at that specific second.
- The validity and SHA-256 fingerprint of the SSL/TLS certificate presented to us by the server.
- The DNS routing records (A, AAAA, NS, TXT) active for that domain at the time of our capture.
- The IP address and Autonomous System (ASN) that responded to our request.
- The visual rendering (PDF/WebP) of the captured DOM by a standard Chromium engine.
๐ด What ProofCore Does NOT Establish
- That the page looked the exact same for users in other geographic locations (Geo-IP targeting).
- Content hidden behind authentication walls, logins, or captchas.
- That the website owner didn't intentionally serve different content specifically to our IPs.
- The factual truthfulness of the statements published on the webpage.
- Automatic legal admissibility of the captured content in your specific jurisdiction.
Case Law & Precedents
Why Web Screenshots Fail in Court
๐ Rossbach v. Montefiore Med. Ctr. (2nd Cir. 2023) โ
The plaintiff submitted a JPEG screenshot of a digital conversation. Forensic examination revealed it was fabricated. The court applied terminating sanctions, completely dismissing the lawsuit for spoliation of evidence.
โ Lesson: Submitted evidence is vulnerable without reproducible cryptographic hashing and network metadata.
โ๏ธ Novak v. Tucows, Inc. (E.D.N.Y. 2007) โ
The court rejected printouts of archived website pages because the presenting party failed to provide adequate authentication foundation regarding how the archives were captured and preserved.
โ Lesson: Web archives require a documented chain of custody or cryptographic seal to support admissibility.
Statutory Evidentiary Context
๐บ๐ธ US Federal Rules of Evidence: Rule 902(13) & (14)
Rule 902(14) governs data copied from an electronic storage medium authenticated by a digital identification process (e.g., SHA-256). ProofCore's HAR archives and cryptographic manifests provide a technically reproducible foundation that can assist in authentication.
๐ช๐บ EU eIDAS Framework
Under eIDAS, electronic evidence cannot be denied legal effect solely because it is electronic. ProofCore provides a non-qualified cryptographic ledger and timestamping mechanism.
๐ HTTP Archive (HAR) & ISO 28500
By capturing the full W3C-standard HTTP Archive (HAR), ProofCore aligns with digital preservation best practices, allowing forensic experts to replay the exact network requests that generated the webpage.
Disclaimer: ProofCore provides technical cryptographic evidence. Admissibility and weight of evidence are determined by the relevant court or tribunal according to applicable procedural laws.
Glossary of Forensic & Technical Terms
[1] Developer Tools (Inspect Element)
A feature built into all modern web browsers that allows any user to edit the text, images, and layout of a webpage locally before taking a screenshot, making flat screenshots unreliable as evidence.
[2] SSL/TLS Certificate
A digital certificate issued by a trusted Certificate Authority (CA) that authenticates a website's identity and encrypts the connection. Capturing its fingerprint proves the data came from the legitimate server, not an imposter.
[3] HAR (HTTP Archive)
A standard JSON-formatted log of a web browser's interaction with a site. It contains every network request, response header, and payload (images, scripts) downloaded during the session.
[4] BGP ASN (Autonomous System Number)
A unique identifier allocated to each network/ISP on the internet (e.g., AS13335 for Cloudflare). It helps trace the physical infrastructure hosting the website.
[5] Merkle Root
A mathematical hash that summarizes thousands of data pieces into a single 64-character string. Anchoring this string to the blockchain proves the existence of all underlying data without exposing the data itself.