Skip to security report
getcares.icu favicon
Domain security and threat intelligence

getcares.icu

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

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.

VirusTotal detections: 4/92 Spamhaus DBL: DBL_BOTNET
Registrar
United StatesPDR
Resolved IP
France94.154.32.109Stellar Group SAS
Registered
2025-10-31
First seen by PhishDestroy
2026-11-21
Page captures
open gallery
Domain age
registered 2025-10-31 according to WHOIS
Reports sent
view timeline
2026-11-21 1 Report Sent

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

Critical
Status
Last known active
VirusTotal
4 / 92
Hosting
France94.154.32.109Stellar Group SAS
Registrar
United StatesPDR
Registered
2025-10-31
Page captures
6

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 / 92 5 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 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
4
Denominator
92
Vendors
alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet
Observed at
2026-11-16 06:31:28
Checked at
2026-11-21 17:36:50
Fetched at
2026-11-21 16:36:51

Spamhaus DBL

DBL_BOTNET

URLScan

Malicious

SHA-256 854ce485…d75754b

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

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

UUID
01a1fed8-6f89-7098-8613-bd94339953c2
Score
100
Malicious
✓
Result at
2026-11-22T04:30:21Z
Enriched at
2026-11-22T09:13:25Z
Source timestamps
Urlscan result at: 2026-11-22 05:30:21; Urlscan enriched at: 2026-11-22 10:13:25
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
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.
AI generated by
threat-v10-gemini
AI generated at
2026-11-21T16:37:25Z
Revision
9f64c5f4d509dfe7dc837441fac859b9fed4d4603d7f7a9a2a4a06d453a65e6f
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: 21 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Trackers

Requests
4

Forms and mixed content

Third-party scripts
0

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80

Carbon estimate

Bytes
32435
CO₂, grams
0.0012
Cleaner than, %
46

DNS servers

Nameservers
  • IP address
    162.251.82.121
    Host
    dns2.regway.com
  • IP address
    162.251.82.122
    Host
    dns1.regway.com
  • IP address
    162.251.82.246
    Host
    dns3.regway.com
  • IP address
    162.251.82.253
    Host
    dns4.regway.com
DNS zone
getcares.icu

Page quality

Layout shift (CLS)
0
SEO score
50
Speed Index, s
6.19
First Contentful Paint (FCP), s
6.19
Largest Contentful Paint (LCP), s
6.48
Total Blocking Time (TBT), ms
99
Performance score
61
Accessibility score
49
Best practices score
96

Location

IP address
94.154.32.109
ASN
214961
Organization
Stellar Group SAS
City
Marseille
Country
FR

TLS certificate

Subject alternative names
  • getcares.icu
  • www.getcares.icu
Key size, bits
3072
Certificate chain
  • getcares.icu
  • YR1
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR1
Serial
064D416AAB6E9FB5751D19C3C8489E0BCFEC
SHA-256
e1f7ab9346a8908e2eab8c57413b080a9e618bd00ff060603364d8f0cdd8241a
Subject
getcares.icu
Valid until
Valid from

DNS records

A
  • 94.154.32.109
NS
  • dns1.regway.com
  • dns3.regway.com
  • dns4.regway.com
  • dns2.regway.com
SOA
Primary nameserver
dns1.regway.com
Hostmaster
canhanet.sendapp.uk
Serial
2026111102
Refresh, seconds
7200
Retry, seconds
7200
Expiry, seconds
172800
Minimum TTL, seconds
38400

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
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
94.154.32.109
IP version
4

Redirects

Redirect chain
  • https://getcares.icu

Subdomains

Count
1
Subdomains
  • www.getcares.icu

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Registrar URL
https://publicdomainregistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • autoRenewPeriod https://icann.org/epp
Nameservers
  • dns3.regway.com
  • dns2.regway.com
  • dns4.regway.com
  • dns1.regway.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
Microsoft-HTTPAPI/2.0
Content-Type
text/html; charset=utf-8
X-Content-Type-Options
nosniff
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-21T16:17:56Z; First: 2026-11-21T16:17:56Z; Changes: 0; Days archived: 1; Avg page bytes: 8224
Trackers
Requests: 4
Forms and mixed content
Third party scripts: 0
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80
Carbon
Bytes: 32435; Co2 grams: 0.0012; Cleaner than: 46
DNS server
NS: (IP: 162.251.82.121; Host: dns2.regway.com), (IP: 162.251.82.122; Host: dns1.regway.com), (IP: 162.251.82.246; Host: dns3.regway.com), (IP: 162.251.82.253; Host: dns4.regway.com); Zone: getcares.icu
Quality
Cls: 0; Seo: 50; Si s: 6.19; Fcp s: 6.19; Lcp s: 6.48; Tbt ms: 99; Performance: 61; Accessibility: 49; Best practices: 96
Location
IP: 94.154.32.109; ASN: 214961; Org: Stellar Group SAS; City: Marseille; Country: FR
SSL
San: getcares.icu, www.getcares.icu; Bits: 3072; Chain: getcares.icu, YR1, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR1; Serial: 064D416AAB6E9FB5751D19C3C8489E0BCFEC; SHA256: e1f7ab9346a8908e2eab8c57413b080a9e618bd00ff060603364d8f0cdd8241a; Subject: getcares.icu; Valid to: 2027-02-09T01:04:04Z; Valid from: 2026-11-11T01:04:05Z
DNS records
A: 94.154.32.109; NS: dns1.regway.com, dns3.regway.com, dns4.regway.com, dns2.regway.com; Soa: Nsname: dns1.regway.com; Hostmaster: canhanet.sendapp.uk; Serial: 2026111102; Refresh: 7200; Retry: 7200; Expire: 172800; Minttl: 38400
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 94.154.32.109; Family: 4
Redirects
Chain: https://getcares.icu
Subdomains
Count: 1; Subdomains: www.getcares.icu
Registration record
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com; Registrar iana ID: 303; Registrar URL: https://publicdomainregistry.com; Created: 2025-10-31T17:52:46Z; Updated: 2026-11-01T00:22:33Z; Expires: 2027-10-31T23:59:59Z; Status: clientTransferProhibited https://icann.org/epp, autoRenewPeriod https://icann.org/epp; Nameservers: dns3.regway.com, dns2.regway.com, dns4.regway.com, dns1.regway.com; Dnssec: unsigned
HTTP headers
Headers: Server: Microsoft-HTTPAPI/2.0; Content type: text/html; charset=utf-8; X content type options: nosniff

