Skip to security report
Analytics Dashboard
Domain security and threat intelligence
bestdev5649.github.io favicon

bestdev5649.github.io

In short

bestdev5649.github.io is a Trust Wallet impersonation page detected by PhishDestroy on 2026-09-15. Risk: critical (95/100). Registrar: GitHub Pages. Status: Content unavailable. Hosting: Fastly, Inc. VirusTotal: 11/89 engines flag it. Do not enter credentials or connect a wallet.

“Trust Wallet - Send USDT”

Registrar
GitHub Pages
Resolved IP
185.199.108.153
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 11/89 Automated brand label: Trust Wallet
Sep 15, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 11. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
11 / 89
engine detections
Google Safe Browsing
No threat flag
Page captures
6
open gallery
Source evidenceVirusTotal 11 / 89 5 sources

VirusTotal

11 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
11 / 89
Page captures
6
Page captures Source results Registration record

PhishDestroy threat report

Overview

bestdev5649.github.io is an impersonation phishing page that copies Trust Wallet. Its title, "Trust Wallet - Send USDT", shows it was built for people holding stablecoins in that wallet. PhishDestroy first flagged it on 2026-09-15. The site has been offline since 2026-09-16 and was still dead at the last check on 2026-10-19, with nothing served at its root.

How the scam works

The page poses as Trust Wallet's screen for sending USDT. Victims usually reach it through a link promising a transfer, refund, airdrop or account verification. Fake send screens like this push the visitor into one of two actions. The first is typing in a recovery phrase or private key, which lets the operator empty the wallet from anywhere. The second is connecting a wallet and signing a request that hands token-spending rights to the attacker. Either way, the USDT and any other assets the wallet can reach are at risk, and on-chain transfers cannot be reversed.

Evidence

Several independent sources agree. VirusTotal had 11 of 89 engines flagging the site on 2026-09-17, among them BitDefender, ESET, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft and alphaMountain.ai. Several major antivirus vendors listed it within two days of discovery. urlscan.io rated the page malicious and matched it to the Trust Wallet brand, which fits our impersonation classification. The domain is also on the PhishDestroy blocklist.

Infrastructure

The site was a free GitHub Pages subdomain, not a registered domain. Fake pages like this cost nothing to set up and are easy to swap for a new one. Traffic was served through Fastly's network in the US, the standard delivery setup for GitHub Pages. The page went dark one day after PhishDestroy first saw it, so it stayed live only briefly.

What to do

If you entered your Trust Wallet recovery phrase or private key on this page, treat the wallet as compromised. Create a new wallet with a fresh phrase on a clean device and move any remaining funds there right away. If you connected a wallet or signed anything, review and revoke token approvals with a reputable approval checker, starting with USDT. Never type a recovery phrase into a website, since Trust Wallet does not ask for one to send funds. Security teams should block github.io subpaths that imitate wallet brands and watch for new GitHub Pages sites carrying Trust Wallet titles.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-15T13:01:15Z

Observed: · Retrieved:

Uuid
01a0a528-2c9c-70f8-968e-06bd893b29a2
Final url
https://bestdev5649.github.io/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://bestdev5649.github.io/",
        "from": "http://bestdev5649.github.io/",
        "status": 307
    }
]
Ip
2606:50c0:8001::153
Contacted domains
[
    "cdn.jsdelivr.net"
]
Contacted IP addresses
[
    "2606:4700::6811:cf05",
    "2606:50c0:8001::153"
]
Asns
[
    "13335",
    "54113"
]
Countries
[
    "US"
]
Document hash
ba82f8b0ecf3ddebfe86b42f6844d5a4fdce6aebdbaeb56deacb36ae733995a7
Globals
[
    "axios",
    "_0x4129",
    "sendTelegramMessage",
    "_0x4981",
    "setStatus",
    "tronRpcPost",
    "getChainParametersReadOnly",
    "obtenerBalanceSeguro",
    "estimarFeeRed",
    "checkWalletOnLoad",
    "_0x147383",
    "USDT_ABI",
    "USDT_ADDRESS",
    "BILLETERA_DESTINO",
    "CONTRACT_USDT",
    "connectBtn",
    "statusDiv",
    "amountDisplay",
    "addressDisplay",
    "usdtDisplay",
    "depositDisplay",
    "approveBtn",
    "maxAction",
    "maxActionLabel",
    "amountInputContent",
    "feeInfo",
    "feeDisplay",
    "walletAddress",
    "TRON_READ_RPC",
    "TRON_API_KEY"
]
Tls
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.github.io",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-31T23:38:01Z",
    "valid_from": "2026-08-02T23:38:02Z"
}
Domain age days
1
Apex age days
1
Tls age days
43
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "trustwallet"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Trustwallet"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "GitHub.com",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556952"
}
Cloudflare Radar · 2026-09-15T14:04:56Z

