ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 4 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
sitemv2dwy8wu2na.cfd was documented with a PhishDestroy internal listing on 2026-10-10, providing a dated record in the publisher's catalogue. On that same date, a PageSpeed performance score was measured for the domain, offering a technical snapshot for comparison.
Recorded Evidence
VirusTotal recorded 0 detections out of 92 total scanners for sitemv2dwy8wu2na.cfd on 2026-10-10. The domain was first observed and registered on 2026-10-10, with Spaceship, Inc. as the registrar. On this date, the PageSpeed performance score was 37, and the domain appeared in the PhishDestroy internal listing.
Interpretation
PhishDestroy provides a record of sitemv2dwy8wu2na.cfd, documenting its inclusion in the publisher's internal catalogue. VirusTotal contains a measurement of external scanner detections, reflecting how the domain was reviewed by multiple security tools. These source records together offer a dated technical and security context for the domain.
Recommended Actions
Preserve the VirusTotal scanner results and the PhishDestroy internal listing for sitemv2dwy8wu2na.cfd as reference points. Compare the documented PageSpeed performance score to future technical assessments to track any new findings or changes.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/FlareNetworkStored page reference
IoC extraction recorded 2026-10-11 04:01:37 UTC
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sitemv2dwy8wu2na.cfd', port=80): Max retries exceeded with url: / (Caused by NewConnection
DOM Analysisanalyzed 2026年10月10日score 100/1003 brand signals
IoC Extractionscanned 2026年10月11日0 wallet · 1 Telegram IoC
Submitted URLhttp://sitemv2dwy8wu2na.cfd/
Favicon Hash
案件 ID
SHORTDOT 域名区 · 公开证据.cfd
ShortDot zone evidence
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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-14 10:00:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-10 14:08:13 UTCcurrent episode first observed: 2026-10-11 20:20:50 UTCobserved RIP window: 2026-10-10 14:08:13 UTC → 2026-10-11 20:20:50 UTC · 30.21hmidpoint estimate ≈ 2026-10-11 05:14:31 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
Cloudflare
CDN
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 sitemv2dwy8wu2na.cfd· checked Oct 10, 2026
37
Poor
Performance
FCP
22.76s
First Contentful Paint
LCP
22.81s
Largest Contentful Paint
CLS
0.379
Cumulative Layout Shift
TBT
1ms
Total Blocking Time
SI
22.76s
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-10 14:03:11 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.175.204.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
13 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.
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(US)
