PhishDestroy first recorded symonp.cc on 2026-10-27. Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-20 12:59 UTC. Retrieved (as stored): 2026-10-27 06:29 UTC. Listed by external blocklists: ScamSniffer.
Page title: “Curve DAO”
More about the sources
Recorded security signals
Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-20 12:59 UTC. Retrieved (as stored): 2026-10-27 06:29 UTC. Listed by external blocklists: ScamSniffer. Use caution — do not enter credentials or personal information.
Risk signals
VirusTotal detections: 2/92Stored blocklist matches: 1Last known active
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 7D+ 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 domainabuse@service.aliyun.com. The latest stored availability evidence still shows the domain reachable; 26 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.
Elapsed since first report
26 days
Reports sent
1
Latest case ID
PD-20261027-AF3108
Current status
HTTP 403 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded symonp.cc on 2026-10-27. Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-20 12:59 UTC. Retrieved (as stored): 2026-10-27 06:29 UTC. Listed by external blocklists: ScamSniffer. Risk: critical (evidence score 100/100). Registrar: Dominet (HK). Status: Reachable · access restricted. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
PhishDestroy added symonp.cc to its internal blocklist on 2026-10-27 after an intake flagged it for malicious detections on VirusTotal. The site returned HTTP 200 and served a page at /main.html when fetched on 2026-10-27.
How the scam works
The listing categorises the site as a phishing page, a common scam that mimics legitimate services to lure users into revealing login credentials or authorising cryptocurrency transactions. No specific form or lure was observed in the captured page, so the exact bait cannot be confirmed.
Evidence
VirusTotal recorded two malicious detections on 2026-10-20 from alphaMountain.ai (phishing) and CRDF (malicious) out of 92 engines. Google Safe Browsing on 2026-10-27 did not flag the domain. urlscan scans on 2026-10-19 (UUID 01a15489-8166-7599-b4e8-cbb25daa9623) and 2026-10-27 (UUID 01a17bef-fff3-7742-84d9-230af93c844d) both gave a malicious verdict with score 100, labeling the page as phishing/crypto‑scam. OTX listed three pulses as of 2026-10-27; PhishDestroy’s internal blocklist marks the domain malicious while external blocklists showed zero matches on that date.
Infrastructure
The domain was registered on 2026-10-01 through Dominet (HK) Limited. TLS from Google Trust Services, valid 2026-10-01 to 2026-12-30 for symonp.cc and *.symonp.cc, serves the site behind Cloudflare, which recorded A records 188.114.96.0, 188.114.97.0, AAAA records 2a06:98c1:3120::, 2a06:98c1:3121::, and a captured IP 104.21.17.93 on 2026-10-27; the hosting network is ASN 13335.
What to do
Visitors should avoid entering any credentials or authorising wallet actions on this site; if they have already done so, they should change any associated passwords immediately. Organizations should add symonp.cc to web‑proxy, DNS or firewall block lists, review access logs for connections, and avoid broader IP or registrar blocking because the address may host unrelated services.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Page code check by a separate monitor · 10 / 100 · 2026-10-27 06:35 UTC
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
10
Analyzed at
2026-10-27T06:35:19Z
Source timestamp
2026-10-27 07:35:19
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
symonp.cc — Suspicious Domain
AI description
PhishDestroy flags symonp.cc as a suspicious domain after malicious detections on VirusTotal and urlscan, with a live HTTP 200 page at /main.html.
AI summary
Overview PhishDestroy added symonp.cc to its internal blocklist on 2026-10-27 after an intake flagged it for malicious detections on VirusTotal. The site returned HTTP 200 and served a page at /main.html when fetched on 2026-10-27. How the scam works The listing categorises the site as a phishing page, a common scam that mimics legitimate services to lure users into revealing login credentials or authorising cryptocurrency transactions. No specific form or lure was observed in the captured page, so the exact bait cannot be confirmed. Evidence VirusTotal recorded two malicious detections on 2026-10-20 from alphaMountain.ai (phishing) and CRDF (malicious) out of 92 engines. Google Safe Browsing on 2026-10-27 did not flag the domain. urlscan scans on 2026-10-19 (UUID 01a15489-8166-7599-b4e8-cbb25daa9623) and 2026-10-27 (UUID 01a17bef-fff3-7742-84d9-230af93c844d) both gave a malicious verdict with score 100, labeling the page as phishing/crypto‑scam. OTX listed three pulses as of 2026-10-27; PhishDestroy’s internal blocklist marks the domain malicious while external blocklists showed zero matches on that date. Infrastructure The domain was registered on 2026-10-01 through Dominet (HK) Limited. TLS from Google Trust Services, valid 2026-10-01 to 2026-12-30 for symonp.cc and *.symonp.cc, serves the site behind Cloudflare, which recorded A records 188.114.96.0, 188.114.97.0, AAAA records 2a06:98c1:3120::, 2a06:98c1:3121::, and a captured IP 104.21.17.93 on 2026-10-27; the hosting network is ASN 13335. What to do Visitors should avoid entering any credentials or authorising wallet actions on this site; if they have already done so, they should change any associated passwords immediately. Organizations should add symonp.cc to web‑proxy, DNS or firewall block lists, review access logs for connections, and avoid broader IP or registrar blocking because the address may host unrelated services. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17bef-fff3-7742-84d9-230af93c844d/ Cloudflare Radar report: https://radar.cloudflare.com/scan/4812c043-b388-4c97-ac6d-1013f6f366f5 URLQuery report: https://urlquery.net/report/71d8b5f9-cd56-4f42-891c-3f223b2061a3 Stored capture screenshot: https://i.ibb.co/chT0f7yR/a6174df8b90e.png Cloudflare Radar screenshot (2026-10-27T05:57:34Z): https://screenshots.phishdestroy.io/cf/4812c043-b388-4c97-ac6d-1013f6f366f5.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/71d8b5f9-cd56-4f42-891c-3f223b2061a3.png URLScan screenshot (2026-10-19T14:21:11Z): https://screenshots.phishdestroy.io/us/01a15489-8166-7599-b4e8-cbb25daa9623.png URLScan capture report: https://urlscan.io/result/01a15489-8166-7599-b4e8-cbb25daa9623/ VirusTotal report: https://www.virustotal.com/gui/domain/symonp.cc Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=symonp.cc Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates symonp.cc as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-27. Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-20 12:59 UTC. Retrieved (as stored): 2026-10-27 06:29 UTC. Listed by external blocklists: ScamSniffer. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is symonp.cc safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on symonp.cc. A confirmed blockchain transaction cannot be reversed.
What should I do if I used symonp.cc?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-10-27
DOM Analysisanalyzed 2026-10-27score 10/1001 brand signal
Submitted URLhttp://symonp.cc/
Favicon Hash
Case ID
Observed page title
Curve DAO
Automated brand references
Curve
TLS Certificate
Issued by Google Trust Services / WE1· stored validity ends in 37 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Certificate fingerprint1789a7eaf72091b8dbbad9f731722c572e52396f7f82fc8f46fb2f7ae608b8b1Certificate names · 2 SANs
symonp.cc
*.symonp.cc
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-11-17 11:29 UTClast content: 2026-11-17 11:29 UTCcurrent episode first observed: 2026-11-17 23:34 UTCobserved RIP window: 2026-11-17 11:29 UTC → 2026-11-17 23:34 UTC · 12.08hmidpoint estimate ≈ 2026-11-17 17: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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:55 UTC.
Recorded events: 14. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Hours from detection to the first unavailable observation: 521
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
7 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+19 d 5 h
Added to PhishDestroy+6 d 16 h
First abuse report sent+12 min
Reported 25 d 23 h after registration
AlienVault OTX
3 community references
+22 min
Alibaba Cloud
Acknowledged the report
same minute
Abuse report sent
PD-20261027-AF3108 · Receipt 83803
domainabuse@service.aliyun.com
+7 min
URLScan
Page captured
+2 min
Cloudflare Radar
Phishing
+1 min
Added to PhishDestroy
symonp.cc
+6 d 16 h
VirusTotal
2/92 engine detections
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.
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
Report all
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Nothing matches. Clear the search or choose another filter.
burve.fiBit flipVariant of curve.fiA 76.76.21.21NS ns01.trademarkarea.comcruve.fiSwapped charactersVariant of curve.fiA 176.65.144.109NS 1-you.njalla.nocur.ve.fiSplit into subdomainVariant of curve.fiA 64.190.63.222MX localhostNS ns1.sedoparking.comcure.fiMissing characterVariant of curve.fiA 64.190.63.222MX localhostNS ns1.sedoparking.comcurve-fi.comVariantVariant of curve.fiA 195.201.128.179NS ns1.dns-redirect.comcurvefi.comVariantVariant of curve.fiA 172.65.185.109NS sp1.gname-dns.comcurvi.fiVowel swapVariant of curve.fiA 88.99.26.106MX mail.curvi.fiNS ns1.polar55.comcurvo.fiVowel swapVariant of curve.fiA 185.53.179.145NS ns1.eurodns.comcuvre.fiSwapped charactersVariant of curve.fiA 176.65.144.109NS 1-you.njalla.no
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including symonp.cc)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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 →
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.