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.
Analysis of votes-moonwell.finance shows a high‑risk phishing infrastructure that is currently active. The domain was registered on March 04, 2026 through NiceNIC International Group Co., Limited and resolves to 188.114.97.3, an IP owned by Cloudflare (AS13335) located in the United States. The site presents an HTTP 403 response and uses a Let’s Encrypt/E7 TLS certificate, indicating a valid HTTPS configuration. Nameservers are adam.ns.cloudflare.com and danica.ns.cloudflare.com, confirming Cloudflare hosting. The domain appears on three security blocklists and is explicitly blocked by PhishDestroy, MetaMask, and SEAL, reinforcing the phishing classification. VirusTotal scans report four of ninety‑four security vendors flag the domain, and Gridinsoft assigns a trust score of 0/100, both indicating malicious reputation. The page title "Un instant…" is the only content observed; no further page details have been disclosed. Defenders should immediately add votes-moonwell.finance to DNS and proxy deny lists, monitor outbound connections to its IP for potential exfiltration, and apply URL filtering to prevent user access. Continuous re‑evaluation is advised, as additional threat intelligence may emerge regarding payloads or credential harvesting techniques associated with this domain.
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.
Observed timelinelast reachable: 2026-09-15 22:18:15 UTCcurrent episode first observed: 2026-09-17 02:45:08 UTCobserved RIP window: 2026-09-15 22:18:15 UTC → 2026-09-17 02:45:08 UTC · 28.45hmidpoint estimate ≈ 2026-09-16 12:31:41 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.
Google PageSpeed Insights — mobile performance audit of votes-moonwell.finance· checked Apr 11, 2026
91
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
2.31s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
323ms
Total Blocking Time
SI
1.34s
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.
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.
(RU)
PhishDestroy Investigation
