Skip to security report
sbc-verifier-sign-in-5119de.webflow.io favicon
Domain security and threat intelligence

sbc-verifier-sign-in-5119de.webflow.io

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

This page mimics an SBC Communications sign-in portal to harvest user credentials and account details. If you entered your password here, change it immediately on the official service.

Page title: “sbc verifier sign in”

More about the sources
Recorded security signals

Stored VirusTotal result: 18/92 engines flagged. Malicious: 17. Suspicious: 1. Analysis time (as stored): 2026-11-17 14:37 UTC. Retrieved (as stored): 2026-11-18 09:43 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 18/92
Registrar
MalaysiaWebflow
Resolved IP
Canada172.64.151.8Cloudflare, Inc. · CDN
Registered
2013-05-08
First seen by PhishDestroy
2026-11-18
Page captures
open gallery
Domain age
registered 2013-05-08 according to RDAP · source data differ
2026-11-18 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded sbc-verifier-sign-in-5119de.webflow.io on 2026-11-18. Stored VirusTotal result: 18/92 engines flagged. Malicious: 17. Suspicious: 1. Analysis time (as stored): 2026-11-17 14:37 UTC. Retrieved (as stored): 2026-11-18 09:43 UTC. Risk: critical (evidence score 95/100). Registrar: Webflow. Status: HTTP 404 · Content unavailable. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
HTTP 404 · Content unavailable
VirusTotal
18 / 92
Hosting
Canada172.64.151.8Cloudflare, Inc. · CDN
Registrar
MalaysiaWebflow
Registered
2013-05-08
Page captures
5

URLScan capture · 2026-11-17 18:00 UTC · SHA-256 cbe21cb9…c2b6541

PhishDestroy analysis, reviewed version

Visual layout and credential harvesting interface

The page hosted at sbc-verifier-sign-in-5119de.webflow.io presents a clean white background featuring the prominent blue SBC globe logo and the text "SBC". Below the branding, it displays input fields labelled "Email Address/User ID" and "Password", accompanied by a blue "Sign In" button and a link for "Sign-in options". Further down the page, explanatory text describes "SBC Communications Inc." along with historical details referencing its origins from the breakup of AT&T and related category links. The layout is designed to trick visitors into believing they are accessing a legitimate telecom sign-in portal. By prompting users to submit their credentials directly into these fields, the site aims to capture sensitive login information for unauthorized access.

Security detections and independent threat verification

18 of 92 VirusTotal engines flagged it on 17 Nov 2026, and OpenPhish blocks it, which confirms that the risk is recognized across multiple security platforms. PhishDestroy's evidence score for it is 75/100 (critical), indicating a high level of threat for users who encounter the link. Because the site still responded on 18 Nov 2026 at 10:40 UTC, visitors continue to face active exposure if they navigate to the URL.

Recommended actions for affected visitors

Anyone who entered credentials on this page should immediately update their passwords on the legitimate service and any other accounts sharing the same credentials. Monitor associated email and financial accounts for unauthorized activity. Report the abusive URL directly to the platform provider at webflow.io to request removal.

Source evidenceVirusTotal 18 / 92 4 sources

VirusTotal

18 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

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.

Source
VirusTotal
Result state
observed
Numerator
18
Denominator
92
Vendors
alphaMountain.ai, BitDefender, DNS8, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, LevelBlue, Lionic, Netcraft, OpenPhish, Phishtank, SOCRadar, Sophos, VIPRE, Webroot
Observed at
2026-11-17 14:37:43
Checked at
2026-11-18 10:43:12
Fetched at
2026-11-18 09:43:12

URLScan

Page capture

SHA-256 6b625cb7…79e7711

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record · 2026-11-19 04:30 UTC

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

UUID
01a1ee06-b8ec-70b9-8214-6f6b4cfaa524
Score
0
Malicious
✗
Result at
2026-11-19T04:30:18Z
Enriched at
2026-11-19T09:13:04Z
Source timestamps
Urlscan result at: 2026-11-19 05:30:18; Urlscan enriched at: 2026-11-19 10:13:04
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
sbc-verifier-sign-in-5119de.webflow.io — SBC credential form
AI description
sbc-verifier-sign-in-5119de.webflow.io copies an SBC sign-in portal to capture credentials, noted as flagged by 18 VirusTotal engines. Protect your account.
AI summary
Visual layout and credential harvesting interface The page hosted at sbc-verifier-sign-in-5119de.webflow.io presents a clean white background featuring the prominent blue SBC globe logo and the text "SBC". Below the branding, it displays input fields labelled "Email Address/User ID" and "Password", accompanied by a blue "Sign In" button and a link for "Sign-in options". Further down the page, explanatory text describes "SBC Communications Inc." along with historical details referencing its origins from the breakup of AT&T and related category links. The layout is designed to trick visitors into believing they are accessing a legitimate telecom sign-in portal. By prompting users to submit their credentials directly into these fields, the site aims to capture sensitive login information for unauthorized access. Security detections and independent threat verification 18 of 92 VirusTotal engines flagged it on 17 Nov 2026, and OpenPhish blocks it, which confirms that the risk is recognized across multiple security platforms. PhishDestroy's evidence score for it is 75/100 (critical), indicating a high level of threat for users who encounter the link. Because the site still responded on 18 Nov 2026 at 10:40 UTC, visitors continue to face active exposure if they navigate to the URL. Recommended actions for affected visitors Anyone who entered credentials on this page should immediately update their passwords on the legitimate service and any other accounts sharing the same credentials. Monitor associated email and financial accounts for unauthorized activity. Report the abusive URL directly to the platform provider at webflow.io to request removal.
AI generated by
threat-v10-gemini
AI generated at
2026-11-18T09:45:49Z
Revision
678cca87449d7848c723c5205371956f848038103b5f73947a659c875f9dd0ed
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
3071

