PhishDestroy first recorded cccomcmaasttxxffintuy.weebly.com on 2026-10-26. Stored VirusTotal result: 11/92 engines flagged. Malicious: 10. Suspicious: 1. Analysis time (as stored): 2026-10-26 12:57 UTC. Retrieved (as stored): 2026-10-26 16:33 UTC. Google Safe Browsing flags it.
Page title: “Home”
More about the sources
Recorded security signals
Stored VirusTotal result: 11/92 engines flagged. Malicious: 10. Suspicious: 1. Analysis time (as stored): 2026-10-26 12:57 UTC. Retrieved (as stored): 2026-10-26 16:33 UTC. Use caution — do not enter credentials or personal information.
Risk signals
VirusTotal detections: 11/92Google Safe Browsing: threat flag recorded
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded cccomcmaasttxxffintuy.weebly.com on 2026-10-26. Stored VirusTotal result: 11/92 engines flagged. Malicious: 10. Suspicious: 1. Analysis time (as stored): 2026-10-26 12:57 UTC. Retrieved (as stored): 2026-10-26 16:33 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Registrar: Square. Status: Last known active. Hosting: Weebly, Inc. Do not enter credentials or connect a wallet.
The captured screenshot dated 2026-10-26 shows a page headed Sign in with your Xfinity ID, containing an email address field, a password field and a red button labelled Let's go, with an Xfinity mobile bill savings promotion beside it and Comcast copyright text below. PhishDestroy classified it as an impersonation phishing page, first seen 2026-10-26.
How the scam works
The page replicates a familiar Xfinity account sign-in while pairing it with a mobile savings offer, so a visitor who typed credentials into the captured form would transmit them to whoever controlled the page. As a category risk, such lookalike sign-in forms enable credential phishing and attempted account takeover against the impersonated service.
Evidence
The screenshot shows the Xfinity-branded credential form and promotional banner described above. On 2026-10-26 urlscan returned a malicious engine verdict with ML score 97 and an overall score of 100, categorising it as phishing with brand label Xfinity. VirusTotal flagged the domain as malicious, with vendors including Kaspersky labelling it phishing, and Google Safe Browsing flagged SOCIAL_ENGINEERING on 2026-10-26. The domain was listed by OpenPhish and on PhishDestroy internal blocklists on 2026-10-26, while Spamhaus DBL showed no listing and OTX recorded 0 pulses; a 307 redirect funneled HTTP to HTTPS. Site inspection found Weebly globals with jQuery, Google reCAPTCHA, Snowplow analytics and Google advertising trackers, plus 4 distinct script SHA256 hashes recorded for pivoting, beginning 5a630b41e7c3.
Infrastructure
No registrar is recorded for this subdomain; hosting was Weebly, Inc. behind a Cloudflare WAF. Weaknesses first: CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP and CORP all absent; DNSSEC unsigned. TLS 1.3, AES-256-GCM-SHA384, forward secrecy, ALPN h2; CAA records present.
What to do
If you entered credentials on this page, change your password on the genuine Xfinity account, enable two-factor authentication, and review recent account activity for unfamiliar changes. Security teams should block cccomcmaasttxxffintuy.weebly.com and use the recorded script hashes for campaign pivoting, while visitors should avoid the page and report it.
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.
The captured page presents an Xfinity ID sign-in form, and PhishDestroy classifies cccomcmaasttxxffintuy.weebly.com as an impersonation phishing threat.
AI summary
Overview The captured screenshot dated 2026-10-26 shows a page headed Sign in with your Xfinity ID, containing an email address field, a password field and a red button labelled Let's go, with an Xfinity mobile bill savings promotion beside it and Comcast copyright text below. PhishDestroy classified it as an impersonation phishing page, first seen 2026-10-26. How the scam works The page replicates a familiar Xfinity account sign-in while pairing it with a mobile savings offer, so a visitor who typed credentials into the captured form would transmit them to whoever controlled the page. As a category risk, such lookalike sign-in forms enable credential phishing and attempted account takeover against the impersonated service. Evidence The screenshot shows the Xfinity-branded credential form and promotional banner described above. On 2026-10-26 urlscan returned a malicious engine verdict with ML score 97 and an overall score of 100, categorising it as phishing with brand label Xfinity. VirusTotal flagged the domain as malicious, with vendors including Kaspersky labelling it phishing, and Google Safe Browsing flagged SOCIAL_ENGINEERING on 2026-10-26. The domain was listed by OpenPhish and on PhishDestroy internal blocklists on 2026-10-26, while Spamhaus DBL showed no listing and OTX recorded 0 pulses; a 307 redirect funneled HTTP to HTTPS. Site inspection found Weebly globals with jQuery, Google reCAPTCHA, Snowplow analytics and Google advertising trackers, plus 4 distinct script SHA256 hashes recorded for pivoting, beginning 5a630b41e7c3. Infrastructure No registrar is recorded for this subdomain; hosting was Weebly, Inc. behind a Cloudflare WAF. Weaknesses first: CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP and CORP all absent; DNSSEC unsigned. TLS 1.3, AES-256-GCM-SHA384, forward secrecy, ALPN h2; CAA records present. What to do If you entered credentials on this page, change your password on the genuine Xfinity account, enable two-factor authentication, and review recent account activity for unfamiliar changes. Security teams should block cccomcmaasttxxffintuy.weebly.com and use the recorded script hashes for campaign pivoting, while visitors should avoid the page and report it. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17902-461f-7769-bdde-5487b4e59cef/ Stored capture screenshot: https://i.ibb.co/Psm5whR4/cf1fd601c850.png URLScan screenshot (2026-10-26T13:05:26Z): https://screenshots.phishdestroy.io/us/01a17850-9907-7118-b950-b11983265beb.png URLScan capture report: https://urlscan.io/result/01a17850-9907-7118-b950-b11983265beb/ URLScan screenshot (2026-10-26T16:19:27Z): https://screenshots.phishdestroy.io/us/01a17902-114a-75e2-acce-4afd35a39e6f.png URLScan capture report: https://urlscan.io/result/01a17902-114a-75e2-acce-4afd35a39e6f/ URLScan screenshot (2026-10-26T16:48:19Z): https://screenshots.phishdestroy.io/us/01a1791c-3435-7584-a47b-ae353fb52282.png URLScan capture report: https://urlscan.io/result/01a1791c-3435-7584-a47b-ae353fb52282/ VirusTotal report: https://www.virustotal.com/gui/domain/cccomcmaasttxxffintuy.weebly.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=cccomcmaasttxxffintuy.weebly.com Archived copy: https://web.archive.org/web/20261026161732/https://cccomcmaasttxxffintuy.weebly.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
Ogurl: https://cccomcmaasttxxffintuy.weebly.com/; Title: Home; Ogimage: https://cccomcmaasttxxffintuy.weebly.com/uploads/1/5/6/5/156501999/screenshot-2025-05-22-191322_orig.png; Ogtitle: My Site
No sri: https://cdn2.editmysite.com/js/lang/en/stl.js, https://cdn11.editmysite.com/js/site/main.js, https://cdn2.editmysite.com/js/site/theme-plugins.js, https://cdn11.editmysite.com/js/site/footerSignup.js, https://cdn2.editmysite.com/js/site/main-customer-accounts-site.js, https://cdn11.editmysite.com/js/jquery-1.8.3.min.js; Third party scripts: 6
PhishDestroy rates cccomcmaasttxxffintuy.weebly.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 11/92 engines flagged. Malicious: 10. Suspicious: 1. Analysis time (as stored): 2026-10-26 12:57 UTC. Retrieved (as stored): 2026-10-26 16:33 UTC. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is cccomcmaasttxxffintuy.weebly.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on cccomcmaasttxxffintuy.weebly.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used cccomcmaasttxxffintuy.weebly.com?
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
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
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
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Social preview cardcccomcmaasttxxffintuy.weebly.com: Phishing site — Flagged by Google Safe Browsing, 21/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).v a6668b30739d
Edge-IP reputation is not attributed to this domain.
Nameservers 1
ns-646.awsdns-16.net
Location describes the IP network.
TLS certificate
Issuer
YE2
Valid from
2026-10-06 19:46:48
Valid until
2027-01-04 19:46:47
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0ab63db1f470cfa51bc6372a78a47a8db5f315e8e14c970970e78d8f6ccd9281Certificate names · 2 SANs
*.weebly.com
weebly.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was reachable but behind an access challenge at the latest check.
Technical details
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedDNS: Resolved
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-11-21 11:34 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-21 11:34 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
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-10-29 01:56 UTC.
Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
5 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+7516 d 12 h
Added to PhishDestroy+3 h 23 min
Google Safe Browsing
Threat flag recorded
+12 d 18 h
Added to PhishDestroy
cccomcmaasttxxffintuy.weebly.com
same minute
URLScan
Page captured
+3 min
Wayback Machine
Page archived
+3 h 20 min
VirusTotal
11/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
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 cccomcmaasttxxffintuy.weebly.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)
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.