On 2026-10-01 the domain snappy-drift.com returned HTTP status 200 in a recorded check, describing only that response at that time. A separate Pagespeed check on 2026-09-23 recorded a performance score of 100 for the domain.
Recorded Evidence
The domain snappy-drift.com was registered on 2025-10-28 with registrar Dynadot Inc. An SSL scan on 2026-09-23 recorded the issuer as Google Trust Services / WE1. VirusTotal recorded 16 detections across 91 scanners on 2026-09-25. OTX recorded 4 pulses on 2026-09-25, and the PhishDestroy internal listing was recorded as true.
Interpretation
The HTTP and Pagespeed records describe responses captured on their own dates, while the VirusTotal and OTX records describe scanner and pulse counts captured on 2026-09-25. The PhishDestroy listing records a publisher catalogue entry rather than a measurement by another source. Because the checks fall on different dates, the records allow comparison of what each source reported, not of a single moment.
Recommended Actions
Preserve the snappy-drift.com HTTP response record and the Pagespeed score record for later comparison. Keep the VirusTotal detection record and the OTX pulse record as separate source documents. Compare the PhishDestroy internal listing against later catalogue entries for snappy-drift.com. Recheck the domain's HTTP response and Pagespeed score to refresh those dated observations.
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: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 10:11:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:11:34 UTClast content: 2026-10-13 10:11:34 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.
技术 · 5 identified
N
Node.js
Programming languages
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
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 snappy-drift.com· checked Sep 23, 2026
100
Good
Performance
FCP
1.05s
First Contentful Paint
LCP
1.05s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.35s
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-10-13 22:29:42 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-23 09:08:29 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.187.105.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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
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)
