Skip to security report
Analytics Dashboard
Domain security report
fbshop689.com favicon

fbshop689.com

“Meta Business”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 21/93 URLQuery threat systems: 5 alerts Automated brand label: Generic
Mar 2, 2026 Generic 1 Report Sent
API
Registrar
Dynadot
Resolved IP
69.5.20.142
Registered
Mar 2, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 21. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
21 det.
URLQuery
URLQuery
5 threat alerts
DNS Security
6/14
CF Radar
Malicious
URLScan
URLScan
Report ↗
TLS Certificate
Hostname mismatch
E8 · Certificate hostname mismatch
Age
8 mo
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

10 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

21 / 93

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

5 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan verdict

malicious

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

DNS blocks

6/14

Observation time not recorded
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

PhishStats

checked — no match recorded

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Observation time not recorded
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
DNS Provider Blocks 6 / 14
Brand Hop Cloudflare Family Cloudflare Security Controld Adblock Controld Family Controld Malware
Dangerous · Checked 14 DNS providers: Quad9, AdGuard, ControlD, CleanBrowsing & more
Threat Detection Systems 5 alerts
Detection System Indicator Verdict Alert
OpenDNS fbshop689.com phishing Phishing Block
Cloudflare DNS fbshop689.com malicious Sinkholed
DNS4EU fbshop689.com malicious Sinkholed
Hagezi Threat Feed fbshop689.com malicious Sinkholed
DigiCert UltraDNS fbshop689.com malicious Sinkholed
Stored URLQuery scan evidence · Mar 2, 2026 13:15 UTC Open source report
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Security Risks Phishing
View full Cloudflare Radar report

Evidence Summary

Critical
VirusTotal
21/93
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

This domain, fbshop689.com, is identified as a phishing site designed to impersonate official Meta Business platforms. The primary threat involves credential harvesting, where visitors are tricked into entering sensitive login details, such as Facebook or Instagram business account credentials, into fraudulent forms. The site may also distribute malware or redirect users to additional malicious pages under the guise of legitimate Meta services. Given its focus on business accounts, the potential impact includes unauthorized access to advertising accounts, financial data, or corporate social media profiles. Analysis indicates this domain was registered on March 02, 2026, through Dynadot LLC, a registrar commonly used for both legitimate and malicious domains. It resolved to the IP address 69.5.20.142, hosted under AS150436 (Byteplus Pte. Ltd.) in Indonesia. The SSL certificate was issued by Let's Encrypt, a common tactic to lend false legitimacy to phishing sites. At the time of detection, 21 out of 95 security vendors on VirusTotal flagged fbshop689.com as malicious. The page title, Meta Business, directly mimics official Meta branding, increasing the likelihood of successful deception. The domain has since been taken offline, but similar threats may reappear under different names. If you visited fbshop689.com or entered any credentials, immediate action is required. First, revoke access to any accounts linked to the site by changing passwords and enabling multi-factor authentication. Review account activity for unauthorized logins, ad campaigns, or financial transactions. Check connected devices for malware, particularly if files were downloaded or browser extensions were installed. Report the incident to your organization’s security team or the official Meta Business support channels to assist in mitigating potential damage. Monitor credit reports and financial statements for signs of fraudulent activity, as stolen credentials may be used for broader attacks.

Data coverage & collection

25 · datasets with records / 6 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
21 / 93 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
5 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
PhishStats
Dated lookup retained
Cloudflare Radar
maliciousCollection time not recorded
DNS security filters
6 / 14 · provider blocksCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Dynadot LLCCollection time not recorded
Network & DNS
69.5.20.142 · 1 · nameserversCollection time not recorded
TLS certificate
E8
Page captures
3 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
59/100 · mobile performance
Response records
1 · outgoing report records
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
16 · stored state changes
Source observation history
6 · stored source events
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 6

These checks have no retained result. This does not mean they passed or that a scan is running.

  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Lookalike relationships
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Dynadot LLC · 69.5.20.142 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Reputation abuse score 0/100 0 reports checked Jun 14, 2026
Registrar Dynadot US(US)
Abuse contactbd_abuse@bytedance.com, abuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for fbshop689.com →
RegistrationCreated Mar 2, 2026 (228d)
Time to First Unavailability 13 days
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 DetectedMar 2, 2026
DOM Analysisanalyzed Jul 29, 2026score 73/1001 brand signal
Submitted URLhttp://fbshop689.com/
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
69.5.20.142
Network ASN
AS150436
Organization
Byteplus Pte. Ltd.
Observed location
Jakarta, ID
Server header
nginx
Nameservers 1
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
E8
Valid from
2026-02-26 11:50:55
Valid until
2026-05-27 11:50:54
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-15 05:52:44 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc1a939fe17ae8282ea632a77ece2222eb677418f0e73e7abdbdca744f68c416f
Certificate names · 9 SANs
  • fbshop687.com
  • fbshop688.com
  • fbshop690.com
  • fbshop691.com
  • www.fbshop687.com
  • www.fbshop688.com
  • www.fbshop689.com
  • www.fbshop690.com
  • www.fbshop691.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 · 69.5.20.142rapiddns.io

