PhishDestroy first recorded login.steamcommunutty.com on 2026-10-26. Stored VirusTotal result: 6/92 engines flagged. Malicious: 4. Suspicious: 2. Analysis time (as stored): 2026-10-26 16:50 UTC. Retrieved (as stored): 2026-10-26 20:19 UTC.
More about the sources
Recorded security signals
Stored VirusTotal result: 6/92 engines flagged. Malicious: 4. Suspicious: 2. Analysis time (as stored): 2026-10-26 16:50 UTC. Retrieved (as stored): 2026-10-26 20:19 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 login.steamcommunutty.com on 2026-10-26. Stored VirusTotal result: 6/92 engines flagged. Malicious: 4. Suspicious: 2. Analysis time (as stored): 2026-10-26 16:50 UTC. Retrieved (as stored): 2026-10-26 20:19 UTC. Risk: critical (evidence score 90/100). Registrar: CNOBIN INFORMATION TEC…. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
The captured screenshot from 2026-10-26 shows a blank browser error screen reading This page isn't working, naming login.steamcommunutty.com, citing HTTP ERROR 500 and offering a Reload button. PhishDestroy listed the domain after automated assessment classified it as a credential phishing page, first seen by PhishDestroy on 2026-10-26. Independent scanners tied the captured content to the Steam brand.
How the scam works
Scanner records show the page served a user-profile route that acts as a lure into an imitation Steam sign-in flow, the standard setup for capturing account usernames and passwords. Anyone who submits credentials on such a copy transfers them to the operator behind the domain. In the captured frame the backend failed, so the sign-in form itself was not rendered.
Evidence
Beyond the 500 error screen, the capture shows the domain name and Reload control exactly as presented on 2026-10-26. URL scanning gave an ML score of 98 and an overall score of 100 in the phishing category with Steam named as the brand, and the traversal passed through a redirect funnel of 307, 301 then 307 responses. VirusTotal flagged the domain as malicious, with CRDF labelling it malicious and CyRadar and Gridinsoft labelling it phishing; Google Safe Browsing did not flag it, Spamhaus DBL was unlisted, OTX recorded 0 pulses, while OpenPhish and Phishunt blocklists listed it alongside PhishDestroy's internal blocklist. Site inspection recorded Prototype JavaScript globals such as Ajax and Form, one tracker request, and 2 distinct script SHA256 hashes, for example 7b31bc98d352, for campaign pivoting.
Infrastructure
Weaknesses first: DNSSEC unsigned; no email-authentication result and no HTTP security-header result recorded; TLS over QUIC with AES-128-GCM. Cloudflare name servers fronted the domain and the server header identified Cloudflare as the CDN and firewall, with no registrar data recorded.
What to do
If you submitted credentials on login.steamcommunutty.com, change your password on the genuine Steam service, enable two-factor authentication and watch for unexpected account activity. Security teams should block login.steamcommunutty.com at proxy, mail and DNS layers and hunt for the recorded script hashes.
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.
PhishDestroy assesses login.steamcommunutty.com as a credential phishing page impersonating Steam, captured on 2026-10-26.
AI summary
Overview The captured screenshot from 2026-10-26 shows a blank browser error screen reading This page isn't working, naming login.steamcommunutty.com, citing HTTP ERROR 500 and offering a Reload button. PhishDestroy listed the domain after automated assessment classified it as a credential phishing page, first seen by PhishDestroy on 2026-10-26. Independent scanners tied the captured content to the Steam brand. How the scam works Scanner records show the page served a user-profile route that acts as a lure into an imitation Steam sign-in flow, the standard setup for capturing account usernames and passwords. Anyone who submits credentials on such a copy transfers them to the operator behind the domain. In the captured frame the backend failed, so the sign-in form itself was not rendered. Evidence Beyond the 500 error screen, the capture shows the domain name and Reload control exactly as presented on 2026-10-26. URL scanning gave an ML score of 98 and an overall score of 100 in the phishing category with Steam named as the brand, and the traversal passed through a redirect funnel of 307, 301 then 307 responses. VirusTotal flagged the domain as malicious, with CRDF labelling it malicious and CyRadar and Gridinsoft labelling it phishing; Google Safe Browsing did not flag it, Spamhaus DBL was unlisted, OTX recorded 0 pulses, while OpenPhish and Phishunt blocklists listed it alongside PhishDestroy's internal blocklist. Site inspection recorded Prototype JavaScript globals such as Ajax and Form, one tracker request, and 2 distinct script SHA256 hashes, for example 7b31bc98d352, for campaign pivoting. Infrastructure Weaknesses first: DNSSEC unsigned; no email-authentication result and no HTTP security-header result recorded; TLS over QUIC with AES-128-GCM. Cloudflare name servers fronted the domain and the server header identified Cloudflare as the CDN and firewall, with no registrar data recorded. What to do If you submitted credentials on login.steamcommunutty.com, change your password on the genuine Steam service, enable two-factor authentication and watch for unexpected account activity. Security teams should block login.steamcommunutty.com at proxy, mail and DNS layers and hunt for the recorded script hashes. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17806-4f90-74ab-b33e-a7f5f89c5701/ Cloudflare Radar report: https://radar.cloudflare.com/scan/03abe0b2-1118-4863-a0c6-00c83f4724af URLQuery report: https://urlquery.net/report/41b9c1dc-4498-4702-816d-d9bbf822ffb9 Stored capture screenshot: https://i.ibb.co/0RSfqrP7/355ee1bff614.png Cloudflare Radar screenshot (2026-10-26T11:42:31Z): https://screenshots.phishdestroy.io/cf/03abe0b2-1118-4863-a0c6-00c83f4724af.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/41b9c1dc-4498-4702-816d-d9bbf822ffb9.png URLScan screenshot (2026-10-26T01:01:24Z): https://screenshots.phishdestroy.io/us/01a175b9-d5dd-716d-b439-9e5286f9bff6.png URLScan capture report: https://urlscan.io/result/01a175b9-d5dd-716d-b439-9e5286f9bff6/ URLScan screenshot (2026-10-26T04:31:43Z): https://screenshots.phishdestroy.io/us/01a1767a-0a7b-70a9-945a-a23fc6e233dc.png URLScan capture report: https://urlscan.io/result/01a1767a-0a7b-70a9-945a-a23fc6e233dc/ URLScan screenshot (2026-10-26T06:08:17Z): https://screenshots.phishdestroy.io/us/01a176d2-cca3-73ef-9a07-22aaead74a38.png URLScan capture report: https://urlscan.io/result/01a176d2-cca3-73ef-9a07-22aaead74a38/ URLScan screenshot (2026-10-26T11:15:39Z): https://screenshots.phishdestroy.io/us/01a177ec-346b-75b8-89d5-19bc1fc84472.png URLScan capture report: https://urlscan.io/result/01a177ec-346b-75b8-89d5-19bc1fc84472/ VirusTotal report: https://www.virustotal.com/gui/domain/login.steamcommunutty.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=login.steamcommunutty.com Archived copy: https://web.archive.org/web/20261026114101/https://login.steamcommunutty.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates login.steamcommunutty.com as critical risk (evidence score 90/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 6/92 engines flagged. Malicious: 4. Suspicious: 2. Analysis time (as stored): 2026-10-26 16:50 UTC. Retrieved (as stored): 2026-10-26 20:19 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is login.steamcommunutty.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on login.steamcommunutty.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used login.steamcommunutty.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.
Registration (base domain)steamcommunutty.com · Created 2026-08-28 (86d · New)—Expires 2027-08-28
Time to First Unavailability9 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 Detected2026-10-26
DOM Analysisanalyzed 2026-10-26score 78/1004 brand signals
Issued by Google Trust Services / WE1· stored validity ends in 62 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.15.242
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
bonnie.ns.cloudflare.com
leif.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-10-26 10:04:43
Valid until
2027-01-24 11:03:31
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint947e4ed6bb906a9d7fa82a2bb6c0e79479b9e498b2649fd57f5f3bccfd2e8045Certificate names · 2 SANs
steamcommunutty.com
*.steamcommunutty.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAIN
RDAP registration
Observed timelinelast reachable: 2026-11-04 09:20 UTClast content: 2026-10-29 03:32 UTCcurrent episode first observed: 2026-11-04 10:21 UTCobserved RIP window: 2026-11-04 09:20 UTC → 2026-11-04 10:21 UTC · 1.01hmidpoint estimate ≈ 2026-11-04 09:50 UTC · precision high · 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-10-29 01:56 UTC.
Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Time to First Unavailability
Hours from detection to the first unavailable observation: 214
Recorded activity
6 entries
Lifecycle
Domain registered
Added to PhishDestroy+59 d 0 h
First abuse report sent+12 min
VirusTotal analysis with detections+4 h 58 min
Reported 59 d 1 h after registration
OrderTLD
Replied to the report
+10 h 6 min
VirusTotal
6/92 engine detections
+4 h 58 min
Abuse report sent
PD-20261026-7E8E14 · Receipt 83417
abuse@ordertld.com
+6 min
URLScan
Page captured
+5 min
Wayback Machine
Page archived
same minute
Added to PhishDestroy
login.steamcommunutty.com
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
Same automated brand label: Steam8
Reports with the same collector label. A shared label does not establish impersonation or common ownership. View matching reports →
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 login.steamcommunutty.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.