Skip to security report
Domain security and threat intelligence
apple-device.report favicon

apple-device.report

In short

apple-device.report is a credential phishing page detected by PhishDestroy on 2026-09-06.

“Login”

Registrar
Sav.com
Resolved IP
188.114.97.3
Registered
May 14, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 12/89 URLQuery threat systems: 1 alert Automated brand label: Apple
VirusTotal
engine detections
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Reports sent
view timeline
OTX: 4 refs Sep 6, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Domain summary

apple-device.report is a credential phishing page detected by PhishDestroy on 2026-09-06. Risk: critical (98/100). Registrar: Sav.com. Status: Content unavailable. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. PhishDestroy sent 1 abuse report. VirusTotal: 12/89 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
12 / 89
OTX
4 community refs
Page captures
6

PhishDestroy threat report

Overview

apple-device.report is a credential phishing page that impersonated Apple and targeted owners of Apple devices who could be persuaded that something about their device needed attention. PhishDestroy first detected it on 2026-09-06. The site has been offline since 2026-09-11, and on 2026-10-19 the domain still did not resolve in DNS. It is dead for now, but a registered domain can be pointed at a new server at any time.

How the scam works

The domain name suggests a device alert or status report, which is a common lure for sending people to a fake sign-in page. The page carried the plain title "Login" and presented itself as an Apple sign-in. Anything typed into it went to the operators, not to Apple. With a working Apple password, attackers can try to take over the account, reach iCloud data and backups, and use device-location and remote-wipe features. Victims who reuse the same password on other services face wider exposure.

Evidence

When VirusTotal checked the domain on 2026-09-08, 12 of 89 security engines flagged it. Those engines included BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, Gridinsoft, alphaMountain.ai and the Vietnamese anti-scam project Chong Lua Dao. Several of those vendors run their own independent detection, so the agreement carries weight even though most engines stayed silent. The domain also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2026-05-14 through Sav.com, LLC, almost four months before PhishDestroy caught it. That gap points to a name bought ahead of time and kept unused until a campaign needed it. The site was served through Cloudflare's network in the US, at 188.114.97.3. That address belongs to Cloudflare's shared proxy, so it hides the real origin server rather than identifying it.

What to do

If you entered your Apple account details on this site, change your Apple password immediately from Settings or Apple's official site. Then review the list of trusted devices and remove any you don't recognize. Turn on two-factor authentication if it is off, and change the password on any other service where you used the same one. Watch for unexpected sign-in notifications, purchases or changes to Find My, and treat later "Apple" messages asking you to confirm codes as suspicious. Defenders should block the domain at DNS and proxy level, watch for it resolving again, and search mail and web logs for users who reached it between 2026-09-06 and 2026-09-11.

Source evidenceVirusTotal 12 / 89 · OTX 4 references 7 sources

VirusTotal

12 / 89 engine detections

Open report
VirusTotal · 2026-09-21T15:32:22Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "desenmascara.me": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
First seen
2026-05-14T19:29:26Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:280"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.2.128"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "deborah.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "deborah.ns.cloudflare.com"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=_gs5s4gFYVXzo9NAGqV6WjXFmrYtLjO3JBh-1IpVegw"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.152.205"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:98cd"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "patryk.ns.cloudflare.com"
    }
]
Dns at
2026-09-06T10:55:39Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.apple-device.report",
        "apple-device.report"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5f945d1c6189db006309c47d5a7b022ebda",
    "sha256": "4a526dbc689c72ce7480ba19fca26b165895af64e3e8de948de879aca72c4d52",
    "subject": "apple-device.report",
    "valid_to": "2026-10-17T14:28:28Z",
    "valid_from": "2026-07-19T14:28:29Z"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "client update prohibited",
        "redemption period"
    ],
    "events": {
        "expiration": "2027-05-14T18:33:14Z",
        "last changed": "2026-09-06T22:12:21Z",
        "registration": "2026-05-14T18:33:14Z",
        "last update of RDAP database": "2026-09-21T15:40:40Z"
    },
    "registrar": "Sav.com, LLC",
    "registrar_iana_id": "609"
}

