VirusTotal
17 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“iCloud”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
17 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
5 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4/12
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no match recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | sateliteapple.support |
malicious | Sinkholed |
| DNS4EU | sateliteapple.support |
malicious | Sinkholed |
| Hagezi Threat Feed | sateliteapple.support |
malicious | Sinkholed |
| OpenDNS | sateliteapple.support |
phishing | Phishing Block |
| Cloudflare DNS | sateliteapple.support |
malicious | Sinkholed |
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
The domain sateliteapple.support poses a significant security threat by attempting to steal Apple account credentials through phishing. This site mimics legitimate Apple services to deceive users into entering sensitive login information, which can lead to unauthorized access, identity theft, and financial loss. Its primary risk lies in impersonation aimed at Apple users, rendering the domain particularly dangerous for those who might assume legitimacy based on its name.
PhishDestroy's analysis reveals that sateliteapple.support was registered recently on February 17, 2026, through the registrar Gransy, s.r.o. It currently resolves to the IP address 188.114.97.3 and uses a Let's Encrypt SSL certificate, which may falsely reassure users due to the presence of HTTPS. The domain is actively flagged by 22 out of 95 VirusTotal security vendors, confirming widespread detection across multiple antivirus and anti-phishing engines. Additionally, it appears on two security blocklists and is blocked by notable services such as OpenPhish and PhishingArmy, underscoring its elevated risk status.
If you have visited sateliteapple.support and provided any personal or login information, it is critical to take immediate action. Change your Apple account password and enable two-factor authentication to prevent unauthorized access. Monitor your accounts for suspicious activity and consider notifying your financial institutions if you shared payment details. Avoid revisiting the domain and use trusted security tools to scan your devices for malware. Staying vigilant against such threats is essential to protect your personal data from compromise.
22 · datasets with records / 9 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Gransy, s.r.o. · 188.114.97.3 · DNS, TLS and retained responses
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.
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.
Edge-IP reputation is not attributed to this domain.
quentin.ns.cloudflare.comLocation describes the IP network.
5e41b42de1f77c4f81dbd78f00344c452811154e83cae6fd1f343c0ea23a941aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of sateliteapple.support · checked Mar 29, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
status_splitScanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sateliteapple.support', port=80): Max retries exceeded with url: / (Caused by NewConnectio
1 · outbound report records
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
dns_inactive
dns_nxdomain
Reachable→Unavailable
14 recorded events. 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
Retained community reports and observations
Reported by 1 community member, first seen Mar 29, 2026
Original reports, independent checks and evidence links
PD-20260329-33D14D Recipient: abuse@regtons.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Recovery steps, reporting contacts and complaint drafts
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
sateliteapple.support)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “iCloud”. Apparent target: Apple.
VirusTotal detections for sateliteapple.support: 17 (2026-08-27 03:14:28 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.