Questions about getcares.icu

Is getcares.icu a legitimate ScreenConnect portal?

Always check your URL bar to ensure you are connecting through verified company infrastructure.

What happens if I entered my password on getcares.icu?

You should immediately change your password on legitimate accounts and review your access logs for unauthorized sessions.

Why is getcares.icu flagged by security vendors?

urlscan classified the page as malicious, and VirusTotal showed 4 of 92 engines flagging it on 16 Nov 2026.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (6)

All capture links and hashes (6)
Observed page title
ScreenConnect Remote Support Software
TLS Certificate
Issued by YR1 · stored validity ends in 78 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Connectwise report ↗
IP Reputation France94.154.32.109 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-11-21
RegistrationCreated 2025-10-31 — Expires 2027-10-31
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-21
DOM Analysisanalyzed 2026-11-21score 0/100
Submitted URLhttps://getcares.icu/
Favicon Hash
Case ID
SHORTDOT ZONE · PUBLIC EVIDENCE .icu

ShortDot zone evidence

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.

ShortDot SA · Luxembourg 7 zones · full-zone evidence updated daily Open the ShortDot evidence repository (GitLab)
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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
France94.154.32.109
Network ASN
AS214961
AS name
STELLARGROUPSAS Stellar Group SAS, FR
Organization
Stellar Group SAS
Observed location
FranceMarseille, 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 fingerprinte1f7ab9346a8908e2eab8c57413b080a9e618bd00ff060603364d8f0cdd8241a
Certificate 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.

Recorded subdomains1

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
Detected via Cloudflare Radar · Wappalyzer engine

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
CRDF
Fortinet
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 61

Google PageSpeed Insights — mobile performance audit of getcares.icu ·

61
Needs Work
Performance
FCP
6.19 s
First Contentful Paint
LCP
6.48 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
99 ms
Total Blocking Time
SI
6.19 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

All stored data119
Open complete records

Captured network requests

Network requests: 15 SHA-256 hashes: 14 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-21 16:05 UTC.

Open this scan on URLScan 01a1fed8-6f89-7098-8613-bd94339953c2 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. 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.

  1. Dns observation
    Observation source
    Dns observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    resolved
    DNS response code
    NOERROR
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-21 19:03:27.048700
    Evidence SHA-256
    306e3107e4558d54bd62d223bb322deb6219e1ffa197e3699254cccf2a170c6a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-21 19:03:27.048700
  2. Current state backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    resolved
    DNS response code
    NOERROR
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-21 17:03:37.000000
    Evidence SHA-256
    9c282f71d4a07a68f45191ad887b8c5d55e52ea777925a1d1e55d3c43518eaa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-21 17:03:37
  3. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-21 17:03:37.000000
    Evidence SHA-256
    9c282f71d4a07a68f45191ad887b8c5d55e52ea777925a1d1e55d3c43518eaa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-21 17:03:37

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 12. 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
    getcares.icu detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Connectwise · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: PDR Ltd. d/b/a PublicDomainRegistry.com. Abuse contacts: 1.
    • abuse@publicdomainregistry.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+380 d 12 h
  3. Added to PhishDestroy+5 d 9 h
  4. First abuse report sent+2 min

Reported 385 d 22 h after registration

  1. Wayback Machine

    Page archived

    +11 min
  2. Abuse report sent

    PD-0A8B1D1253D6E147D824 · Receipt 85506

    abuse@publicdomainregistry.com
    +2 min
  3. Added to PhishDestroy

    getcares.icu

    same minute
  4. URLScan

    Page captured

    +5 d 9 h
  5. 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
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

Check for cloaking

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

getcares.icu

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-0A8B1D1253D6E147D824 Recipient: abuse@publicdomainregistry.com
PDF notice generated Notice text archived (395 characters)
Abuse notice text as sent to the provider
Registrar policy. Per PDR Ltd. d/b/a PublicDomainRegistry.com's published terms: “Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice”
Applicable law. Domestic legal framework (India): IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud).
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 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)
  • 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/getcares.icu"
  title="PhishDestroy threat report for getcares.icu"
  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>