Latest Classified Outcome 2026-10-16 20:22:38 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-17 01:07:33 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-03-15 11:09:02 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-03-15 11:09:02 UTC → 2026-09-30 16:14:55 UTC · 4,781.10h midpoint estimate ≈ 2026-06-23 01:41:58 UTC · precision very low · 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.

  • www.fbshop689.comDomain record

The original observation time is not recorded for these hostnames.

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

21 / 93 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
Cluster25
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
MalwareURL
OpenPhish
Seclookup
SOCRadar
Sophos
Trustwave
VIPRE

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 fbshop689.com · checked Mar 2, 2026

59
Needs Work
Performance
FCP
5.53s
First Contentful Paint
LCP
5.6s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
114ms
Total Blocking Time
SI
11.72s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
4781.1
Estimate basis
Bounded by observations
Estimate precision
very_low

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fbshop689.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Unreachable

Timeline & response

1 · outbound report records

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.
  1. VirusTotal Detections Update 2026-03-11 02:39:13 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 21 to 19.
  2. VirusTotal Detections Update 2026-03-09 02:29:27 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 21 to 19.
  3. VirusTotal Detections Update 2026-03-06 04:10:06 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 21 to 19.
  4. VirusTotal Detections Update 2026-03-04 02:07:48 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 21 to 19. Resolved alerts: DNS8, OpenPhish.
  5. Cloudflare Radar Scan 2026-03-02 21:30:07 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  6. VirusTotal Detections Update 2026-03-02 15:15:52 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 19. Added scanner alerts: ADMINUSLabs, BitDefender, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, MalwareURL, OpenPhish, SOCRadar, Seclookup, Sophos, Trustwave, VIPRE, alphaMountain.ai.
Stored observation history22

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

    dns_inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

Earlier observations 17
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  9. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  11. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  12. VirusTotal · Detection count

    21→19

  13. VirusTotal · Detection count

    21→19

  14. VirusTotal · Detection count

    21→19

  15. VirusTotal · Detection count

    21→19

  16. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/cd9e97c2-9afd-43ad-8bf3-dd4beb102eb3

  17. VirusTotal · Detection count

    0→19

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
fbshop689.com detected and queued for full analysis
Mar 2, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
URLScan Verdict
URLScan returned a malicious verdict · score 100
Jul 29, 2026
Cloudflare Radar Report
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 Wayback Machine — historical evidence archived
Mar 14, 2026
VirusTotal
21/93 recorded on VirusTotal
Mar 2, 2026
DNS Security Blocks
Blocked by 6 of 14 checked DNS providers: Brand hop, Cloudflare family, Cloudflare security, Controld adblock
CF Radar: Malicious
Cloudflare Radar classified this domain as Security threats, Phishing, Security Risks, phishing
Brand Impersonation
Impersonation of Generic
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
VT Detection -2
2 detections removed (21 → 19)
Mar 11, 2026
VT Detection -2
2 detections removed (21 → 19)
Mar 9, 2026
VT Detection -2
2 detections removed (21 → 19)
Mar 6, 2026
VT Detection -2
2 detections removed (21 → 19)
Mar 4, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 2, 2026
VT Detection +19
+19 new detections (0 → 19): ADMINUSLabs, BitDefender, CRDF, CyRadar +15
Mar 2, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Dynadot LLC, 2 abuse contacts
bd_abuse@bytedance.comabuse@dynadot.com
Mar 2, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Mar 2, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Mar 15, 2026
Time to First Unavailability
317 hours elapsed from detection to the first unavailable observation.
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

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Mar 2, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 21 det. ChainPatrol URLQuery 5 threat alerts SSL Labs Certificate hostname mismatch CF Radar Malicious DNS Security 6/14 WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260302-57F086 Recipient: bd_abuse@bytedance.com
Page title stored with report: Meta Business
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Content unavailable
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 fbshop689.com)
  • 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
Read the evidence in context

About This Report: fbshop689.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Meta Business”. Apparent target: Generic.

VirusTotal detections for fbshop689.com: 21 (2026-03-02 19:00:26 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A 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/fbshop689.com"
  title="PhishDestroy threat report for fbshop689.com"
  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>