Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, safety-ledger.pages.dev returned HTTP status 200 in a recorded check, and the domain was first observed on 2026-09-15. A PageSpeed check on 2026-09-21 recorded a performance score of 100 for the page.
Recorded Evidence
The external blocklists MetaMask, SEAL and PhishFeed each listed the domain as of the 2026-10-01 blocklist check, and an internal listing was recorded as true. VirusTotal recorded 4 detections across 91 scanners on 2026-09-29. The SSL certificate, scanned on 2026-09-21, was issued by Google Trust Services / WE1.
Interpretation
The external blocklists, VirusTotal and the internal listing were recorded on different dates, so their observations cannot be treated as a single synchronized snapshot. The 2026-10-01 HTTP response and blocklist check fall on the same date, while the VirusTotal scan and SSL scan predate them. Comparing these dated records shows how the evidence set changed over time without asserting a verdict.
Recommended Actions
Reviewers should retain the dated records for safety-ledger.pages.dev, including the 2026-10-01 HTTP check and the 2026-09-29 VirusTotal result, for later comparison. Subsequent checks of safety-ledger.pages.dev should be compared against these baseline dates to identify changes in the recorded observations. During review, avoid submitting sensitive information to safety-ledger.pages.dev until the evidence has been independently verified.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-13 10:12:03 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 10:12:03 UTClast content: 2026-10-13 10:12:03 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of safety-ledger.pages.dev· checked Sep 21, 2026
100
Good
Performance
FCP
0.92s
First Contentful Paint
LCP
0.92s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.33s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-09-21 07:43:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
safety-ledger.pages.dev detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · safety-ledger.pages.dev
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