URLQuery

1 threat-system alert

Open report

OTX

4 community references

Open report

Cloudflare Radar

provider verdict: clean

Not recorded
Open report
Cloudflare Radar · 2026-09-06T11:07:45Z

Observed: · Retrieved:

Uuid
dd404886-1115-469c-ba63-7b3ca7cbdfb7
Final url
https://apple-device.report/
Status
200
History
[
    {
        "url": "https://apple-device.report/",
        "status": 200
    }
]
DOM structure hash
b2f4c46981e587d2d9d2fe94c6a0b0aed9e4595e31ecea6092e03283f8db3e29
Document hash
fc204708e2263984b3bd87069d3eaca73839ac511e689359e3c90693b3c6cc32
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "apple-device.report",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "apple-device.report",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "apple-device.report",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    },
    {
        "name": "apple-device.report",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
Registration record
{
    "registrar": "Sav.com, LLC",
    "created": "2026-05-14T18:33:14Z",
    "updated": "2026-08-12T07:37:40Z",
    "expires": "2027-05-14T18:33:14Z",
    "nameservers": [
        "deborah.ns.cloudflare.com",
        "patryk.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report
URLScan · 2026-09-06T11:00:42Z

Observed: · Retrieved:

Uuid
01a07660-8c05-71c6-a1e7-2a0f0a9c7b69
Final url
https://apple-device.report/
Status
200
Ip
104.21.2.128
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "104.21.2.128"
]
Asns
[
    "13335"
]
Document hash
fc204708e2263984b3bd87069d3eaca73839ac511e689359e3c90693b3c6cc32
Globals
[
    "__cfBeacon"
]
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "*.apple-device.report",
        "apple-device.report"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "apple-device.report",
    "protocol": "QUIC",
    "valid_to": "2026-10-17T14:28:28Z",
    "valid_from": "2026-07-19T14:28:29Z"
}
Domain age days
114
Apex age days
114
Tls age days
48
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 91,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.1.33"
}

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
Network Security Intelligence
Threat Detection Systems 1 alert
Detection SystemIndicatorVerdictAlert
DNS4EU apple-device.reportmaliciousSinkholed
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:

Questions about apple-device.report

Is apple-device.report legit?

No. PhishDestroy classifies apple-device.report as a credential phishing page (risk: critical, 98/100); it was first detected on 2026-09-06. VirusTotal: 12/89 engines flag it. Treat the site as unsafe.

Is apple-device.report safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on apple-device.report. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used apple-device.report?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

All capture links and hashes (6)
Observed page title
Login
Automated brand references
Apple
TLS Certificate
Issued by YE1

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Sav.com (Unknown)
RegistrationCreated May 14, 2026 (163d) — Expires May 14, 2027
Time to First Unavailability 4 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 DetectedSep 6, 2026
DOM Analysisanalyzed Sep 6, 2026score 98/1001 brand signal
Submitted URLhttps://apple-device.report/
Favicon Hash
Case ID
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

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • deborah.ns.cloudflare.com
  • patryk.ns.cloudflare.com

Mail routing 1 MX record

  • mx.all-harmless.domainspriority 10

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-07-19 14:28:29
Valid until
2026-10-17 14:28:28
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint4a526dbc689c72ce7480ba19fca26b165895af64e3e8de948de879aca72c4d52
Certificate names · 2 SANs
  • *.apple-device.report
  • apple-device.report

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SOCRadar
Sophos
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of apple-device.report · checked Sep 6, 2026

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

Availability observations

Last reachable observation

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

Check for cloaking

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

apple-device.report
Saved result
Unreachable
Stored observation history14

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

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 9
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Reachable→Unavailable

  9. Availability monitor · First collection record

    Reachable

