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.
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.
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 / 924 sources
SourceResultRecorded · UTCOpen
VirusTotal
18 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 15 fields
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.
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.
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.
Issued by Google Trust Services / WE1· stored validity ends in 28 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.64.151.8
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
Toronto, 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 fingerprint5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7Certificate 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.
No phishing content was served at the latest check.
Technical details
Primary outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: Stale
Latest HTTP observationInactiveHttp No Content70%2026-11-22 11:14 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-18 12:13 UTCcurrent episode first observed: 2026-11-19 00:08 UTCobserved RIP window: 2026-11-18 12:13 UTC → 2026-11-19 00:08 UTC · 11.92hmidpoint 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.
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.
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including 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)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.