The getcares.icu page copies the ScreenConnect remote support interface to present an unverified login portal. If you visited this address or tried to log in, close the page immediately and check your real accounts.
Page title: “ScreenConnect Remote Support Software”
More about the sources
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. Malicious: 1. Suspicious: 3. Analysis time (as stored): 2026-11-16 06:31 UTC. Retrieved (as stored): 2026-11-21 16:36 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 getcares.icu on 2026-11-21. Stored VirusTotal result: 4/92 engines flagged. Malicious: 1. Suspicious: 3. Analysis time (as stored): 2026-11-16 06:31 UTC. Retrieved (as stored): 2026-11-21 16:36 UTC. Risk: critical (evidence score 80/100). Registrar: PDR. Status: Last known active. Hosting: Stellar Group SAS. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
URLScan capture · 2026-11-21 16:02 UTC · SHA-256 55310bf6…a4a67f6
PhishDestroy analysis, reviewed version
ScreenConnect support portal layout on getcares.icu
The page at getcares.icu presents itself as a ScreenConnect remote support and collaboration portal against a landscape backdrop. The top left corner displays the "ScreenConnect" brand name, and the upper right features a "Login" button. A central dialog box reads "Welcome" alongside the text "Welcome to our online remote support and collaboration portal. The following options allow you to connect to a session." Right beside this, another box displays "No Available Sessions" with text noting that no sessions are publicly listed and visitors should use an invitation code from email. This design mimics official remote access deployment interfaces to make visitors feel they have arrived at a legitimate support portal.
Independent detections and security telemetry
Security analysts monitor this deployment because urlscan classified the page as malicious, and VirusTotal showed 4 of 92 engines flagging it on 16 Nov 2026, with Forcepoint ThreatSeeker, CRDF and Fortinet among the flagging vendors; its PhishDestroy evidence score is 45/100 (high). Furthermore, 153 other reported domains use the same nameserver pair, which links this address to a broader network of suspicious registrations sharing infrastructure.
Where this support portal copy leads
Pages mimicking remote management tools usually attempt to harvest user credentials or trick visitors into downloading unauthorized remote access software. Entering login details on such an unverified portal exposes your organization or personal environment to unauthorized access by whoever controls the domain.
Recommended precautions
Always verify that you are reaching out through official IT channels rather than clicking unverified links sent via email or chat. If you attempted to log in through getcares.icu, assume your credentials may have been compromised and immediately update your passwords on legitimate platforms.
Source evidenceVirusTotal 4 / 925 sources
SourceResultRecorded · UTCOpen
VirusTotal
4 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 11 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.
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
getcares.icu — ScreenConnect remote support portal clone
AI description
getcares.icu presents a ScreenConnect support login portal and is flagged by urlscan and 4 VirusTotal engines. Avoid entering credentials.
AI summary
ScreenConnect support portal layout on getcares.icu The page at getcares.icu presents itself as a ScreenConnect remote support and collaboration portal against a landscape backdrop. The top left corner displays the "ScreenConnect" brand name, and the upper right features a "Login" button. A central dialog box reads "Welcome" alongside the text "Welcome to our online remote support and collaboration portal. The following options allow you to connect to a session." Right beside this, another box displays "No Available Sessions" with text noting that no sessions are publicly listed and visitors should use an invitation code from email. This design mimics official remote access deployment interfaces to make visitors feel they have arrived at a legitimate support portal. Independent detections and security telemetry Security analysts monitor this deployment because urlscan classified the page as malicious, and VirusTotal showed 4 of 92 engines flagging it on 16 Nov 2026, with Forcepoint ThreatSeeker, CRDF and Fortinet among the flagging vendors; its PhishDestroy evidence score is 45/100 (high). Furthermore, 153 other reported domains use the same nameserver pair, which links this address to a broader network of suspicious registrations sharing infrastructure. Where this support portal copy leads Pages mimicking remote management tools usually attempt to harvest user credentials or trick visitors into downloading unauthorized remote access software. Entering login details on such an unverified portal exposes your organization or personal environment to unauthorized access by whoever controls the domain. Recommended precautions Always verify that you are reaching out through official IT channels rather than clicking unverified links sent via email or chat. If you attempted to log in through getcares.icu, assume your credentials may have been compromised and immediately update your passwords on legitimate platforms.
IP Reputation94.154.32.1090/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing.0 reportschecked 2026-11-21
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
94.154.32.109
Network ASN
AS214961
AS name
STELLARGROUPSAS Stellar Group SAS, FR
Organization
Stellar Group SAS
Observed location
Marseille, FR
Server header
Microsoft-HTTPAPI/2.0
Nameservers 4
dns1.regway.com
dns2.regway.com
dns3.regway.com
dns4.regway.com
SOA
nsname: dns1.regway.com
hostmaster: canhanet.sendapp.uk
serial: 2026111102
refresh: 7200
retry: 7200
expire: 172800
minttl: 38400
Location describes the IP network.
TLS certificate
Issuer
YR1
Valid from
2026-11-11 01:04:05
Valid until
2027-02-09 01:04:04
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte1f7ab9346a8908e2eab8c57413b080a9e618bd00ff060603364d8f0cdd8241aCertificate names · 2 SANs
getcares.icu
www.getcares.icu
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.getcares.icuDomain record
Technologies · 1 identified
M
Microsoft HTTPAPI
Web servers
Microsoft HTTPAPI is a kernel-mode HTTP driver in the Windows operating system responsible for handling HTTP requests and responses with efficiency, scalability, and security.
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-21 16:05 UTC.
Loads saved data; the suspicious site is not opened.
Captured network requests
#
Network request
HTTP method · status
Type
Uncompressed size
Response body SHA-256
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Domain monitor · First collection record
Reachable
All retained availability observations3
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 12. 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+380 d 12 h
Added to PhishDestroy+5 d 9 h
First abuse report sent+2 min
Reported 385 d 22 h after registration
Wayback Machine
Page archived
+11 min
Abuse report sent
PD-0A8B1D1253D6E147D824 · Receipt 85506
abuse@publicdomainregistry.com
+2 min
Added to PhishDestroy
getcares.icu
same minute
URLScan
Page captured
+5 d 9 h
VirusTotal
4/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 matches6
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 getcares.icu)
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.