Security engines reporting a detection: 1. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
packscan.org was recorded in the PhishDestroy internal listing as of 2026-10-12, providing a catalogue entry for the domain on that date. A PageSpeed performance score was also measured, documenting technical characteristics.
Recorded Evidence
VirusTotal checked packscan.org on 2026-10-08, documenting 1 detection from 92 total scanners. The domain was registered with NAMECHEAP INC on 2026-09-28. The PhishDestroy internal listing was recorded as true on 2026-10-12, and a PageSpeed performance score of 50 was measured on the same day.
Interpretation
The VirusTotal observation contains a quantitative measurement of detections and scanner coverage, offering a view into how packscan.org was evaluated by external security tools. PhishDestroy provides a catalogue listing, which is a qualitative record of internal review or classification. These sources together allow for comparison between external scanning results and internal listing status, each with its own scope and date.
Recommended Actions
For packscan.org, preserve the VirusTotal detection record and the PhishDestroy internal listing for ongoing comparison. Review the PageSpeed performance score to monitor any changes in technical characteristics over time. Use these source records to inform future assessments and track updates in external or internal catalogue entries.
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.
RegistrationCreated Sep 28, 2026 (14d · Very New!)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 12, 2026
DOM Analysisanalyzed Oct 13, 2026score 35/1007 brand signals
Submitted URLhttp://packscan.org/
Favicon Hash
Page Title
PackScan — AI Crypto Portfolio Tracker
Impersonates
AcrossBackpackBaseDiscordEthereumSolanaTelegram
TLS Certificate
Certificate hostname mismatch·
Issued by Let's Encrypt / YR1· stored validity ends in 80 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
170.75.160.175
Network ASN
AS174
Organization
Lunanode Hosting Inc
Observed location
Toronto, CA
Server header
nginx
Mail routing 5 MX records
eforward1.registrar-servers.compriority 10
eforward3.registrar-servers.compriority 10
eforward2.registrar-servers.compriority 10
eforward4.registrar-servers.compriority 15
eforward5.registrar-servers.compriority 20
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR1
Valid from
2026-10-02 23:46:01
Valid until
2026-12-31 23:46:00
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-12 22:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3ef71527618a1a10ae6984b0bea64d0bb0f8a1c77d55e415ff82143895176f56Certificate names · 1 SANs
www.packscan.org
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 · 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.org· checked Oct 12, 2026
50
Needs Work
Performance
FCP
3.57s
First Contentful Paint
LCP
16.62s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
531ms
Total Blocking Time
SI
5.59s
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 20:27:37 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 170.75.160.175.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
packscan.org 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 →
(SE)
