packscan.cash was recorded on 2026-10-13 with entries on the MetaMask and SEAL external blocklists. The domain also received a PageSpeed performance score of 34, which may be relevant for technical evaluations.
Recorded Evidence
On 2026-10-13, packscan.cash appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on the same date, recording zero detections out of 92 scanners. OTX registered two pulses for the domain on 2026-10-13. PhishDestroy internally listed the domain, and the registration date was recorded as 2026-09-28. The PageSpeed performance score was 34 on 2026-10-13.
Interpretation
PhishDestroy provides an internal listing, documenting the presence of packscan.cash in its system as of 2026-10-13. VirusTotal records contain the results of multiple security scanners, offering a view of how the domain was evaluated by external tools. These sources capture different aspects of the domain’s technical and reputational profile.
Recommended Actions
Retain the MetaMask and SEAL blocklist entries for packscan.cash as reference points for future checks. Preserve VirusTotal scan results and OTX pulse records for comparison over time. Keep the PhishDestroy listing and PageSpeed performance score to track any changes in technical or reputational status.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='packscan.cash', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
登録情報作成日 2026年9月28日 (14d · Very New!)—Expires 2027年9月28日
技術詳細Provenance & timestamps
初確認2026年10月13日
DOM Analysisanalyzed 2026年10月13日score 40/1007 brand signals
Submitted URLhttp://packscan.cash/
Favicon Hash
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 10:00:11 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 00:17:30 UTCcurrent episode first observed: 2026-10-13 08:20:58 UTCobserved RIP window: 2026-10-13 00:17:30 UTC → 2026-10-13 08:20:58 UTC · 8.06hmidpoint estimate ≈ 2026-10-13 04:19:14 UTC · precision medium · 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.
使用技術 · 2 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of packscan.cash· checked Oct 13, 2026
34
Poor
Performance
FCP
2.59s
First Contentful Paint
LCP
11.42s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1732ms
Total Blocking Time
SI
16.1s
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-10-12 23:42:58 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 170.75.160.175.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
10 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.
ブロックリストの検出
掲載先 2 blocklists: MetaMask, SEAL
2026年10月13日
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Brand Impersonation
Impersonation of Across
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026年10月13日
Technical Analysis Recorded
レポートには、保存されたテクノロジーまたはフォレンジック分析の結果が含まれます。
2026年10月13日
Sent Report Recorded
Stored outgoing record associated with registrar NameCheap, Inc., 2 abuse contacts
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)
