The domain revs-eralabs.pages.dev returned an HTTP 403 status on 2026-10-01, indicating restricted access at that time. Additionally, the domain was listed on the ScamSniffer blocklist as of 2026-10-01.
Recorded Evidence
On 2026-09-17, VirusTotal reported 2 detections out of 89 scanners for revs-eralabs.pages.dev. The domain was first observed on 2026-09-05 and had a PageSpeed performance score of 54 as of 2026-09-15. The SSL certificate was issued by Google Trust Services / WE1 and was scanned on 2026-09-15. Phishdestroy internally listed the domain as of the most recent evidence.
Interpretation
The combination of an HTTP 403 response and inclusion on the ScamSniffer blocklist suggests that access to revs-eralabs.pages.dev was restricted while also being flagged by at least one external threat intelligence source. VirusTotal’s detections, though limited in number, indicate that some security vendors have identified potential concerns with the domain. The presence of an internal listing by Phishdestroy further highlights that the domain has drawn attention from multiple monitoring sources.
Recommended Actions
Review all available evidence for revs-eralabs.pages.dev, including the ScamSniffer blocklist entry and VirusTotal’s detection records, to inform any further investigation. Preserve the HTTP response record and internal listing details for future comparison or escalation. Continue monitoring for updates from these sources to track any changes in the domain’s status.
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 22:06:48 UTCcurrent episode first observed: 2026-10-01 01:39:34 UTCobserved RIP window: 2026-09-15 22:06:48 UTC → 2026-10-01 01:39:34 UTC · 363.55hmidpoint estimate ≈ 2026-09-23 11:53:11 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.
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
Gridinsoft
网站性能分析
Google PageSpeed Insights — mobile performance audit of revs-eralabs.pages.dev· checked Sep 15, 2026
54
Needs Work
Performance
FCP
30.82s
First Contentful Paint
LCP
31.57s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
100ms
Total Blocking Time
SI
30.82s
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-16 10:00:36 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-14 23:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 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.
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)