Page title and metadata

Page title
sbc verifier sign in
Generator
Webflow

Trackers

Requests
6
Observed services
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Webflow
    Company
    Webflow
    Country
    US
    Category
    Hosting
    Requests
    5

Forms and mixed content

Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
73
Download
1
Response time, ms
105

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
3647
CO₂, grams
0.0001
Cleaner than, %
94

DNS servers

Nameservers
  • IP address
    108.162.194.3
    Host
    journey.ns.cloudflare.com
  • IP address
    162.159.44.142
    Host
    lamar.ns.cloudflare.com
DNS zone
webflow.io

Page quality

Layout shift (CLS)
0.26
SEO score
91
Speed Index, s
1.84
First Contentful Paint (FCP), s
1.84
Largest Contentful Paint (LCP), s
1.96
Total Blocking Time (TBT), ms
0
Performance score
85
Accessibility score
93
Best practices score
100

Location

IP address
2a06:98c1:3105::6812:24f8
ASN
13335
Organization
Cloudflare, Inc.
City
London
Country
GB

TLS certificate

Subject alternative names
  • webflow.io
  • *.webflow.io
Key size, bits
256
Certificate chain
  • webflow.io
  • WE1
  • GTS Root R4
Issuer
Google Trust Services / WE1
Serial
AC972EF95A18AB8F0E5A2917E958D6DA
SHA-256
5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7
Subject
webflow.io
Valid until
Valid from

DNS records

A
  • 104.18.36.248
  • 172.64.151.8
AAAA
  • 2a06:98c1:3105::6812:24f8
  • 2a06:98c1:3102::ac40:9708

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3102::ac40:9708
IP version
6

Redirects

Redirect chain
  • https://sbc-verifier-sign-in-5119de.webflow.io

Technology stack

Technologies
  • Webflow
  • jQuery 3.5.1
  • Cloudflare Turnstile
  • Cloudflare
  • HTTP/3

Page links

Internal link addresses
  • https://sbc-verifier-sign-in-5119de.webflow.io/
Internal links
1

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
Content-Security-Policy
frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com
Link
<https://cdn.prod.website-files.com>; rel=preconnect; crossorigin, <https://cdn.prod.website-files.com/6afb07fd594a46e0db160ff8/css/sbc-verifier-sign-in-5119de.webflow.shared.c80b86783.css>; rel=preload; as=style; crossorigin; integrity="sha384-yAuGeDHM5dvqfxmmSsBMme6Kl0L/Cg1HrxprOdUwfU0z3b3JPCi73J5
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Web archive observations
Last: 2026-11-18T01:29:09Z; First: 2026-11-18T01:29:09Z; Changes: 0; Days archived: 1; Avg page bytes: 3071
Page title and metadata
Title: sbc verifier sign in; Generator: Webflow
Trackers
Requests: 6; Trackers: (Name: Amazon CloudFront; Company: Amazon; Country: US; Category: Hosting; Requests: 1), (Name: Webflow; Company: Webflow; Country: US; Category: Hosting; Requests: 5)
Forms and mixed content
Third party scripts: 2
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 73; Download: 1; Response ms: 105
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 3647; Co2 grams: 0.0001; Cleaner than: 94
DNS server
NS: (IP: 108.162.194.3; Host: journey.ns.cloudflare.com), (IP: 162.159.44.142; Host: lamar.ns.cloudflare.com); Zone: webflow.io
Quality
Cls: 0.26; Seo: 91; Si s: 1.84; Fcp s: 1.84; Lcp s: 1.96; Tbt ms: 0; Performance: 85; Accessibility: 93; Best practices: 100
Location
IP: 2a06:98c1:3105::6812:24f8; ASN: 13335; Org: Cloudflare, Inc.; City: London; Country: GB
SSL
San: webflow.io, *.webflow.io; Bits: 256; Chain: webflow.io, WE1, GTS Root R4; Issuer: Google Trust Services / WE1; Serial: AC972EF95A18AB8F0E5A2917E958D6DA; SHA256: 5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7; Subject: webflow.io; Valid to: 2026-12-21T03:46:57Z; Valid from: 2026-09-22T02:47:08Z
DNS records
A: 104.18.36.248, 172.64.151.8; Aaaa: 2a06:98c1:3105::6812:24f8, 2a06:98c1:3102::ac40:9708
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2a06:98c1:3102::ac40:9708; Family: 6
Redirects
Chain: https://sbc-verifier-sign-in-5119de.webflow.io
Tech stack
Technologies: Webflow, jQuery 3.5.1, Cloudflare Turnstile, Cloudflare, HTTP/3
Page links
Internal: https://sbc-verifier-sign-in-5119de.webflow.io/; Internal count: 1
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8; Content security policy: frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com; Link: <https://cdn.prod.website-files.com>; rel=preconnect; crossorigin, <https://cdn.prod.website-files.com/6afb07fd594a46e0db160ff8/css/sbc-verifier-sign-in-5119de.webflow.shared.c80b86783.css>; rel=preload; as=style; crossorigin; integrity="sha384-yAuGeDHM5dvqfxmmSsBMme6Kl0L/Cg1HrxprOdUwfU0z3b3JPCi73J5
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Questions about sbc-verifier-sign-in-5119de.webflow.io