All retained availability observations36

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-25 03:19:34.000000
    Evidence SHA-256
    f7807fc53bd9757ccc4f4b61c98c8d5f5bad858e92863f0337c01bedc36a953e
  2. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-23 22:56:16.207510
    Evidence SHA-256
    ddef624cdce5282db1a2273985b80abd1ec51e870abcdd0fb132591c1b12f9f4
  3. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-23 03:23:34.000000
    Evidence SHA-256
    8303e7e2e95a380b256a2155f804776c24a9127a5a00e098f1a051a4ae4c175e
  4. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-22 22:55:15.888363
    Evidence SHA-256
    5d418eb51df9b8c6d74209546748b7668ac29b85ae9abdb2669a9f23e1c93ded
  5. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-21 16:53:36.928467
    Evidence SHA-256
    36ca6315e479e2f31971bf6d3b12cbcb489e1e5031060db2e4e3a77a1ec0d1bc
  6. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-21 03:14:09.000000
    Evidence SHA-256
    7097b02b54d63d83d25018a890a42ed56215839cd4cae62ee24da3e9e2393095
  7. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-20 10:21:37.183325
    Evidence SHA-256
    8655d910ad503411f6c3ac31ef6b690e07ccfd5345beff2ff6f27aa9c8d03cbd
  8. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-19 10:21:20.392196
    Evidence SHA-256
    7d8542a9f4fb036625d678a1e5c8ef28cb2ea6da6d773887db2c13cba1884ebd
  9. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-19 03:13:47.000000
    Evidence SHA-256
    1498e3ae7fa9c10fa2684bae31fffd8e118e82b9c62b3b9ea9b16d7fc63750c6
  10. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-18 10:21:15.144873
    Evidence SHA-256
    21008aa06e53c33a48b4f2d580bb5fa7bb89e69ad466a5eac0ecacc9b0d239aa
  11. unknown
    Cause
    stale_current_evidence
    Monitor confidence
    0
    Original source timestamp
    2026-10-17 03:12:42.000000
    Evidence SHA-256
    364de3b87438a842f3e85eedfe1148f67fde4c7c1de12bb8f78dc52de8fe45c8
  12. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-17 03:12:42.000000
    Evidence SHA-256
    a3902e81809ade075bb092a0364c6cdaf4770f65e2da03561a24c8a6c0f39494
  13. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-16 22:22:38.733165
    Evidence SHA-256
    325ec20907621c35f6ce46e547e42140404642149567e6e93fddc33a8bd374af
  14. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-15 22:22:19.692675
    Evidence SHA-256
    b57a186ff0227f88bef5c1c9196d29e5e1e46b108d002523d7103218bdbfa456
  15. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-15 03:12:54.000000
    Evidence SHA-256
    03ec6c2943f426c3b6fbdb280e2a94737084c4b8ab934a2bc3d033610b0c6c8c
  16. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-14 22:21:26.687207
    Evidence SHA-256
    7421cc6cc9ae2e2b542829ae29de0fec760f6f79917b5aecad74f6d6b76202c3
  17. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-13 22:21:07.146269
    Evidence SHA-256
    e11aa72fb636ff77b21b69403f36401f9e4b9ee1bb373b7733ef0c35501ecfe7
  18. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-13 03:15:42.000000
    Evidence SHA-256
    00ce3639095f58a07a7328e3a613ab5575289bfa38e1c7c044a6ab9f63e5a078
  19. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-12 22:20:57.953315
    Evidence SHA-256
    b51da1bffddd174f641115e0ee43debcbd98219ab5681a6bfa7c3c60f8e8a4dc
  20. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-11 22:20:50.151913
    Evidence SHA-256
    812c3e0613a5f83dcce46efc2ff89b2699babd528627f426f34ba02bb46ff502
  21. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-11 03:14:25.000000
    Evidence SHA-256
    ec06cc8234a7d312ca771934a39f6b61403791df74d0a9f63d9546770efee438
  22. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-10 22:20:48.858561
    Evidence SHA-256
    e889a69e638e4b99f08646ff552e08a5e00e8c10757070b22974368774e37dce
  23. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-09 22:20:42.401113
    Evidence SHA-256
    4ba0c4f5e4344e3b8f573b980beedd63ce44b8a9e40e19356498f928d28b0f89
  24. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-09 03:25:07.000000
    Evidence SHA-256
    425d52982ec71da06a5a9ddde7acccdfd41025afc6a7fa29a534489d844f32b4
  25. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-08 22:20:32.448533
    Evidence SHA-256
    8edb3f7a2fc304b8a5177c3ded626d4b057bb928567328c50d7173ba35619249
  26. unknown
    Cause
    origin_unreachable
    Mechanism
    http_5xx
    Monitor confidence
    20
    Original source timestamp
    2026-10-07 03:43:32.000000
    Evidence SHA-256
    d3602fd4d7dac76fa0c0fffc5af87efdb23c1648bd704603e2d2daef1aaec68b
  27. unknown
    Cause
    stale_current_evidence
    Monitor confidence
    0
    Original source timestamp
    2026-10-07 03:43:32.000000
    Evidence SHA-256
    35b324ee17ae48fcd558e9eba6d95e2450a144b8b4b3bb675f1e13c88e7222c5
  28. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-07 00:13:39.270476
    Evidence SHA-256
    784b7ecbfd4d1f5c1f16811db27561f9397cfd12df6afd2ebacc11549485492a
  29. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-06 00:13:39.266033
    Evidence SHA-256
    6c7931c23b94bd542e1a363178918666093733143cd28bece59cd4213edf8d91
  30. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-05 00:13:35.837561
    Evidence SHA-256
    77e7d9ba0185b6198093d9e0f352c4cbcd747488876781a08693a3c8bc5d549f
  31. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-03 18:16:30.317188
    Evidence SHA-256
    840b924a67ca79486e792b172d1b87f62f62ee384d32bc16ba39337f2f879ec1
  32. unknown
    Cause
    origin_unreachable
    Mechanism
    http_5xx
    Monitor confidence
    20
    Original source timestamp
    2026-10-03 03:36:14.000000
    Evidence SHA-256
    11147481d1243437310628e2b48199ec8e7e57de61f200923d981ded98f90cb7
  33. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-02 18:16:28.238873
    Evidence SHA-256
    5d3ae438f1bd62165937c39e51256e63486d0beeebca7f3425c78ec172cf9bba
  34. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-10-01 18:16:25.663717
    Evidence SHA-256
    67a7ebe23fe91bf233b75e7e64aa2bb873758e1184964d313eba6317c44a07c3
  35. unknown
    Cause
    origin_unreachable
    Mechanism
    http_5xx
    Monitor confidence
    20
    Original source timestamp
    2026-10-01 03:38:29.000000
    Evidence SHA-256
    2ced60649c076c3df5f8d14c877922493b1737b9e470d12ef3e478b958a30925
  36. dns_inactive
    Cause
    dns_nxdomain
    Monitor confidence
    80
    Original source timestamp
    2026-09-30 18:14:55.856480
    Evidence SHA-256
    8d401fea30db1fdd3ca5b1e77bd91eb7b500ba9ae52e090028f06cf68c951184

Recorded activity

5 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    12/89 engine detections

    View source
  3. Abuse report sent

    PD-20260906-8E9F81

    abuse-trusted.savcom@in.wixanswers.com
  4. Added to PhishDestroy

    apple-device.report

    View source
  5. URLScan

    Page captured

    View source

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260906-8E9F81 Recipient: abuse-trusted.savcom@in.wixanswers.com
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

7 evidence signal groups linked 1 stored notification records Content unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 apple-device.report)
  • 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

Official reporting routes

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/apple-device.report"
  title="PhishDestroy threat report for apple-device.report"
  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>