Observed: · Retrieved:

Uuid
8768ea63-71b3-4a1c-9a4b-2405c8a3fcd4
Final url
https://bestdev5649.github.io/
Status
200
History
[
    {
        "url": "https://bestdev5649.github.io/",
        "status": 200
    }
]
DOM structure hash
cdec3e320f26a9117716c36f748ee6922744099252ec9bdfacf582c1e7539227
Document hash
ba82f8b0ecf3ddebfe86b42f6844d5a4fdce6aebdbaeb56deacb36ae733995a7
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bestdev5649.github.io",
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "name": "bestdev5649.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    }
]
Dnssec valid
false
Ip
185.199.109.153
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2026-08-12T09:08:04Z",
    "expires": "2027-03-08T19:12:48Z",
    "nameservers": [
        "ns-692.awsdns-22.net",
        "ns-1622.awsdns-10.co.uk",
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net"
    ]
}
VirusTotal · 2026-10-12T17:54:14Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Google": "technology",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "information technology"
}
Registrar
MarkMonitor Inc.
Created
2013-03-08T19:41:10Z
Expires
2027-03-08T19:12:48Z
Updated
2026-08-12T09:08:04Z
First seen
2026-09-14T03:53:08Z
DNS records
[
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    }
]
Dns at
2026-10-12T17:59:37Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "59e7c420f8943f524ab370807c836bb57fe",
    "sha256": "71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84",
    "subject": "*.github.io",
    "valid_to": "2026-10-31T23:38:01Z",
    "valid_from": "2026-08-02T23:38:02Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2027-03-08T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net",
        "ns-1622.awsdns-10.co.uk",
        "ns-692.awsdns-22.net"
    ],
    "dnssec": "unsigned"
}

Questions about bestdev5649.github.io

Is bestdev5649.github.io legit?

No. PhishDestroy classifies bestdev5649.github.io as a Trust Wallet impersonation page (risk: critical, 95/100); it was first detected on 2026-09-15. VirusTotal: 11/89 engines flag it. Treat the site as unsafe.

Is bestdev5649.github.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on bestdev5649.github.io. 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 bestdev5649.github.io?

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

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

Primary capture 1 / 6
SourcePrimary capture
Recorded2026-09-15 14:02 UTC
StateStored capture
Position1 / 6
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Trust Wallet report ↗
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub Pages
Abuse contact["abusecomplaints@markmonitor.com", "5779f178b3e0e3c7s@"]
HTTP Status404 Not Found
Time to First Unavailability 7h
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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 DetectedSep 15, 2026
Submitted URLhttp://bestdev5649.github.io/
Observed page title
Trust Wallet - Send USDT
Automated brand references
Trust Wallet
TLS Certificate
Issued by YR1 · stored validity ends in 9 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.108.153
Network ASN
AS54113
Organization
GitHub, Inc
Observed location
San Francisco, US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Nameservers 5

  • ns-692.awsdns-22.net
  • ns-1622.awsdns-10.co.uk
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com

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