Is sbc-verifier-sign-in-5119de.webflow.io a legitimate site?

It has been flagged by 18 VirusTotal engines by security scanners.

What happens if I entered my password on this page?

Your login credentials have likely been exposed to malicious actors. You should change your password immediately on your real account and enable multi-factor authentication.

How can I report this fraudulent domain?

You can report the URL to the hosting provider webflow.io and security vendors so they can take down the infrastructure. Prompt reporting helps protect other potential victims from falling into the same trap.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 100 report ↗
IP Context Canada172.64.151.8 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Webflow MY(MY)
Abuse contactabuse@webflow.com
Registration (base domain)webflow.io · Created 2013-05-08
HTTP Status404 Not Found
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-18
DOM Analysisanalyzed 2026-11-18score 0/100
Submitted URLhttps://sbc-verifier-sign-in-5119de.webflow.io/
Observed page title
sbc verifier sign in
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 28 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.64.151.8
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • journey.ns.cloudflare.com
  • lamar.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-22 02:47:08
Valid until
2026-12-21 03:46:57
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7
Certificate names · 2 SANs
  • webflow.io
  • *.webflow.io

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

Latest Classified Outcome 2026-11-22 11:14 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale
Latest HTTP observation Inactive Http No Content 70% 2026-11-22 11:14 UTC
RDAP registration
Observed timeline last reachable: 2026-11-18 12:13 UTC current episode first observed: 2026-11-19 00:08 UTC observed RIP window: 2026-11-18 12:13 UTC → 2026-11-19 00:08 UTC · 11.92h midpoint estimate ≈ 2026-11-18 18:10 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.
Technologies · 3 identified
Open complete records

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
LevelBlue
OpenPhish
Phishtank
Gridinsoft
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker
PageSpeed (mobile): 85

Google PageSpeed Insights — mobile performance audit of sbc-verifier-sign-in-5119de.webflow.io ·

85
Needs Work
Performance
FCP
1.7 s
First Contentful Paint
LCP
1.85 s
Largest Contentful Paint
CLS
0.26
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.7 s
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
11.92
Estimate basis
Bounded by observations
Estimate precision
Medium

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

All stored data107
Open complete records

Captured network requests

Network requests: 11 SHA-256 hashes: 10 URLScan scan:

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-11-18 09:43 UTC.

Open this scan on URLScan 01a1ee06-b8ec-70b9-8214-6f6b4cfaa524 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
sbc verifier sign in
Crawler
404 - Page not found
sbc-verifier-sign-in-5119de.webflow.io
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

    No page content

    no page content in the HTTP response

  2. Domain monitor · First collection record

    Reachable

All retained availability observations9
Open complete records

Threat Response Pipeline

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

Recorded events: 9. 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
  • Threat Ingested
    sbc-verifier-sign-in-5119de.webflow.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+4941 d 12 h
  3. Added to PhishDestroy+19 h 2 min
  1. Cloudflare Radar

    Phishing

    +3 min
  2. Added to PhishDestroy

    sbc-verifier-sign-in-5119de.webflow.io

    same minute
  3. URLScan

    Page captured

    +19 h 2 min
  4. VirusTotal

    18/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
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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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.

  • 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 sbc-verifier-sign-in-5119de.webflow.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

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.

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.

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/sbc-verifier-sign-in-5119de.webflow.io"
  title="PhishDestroy threat report for sbc-verifier-sign-in-5119de.webflow.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>