This public record shows how Vakteye verification pages display proof metadata. It is not a customer certificate and does not replace a live production scan.
- Evidence hash
- sha256:b1f7cac65cb25f491bfed36bce272a4f0a0accb615f91d45fe7f26d787d691d0
- Signature status
- Demo package
This sample demonstrates the public verification flow. Production proof packages use stored certificate records and signature fields where available.
What each check means
Consent flow
We clicked reject. Tracking cookies and pixels stopped loading, the way they should.
Policy vs traffic
The privacy policy matched what the site actually sent in network traffic.
Encryption and headers
TLS, HSTS, secure cookie flags, and CSP were in place.
Third parties
No unexpected trackers loaded from external domains.
Where we stop
An automated scanner checks what a visitor's browser can see. Some things it can't reach:
- Backend systems and databases
- Payment processing
- Logged-in and account flows
Those need a formal audit, with access behind the login.
Audit record
The detailed record, for auditors and compliance officers.
- Scope
- vakteye.com
- Jurisdiction
- European Union
- Method
- Weekly automated scan
- Issued
- Jun 23, 2026