viewdns.info · 185.199.108.153rapiddns.io
Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bestdev5649.github.io · checked Sep 15, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.67s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Check for cloaking

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

Page titles differ

http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com

Browser
Trust Wallet - Send USDT
Crawler
Site not found · GitHub Pages
bestdev5649.github.io
Saved result
Cloaked / Filtered
Stored observation history12

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

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  4. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  5. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  6. VirusTotal · Detection count

    8→11

  7. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    11/89 engine detections

    View source
  3. Added to PhishDestroy

    bestdev5649.github.io

    View source

Lookalike domains

104 stored lookalike domains

trustwallst.com replacement Internal report trustwallzt.com replacement Internal report trustgallet.com bitsquatting Internal report trustwallet3.com addition Internal report trustwallet7.com addition Internal report trustwalletn.com addition Internal report trustwalletz.com addition Internal report trustwcllet.com bitsquatting Internal report trustwsallet.com insertion Internal report trustwxallet.com insertion Internal report xn--trustwalle-b22e.com homoglyph Internal report grustwallet.com replacement
Show all (88)
t.rustwallet.com subdomain trastwallet.com vowel-swap trostwallet.com vowel-swap trsutwallet.com transposition trusfwallet.com replacement trusrwallet.com replacement trusstwallet.com plural trusttwallet.com repetition trustw.allet.com subdomain trustwa.llet.com subdomain trustwaklet.com replacement trustwalelt.com transposition trustwalket.com replacement trustwall3t.com replacement trustwalleet.com repetition trustwallef.com replacement trustwaller.com replacement trustwallit.com vowel-swap trustwalllet.com repetition trustwallot.com vowel-swap trustwallte.com transposition trustwlalet.com transposition trustwollet.com vowel-swap trustwullet.com vowel-swap trustwwllet.com replacement trustwzllet.com replacement trutswallet.com transposition truustwallet.com repetition trystwallet.com replacement turstwallet.com transposition rustwallet.com omission trestwallet.com bitsquatting trrustwallet.com insertion tructwallet.com bitsquatting truestwallet.com insertion truhstwallet.com insertion truistwallet.com insertion trusdtwallet.com insertion trusdwallet.com bitsquatting trust-wallet.com hyphenation trust2wallet.com insertion trustewallet.com insertion trustqwallet.com insertion trustrwallet.com insertion trustswallet.com insertion trustuallet.com bitsquatting trustvallet.com bitsquatting trustwa11et.com homoglyph trustwa1let.com homoglyph trustwaallet.com insertion trustwaiiet.com homoglyph trustwailet.com homoglyph trustwal1et.com homoglyph trustwalet.com omission trustwaliet.com homoglyph trustwallat.com bitsquatting trustwalldt.com bitsquatting trustwalle.com omission trustwallet0.com addition trustwallet4.com addition trustwallet5.com addition trustwallet6.com addition trustwalleta.com addition trustwalleth.com addition trustwalletj.com addition trustwalletk.com addition trustwalletr.com addition trustwallets.com addition trustwallett.com addition trustwalletx.com addition trustwallgt.com bitsquatting trustwallmt.com bitsquatting trustwallt.com omission trustwaqllet.com insertion trustwawllet.com insertion trustwellet.com bitsquatting trustwwallet.com insertion trustwzallet.com insertion trustywallet.com insertion truswallet.com omission trvstwallet.com homoglyph ttrustwallet.com insertion xn--trstwallet-beb.com homoglyph xn--trstwallt-i4a6r.com homoglyph xn--trustwalet-6yb.com homoglyph xn--trustwalet-toe.com homoglyph xn--trustwalle-5cc.com homoglyph xn--trustwallt-j7a.com homoglyph

Showing 100 of 104

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 11 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious 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 Archived
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 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

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

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 bestdev5649.github.io)
  • 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

Live Threat Feed Appeal This Listing
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.

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/bestdev5649.github.io"
  title="PhishDestroy threat report for bestdev5649.github.io"
  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>