Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
The domain dashboard-embercurve.xyz was observed with a MetaMask external blocklist entry on 2026-10-13, providing a dated reference from a recognized monitoring source. A PageSpeed performance score of 78 was also recorded on that date, documenting technical characteristics relevant to infrastructure assessment.
Recorded Evidence
MetaMask and SEAL both listed dashboard-embercurve.xyz on their external blocklists as of 2026-10-13. VirusTotal recorded 0 detections out of 92 scanners when it checked the domain on 2026-10-03. The domain was first observed on 2026-10-13 and registered on 2026-09-18. PhishDestroy internally listed the domain, and a PageSpeed performance score was measured on 2026-10-13.
Interpretation
PhishDestroy contains an internal listing of dashboard-embercurve.xyz, which documents its presence in that system's records. VirusTotal provides a measurement based on a scan from multiple sources, recording the number of detections found during its check. The external blocklist entries from MetaMask and SEAL represent inclusion in those monitoring lists, which are separate from technical performance measurements.
Recommended Actions
For dashboard-embercurve.xyz, retain the MetaMask and SEAL blocklist entries as reference records for future reviews. Preserve the VirusTotal scan record and the PhishDestroy internal listing for comparison with subsequent security checks. Use the PageSpeed performance score as a technical benchmark when evaluating later infrastructure or security reviews.
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.
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.
Values retained by the collector; long values may be shortened during collection.
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-13 13:06:40 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.171.78.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
7 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日
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(RU)
PhishDestroy Investigation
