Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev favicon

curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev

In short

curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (72/100). Registrar: Tencent Cloud. Status: Last known active. Hosting: ACE-AS-AP - ACE, SG. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Files Collection”

Review the evidence
Registrar
Tencent Cloud
Resolved IP
Singapore43.174.247.29ACE-AS-AP - ACE, SG
Registered
Jun 9, 2025
First observed
Oct 25, 2026
PhishDestroy assessment Critical
72/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Spamhaus DBL: phishing domain
VirusTotal
4 / 92
engine detections ·
Page captures
3
open gallery
Domain age
505 days
Oct 25, 2026
X Telegram API

Questions about curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev

Is curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev legit?

No. PhishDestroy classifies curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev as a phishing page (risk: critical, 72/100); it was first detected on 2026-10-25. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 4 / 92 6 sources

VirusTotal

4 / 92 engine detections

Open report

Spamhaus DBL

phishing domain

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 190a5d90a89d499d6ebb2027c53a12512202d27cfb7ddabd2ba2cc6509d9464c

Open report
Separate monitor record · 2026-10-25 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1713b-7fa3-77ea-b245-6d44d02fc2d5
score
0
malicious
false
result_at
2026-10-25T04:30:43Z
enriched_at
2026-10-25T09:11:58Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:43","urlscan_enriched_at":"2026-10-25 10:11:58"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy DOM

71 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 40 / 100 · 2026-10-25T07:20:22Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
40
analyzed_at
2026-10-25T07:20:22Z
source_timestamp
2026-10-25 08:20:22
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
Observed page title
Files Collection
Automated brand references
Google
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 49 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation Singapore43.174.247.29 abuse score 7/100 5 reports PhishingOpen ProxyEmail SpamBad Web Bot checked Oct 25, 2026 last reported
Registrar (base domain) Tencent Cloud
Abuse contactas139341_abuse@aceville.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for edgeone.dev →
Hosting abuse contact as139341_abuse@aceville.net ACE-AS-AP - ACE, SG · AS139341
Registration (base domain)edgeone.dev · Created Jun 9, 2025 — Expires Jun 9, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 71/1001 brand signal
Submitted URLhttp://curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev/
ICANN OVERSIGHT Registration: edgeone.dev

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain edgeone.dev behind this subdomain, 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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Singapore43.174.247.29
Network ASN
AS139341
Organization
ACE-AS-AP - ACE, SG
Observed location
SingaporeSG
Server header
edgeone makers

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-17 02:52:54
Valid until
2026-12-16 02:52:53
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-25 05:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6d538285ba8e76e272733030941a0f13d96a5ad70d8ff34789947928afe7b1fa
Certificate names · 1 SAN
  • edgeone.dev

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 43.174.247.29rapiddns.io

Latest Classified Outcome 2026-10-27 11:02:12 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-27 11:02:12 UTC
RDAP registration
Observed timeline last reachable: 2026-10-26 00:13:52 UTC last content: 2026-10-26 00:13:52 UTC
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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
SOCRadar
VIPRE
Webroot
Yandex Safebrowsing

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev/
Final URL: https://curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev/
Files Collection
Response
HTTP 200
HTML body
22.3 KB
Compressed
3.3 KB
Links
0 internal · 17 external
Selected response headers
Content-Type: text/html
Cache-Control: public,max-age=0,must-revalidate
Content-Encoding: gzip
Server: edgeone makers
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 15
Accept-Ranges
bytes
Age
496474
Cache-Control
public,max-age=0,must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Length
3397
Content-Type
text/html
Date
Sun, 25 Oct 2026 04:01:01 GMT
EO-Cache-Status
Cache Hit
EO-LOG-UUID
7908671640298342519
Etag
"9cf12045bbe0f0d6b13c5915ddf952bf"
Last-Modified
Mon, 19 Oct 2026 08:58:26 GMT
Server
edgeone makers
Vary
Origin, Access-Control-Request-Headers, Access-Control-Request-Method
X-NWS-LOG-UUID
7908671640298342519

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations10

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:12.000000
    Evidence SHA-256
    8f5c3549aae35489582ec817cdb51de731c46a31a3af3e4e1f9cfc212b87099f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:12
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:12.000000
    Evidence SHA-256
    8f5c3549aae35489582ec817cdb51de731c46a31a3af3e4e1f9cfc212b87099f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:12
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:10.000000
    Evidence SHA-256
    e70b67595ee575349b55bfafe5eb7724f6e8808435f2cb5bde5ef1847b29817c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:10
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:10.000000
    Evidence SHA-256
    e70b67595ee575349b55bfafe5eb7724f6e8808435f2cb5bde5ef1847b29817c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:10
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:13:52.000000
    Evidence SHA-256
    665f80651046bc8fa69ac9a508b8d3c60e33101f58e55cb148db1bfa35e97e04
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:13:52
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:13:52.000000
    Evidence SHA-256
    665f80651046bc8fa69ac9a508b8d3c60e33101f58e55cb148db1bfa35e97e04
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:13:52
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:17:16.000000
    Evidence SHA-256
    e1068554c351cf631743807e05a4acc6f4745c5af47595a7136ea675de5082eb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:17:16
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:17:16.000000
    Evidence SHA-256
    e1068554c351cf631743807e05a4acc6f4745c5af47595a7136ea675de5082eb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:17:16
    Evidence reason
    alive_content
  9. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:06:05.000000
    Evidence SHA-256
    43093948ab00d074ae7c5e70d067252f95709fef6d65d94bdb495101c2c44177
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 05:06:05
    Evidence reason
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:06:05.000000
    Evidence SHA-256
    43093948ab00d074ae7c5e70d067252f95709fef6d65d94bdb495101c2c44177
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 05:06:05
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. VirusTotal

    4/92 engine detections

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev

    View source
  4. URLScan

    Page captured

    View source
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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.

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev"
  title="PhishDestroy threat report for curly-turquoise-twt5ttp0-dp0wdco785zo.edgeone.dev"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>