retikfinance-com.pages.dev was observed returning an HTTP 403 status on 2026-10-01, indicating restricted access at that time. The domain was also listed on both MetaMask and SEAL blocklists, which are external sources tracking potentially problematic domains.
Recorded Evidence
On 2026-10-01, retikfinance-com.pages.dev was checked and found to be on the MetaMask and SEAL blocklists. The domain was first observed on 2026-09-15, and its HTTP response code was 403 as of 2026-10-01. VirusTotal scanned the domain on 2026-09-21 with 89 scanners and reported zero detections. The domain was internally listed by PhishDestroy, and its PageSpeed performance score was recorded as 100 on 2026-09-21.
Interpretation
The sources provide a timeline of observations, with blocklist inclusion and HTTP status recorded on 2026-10-01, while VirusTotal and PageSpeed results are from 2026-09-21. Comparing these dates helps clarify the sequence of events and the consistency of findings from different sources. Each source offers a distinct perspective, and their results may change with subsequent checks.
Recommended Actions
For retikfinance-com.pages.dev, retain all evidence from the listed sources for future reference and comparison. When reviewing subsequent observations, carefully note the dates and any changes in blocklist status or scanner results. Avoid submitting sensitive information to the domain during any review process, and prioritize monitoring for updates from the same sources.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-15 14:28:16 UTCcurrent episode first observed: 2026-10-01 01:53:45 UTCobserved RIP window: 2026-09-15 14:28:16 UTC → 2026-10-01 01:53:45 UTC · 371.42hmidpoint estimate ≈ 2026-09-23 08:11:00 UTC · precision low · basis bounded
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.
技术 · 3 identified
H
HSTS
安全
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 retikfinance-com.pages.dev· checked Sep 21, 2026
100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
1.85s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
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.
Domain Status Transition2026-09-21 10:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-21 08:13:11 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
2026年9月23日
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月14日
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of Genericcrypto
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(US)
