Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 7/92 engines flagged. malicious: 7. suspicious: 0. Analysis time (as stored): 2026-11-08T07:24:40Z. Retrieved (as stored): 2026-11-08T14:24:02Z. Listed by external blocklists: Phishunt. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
icloud-jpz.xyz favicon

icloud-jpz.xyz

In short

On 2026-11-08, icloud-jpz.xyz displayed a Chinese-language sign-in page. The layout pairs a dark teal panel bearing an "OK" logo tile with the label "ok" against a white card headed "登入" (sign in). The card contains three input fields: an account field (帐号), a password field (密码), and a verification code field (请输入验证码) accompanied by a distorted-character CAPTCHA image and a link to refresh it if unreadable. A full-width teal button labeled "登入" sits below the fields.

Review the evidence
Registrar
SingaporeGname
Resolved IP
Japan154.213.181.7Zillion Network Inc.
First observed
Nov 8, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed URLScan
Risk signals
VirusTotal detections: 7/92 Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
7 / 92
engine detections ·
Google Safe Browsing
Flagged
Blocklist matches
1
Phishunt
URLScan
Malicious
engine verdict · score 99
Page captures
2
open gallery
Nov 8, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded icloud-jpz.xyz on 2026-11-08. Stored VirusTotal result: 7/92 engines flagged. malicious: 7. suspicious: 0. Analysis time (as stored): 2026-11-08T07:24:40Z. Retrieved (as stored): 2026-11-08T14:24:02Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: Gname. Status: Last known active. Hosting: Zillion Network Inc. Listed by external blocklists: Phishunt. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
7 / 92
Blocklist matches
1
Hosting
Japan154.213.181.7Zillion Network Inc.
Registrar
SingaporeGname
Page captures
2
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-08T13:17:47Z
SHA-256: 4ae3dc078244fb9f72824614370d7e13114214c77dc36171f4256c3efc29e68f

PhishDestroy analysis, reviewed version

On 2026-11-08, icloud-jpz.xyz displayed a Chinese-language sign-in page. The layout pairs a dark teal panel bearing an "OK" logo tile with the label "ok" against a white card headed "登入" (sign in). The card contains three input fields: an account field (帐号), a password field (密码), and a verification code field (请输入验证码) accompanied by a distorted-character CAPTCHA image and a link to refresh it if unreadable. A full-width teal button labeled "登入" sits below the fields.

The stored VirusTotal domain result reports 7 detections out of 92 engines. CRDF reported "malicious"; Lionic reported "phishing".

Source evidenceVirusTotal 7 / 92 · Google Safe Browsing: flagged 7 sources

VirusTotal

7 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
7
Suspicious
0
Undetected
38

Vendor labels

CRDF
malicious
Lionic
phishing
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
Google Safe Browsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • self-signed

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
elevated exposure

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    a.share-dns.com
  • TTL, seconds
    600
    Type
    SOA
    Responsible mailbox
    master.share-dns.com
    Value
    a.share-dns.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    b.share-dns.net
  • TTL, seconds
    600
    Type
    A
    Value
    154.213.181.7

DNS records observed

JARM fingerprint

29d29d00000000000042d42d000000dd5c266caaa8baaf93008418f7774284

Certificate

Subject alternative names
  • VM-NRZqp1Fd
Issuer
VM-NRZqp1Fd
Serial
4e26e9846df76cbddd
SHA-256
4aab3e9b47bfca11e1e702310d25b7e00b03eaea38abd0da91e1a3822561cdc1
Subject
VM-NRZqp1Fd
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 7,
    "suspicious": 0,
    "undetected": 38
}
Vendor labels
{
    "CRDF": "malicious",
    "Lionic": "phishing",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "self-signed"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "elevated exposure"
}
First seen
2026-11-08T00:46:52Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "a.share-dns.com"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "master.share-dns.com",
        "value": "a.share-dns.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "b.share-dns.net"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "154.213.181.7"
    }
]
Dns at
2026-11-08T07:26:17Z
Jarm
29d29d00000000000042d42d000000dd5c266caaa8baaf93008418f7774284
Certificate
{
    "san": [
        "VM-NRZqp1Fd"
    ],
    "issuer": "VM-NRZqp1Fd",
    "serial": "4e26e9846df76cbddd",
    "sha256": "4aab3e9b47bfca11e1e702310d25b7e00b03eaea38abd0da91e1a3822561cdc1",
    "subject": "VM-NRZqp1Fd",
    "valid_to": "2027-11-08T00:55:49Z",
    "valid_from": "2026-11-08T00:55:49Z"
}
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
scope
unknown
result_state
observed
numerator
7
denominator
92
malicious
null
suspicious
null
vendors
["CRDF","Emsisoft","Forcepoint ThreatSeeker","Fortinet","Google Safe Browsing","Lionic","Netcraft"]
observed_at
2026-11-08 07:24:40
checked_at
2026-11-08 15:24:02
fetched_at
2026-11-08 14:24:03
time_basis
as stored; legacy timezone not established

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious · engine verdict · score 99

SHA-256 ebcd5d5422f1ebaf83780b48c33c7ec8538885cde56127545068ef1a7ab7ce97

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1bb4e-ba57-74ff-9972-db42602c8b49

Final URL

https://icloud-jpz.xyz/

HTTP response

200

IP address

154.213.181.7

Contacted domains

  • cdnjs.cloudflare.com

Contacted IP addresses

  • 104.17.24.14
  • 154.213.181.7

Autonomous systems (ASN)

  • 13335
  • 54801

Server countries

  • JP

Document hash

ebcd5d5422f1ebaf83780b48c33c7ec8538885cde56127545068ef1a7ab7ce97

Script hashes

  • bead4b6e9cb5d20013017ead09800c7e4e95a862c12eaa9fbbf705ad7330323c
  • d3bdbd73445a8436cc00fe829bbe0849bc5fe73571de79fe5a708d4fdf49879a
  • 7dfcfd26ec4d50d6f87cf7249e8ea6dfa183d79d0234b0800ae87eec7af5b2c7

JavaScript globals

  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • __INTLIFY_PROD_DEVTOOLS__
  • __INTLIFY_JIT_COMPILATION__
  • __INTLIFY_DROP_MESSAGE_COMPILER__
  • __VUE_I18N_FULL_INSTALL__
  • __VUE_I18N_LEGACY_API__
  • __VUE__

Browser storage keys

  • mock-store-v6

TLS session and certificate

Subject alternative names
  • VM-NRZqp1Fd
Cipher
AES_256_GCM
Issuer
VM-NRZqp1Fd
Subject
VM-NRZqp1Fd
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

365

Page requests

11

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a1bb4e-ba57-74ff-9972-db42602c8b49
Final url
https://icloud-jpz.xyz/
Status
200
Ip
154.213.181.7
Contacted domains
[
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.24.14",
    "154.213.181.7"
]
Asns
[
    "13335",
    "54801"
]
Countries
[
    "JP"
]
Document hash
ebcd5d5422f1ebaf83780b48c33c7ec8538885cde56127545068ef1a7ab7ce97
Script hashes
[
    "bead4b6e9cb5d20013017ead09800c7e4e95a862c12eaa9fbbf705ad7330323c",
    "d3bdbd73445a8436cc00fe829bbe0849bc5fe73571de79fe5a708d4fdf49879a",
    "7dfcfd26ec4d50d6f87cf7249e8ea6dfa183d79d0234b0800ae87eec7af5b2c7"
]
Globals
[
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "__VUE__"
]
Storage keys
[
    "mock-store-v6"
]
Tls
{
    "san": [
        "VM-NRZqp1Fd"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "VM-NRZqp1Fd",
    "subject": "VM-NRZqp1Fd",
    "protocol": "TLS 1.3",
    "valid_to": "2027-11-08T00:55:49Z",
    "valid_from": "2026-11-08T00:55:49Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
365
Requests
11
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a1bb4e-ba57-74ff-9972-db42602c8b49
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

9e07ec34-e3e0-44b2-907c-3543913cb9a3

Final URL

https://icloud-jpz.xyz/

Navigation history

  • URL
    https://icloud-jpz.xyz/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    icloud-jpz.xyz
    Type
    A
    Value
    154.213.181.7

DNSSEC valid

No

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Expires
Nameservers
  • a6.share-dns.com
  • b6.share-dns.net
Original source fields · JSON
Uuid
9e07ec34-e3e0-44b2-907c-3543913cb9a3
Final url
https://icloud-jpz.xyz/
History
[
    {
        "url": "https://icloud-jpz.xyz/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "icloud-jpz.xyz",
        "type": "A",
        "value": "154.213.181.7"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2026-11-07T22:52:23Z",
    "expires": "2027-11-07T23:59:59Z",
    "nameservers": [
        "a6.share-dns.com",
        "b6.share-dns.net"
    ]
}

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-11-08T14:41:59Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-11-08T14:41:59Z
source_timestamp
2026-11-08 15:41:59
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
icloud-jpz.xyz: Recorded Chinese-language account sign-in form
ai_description
PhishDestroy records icloud-jpz.xyz showing a Chinese-language sign-in page with account, password and verification code fields.
ai_summary
On 2026-11-08, icloud-jpz.xyz displayed a Chinese-language sign-in page. The layout pairs a dark teal panel bearing an "OK" logo tile with the label "ok" against a white card headed "登入" (sign in). The card contains three input fields: an account field (帐号), a password field (密码), and a verification code field (请输入验证码) accompanied by a distorted-character CAPTCHA image and a link to refresh it if unreadable. A full-width teal button labeled "登入" sits below the fields. The stored VirusTotal domain result reports 7 detections out of 92 engines. CRDF reported "malicious"; Lionic reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-08 15:27:54
revision
9037f726cfe17829624d8590224f63b4970bf98d4e9c933b438baa30bf3dca4d
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: 14 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Trackers

Requests
10
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    3

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    162.159.27.88
    Host
    b.share-dns.net
  • IP address
    172.64.53.25
    Host
    a.share-dns.com
DNS zone
icloud-jpz.xyz

Location

IP address
154.213.181.7
ASN
54801
Organization
Zillion Network Inc.
City
Tokyo
Country
JP

TLS certificate

Issuer
VM-NRZqp1Fd
Subject
VM-NRZqp1Fd

DNS records

A
  • 154.213.181.7
NS
  • a.share-dns.com
  • b.share-dns.net
SOA
Primary nameserver
a.share-dns.com
Hostmaster
master.share-dns.com
Serial
1794091967
Refresh, seconds
3600
Retry, seconds
1200
Expiry, seconds
86400
Minimum TTL, seconds
600

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
154.213.181.7
IP version
4

Technology stack

Technologies
  • Vue.js
  • Cloudflare
  • Font Awesome
  • cdnjs

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Updated
Expires
Status
  • serverTransferProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • a6.share-dns.com
  • b6.share-dns.net
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-08T14:22:16Z",
    "first": "2026-11-08T14:22:16Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 842
}
Trackers
{
    "requests": 10,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.88",
            "host": "b.share-dns.net"
        },
        {
            "ip": "172.64.53.25",
            "host": "a.share-dns.com"
        }
    ],
    "zone": "icloud-jpz.xyz"
}
Location
{
    "ip": "154.213.181.7",
    "asn": "54801",
    "org": "Zillion Network Inc.",
    "city": "Tokyo",
    "country": "JP"
}
Ssl
{
    "issuer": "VM-NRZqp1Fd",
    "subject": "VM-NRZqp1Fd"
}
DNS records
{
    "A": [
        "154.213.181.7"
    ],
    "NS": [
        "a.share-dns.com",
        "b.share-dns.net"
    ],
    "SOA": "{\"nsname\": \"a.share-dns.com\", \"hostmaster\": \"master.share-dns.com\", \"serial\": 1794091967, \"refresh\": 3600, \"retry\": 1200, \"expire\": 86400, \"minttl\": 600}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "154.213.181.7",
    "family": 4
}
Tech stack
{
    "technologies": [
        "Vue.js",
        "Cloudflare",
        "Font Awesome",
        "cdnjs"
    ]
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2026-11-07T22:52:23Z",
    "updated": "2026-11-07T22:52:32Z",
    "expires": "2027-11-07T23:59:59Z",
    "status": [
        "serverTransferProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "a6.share-dns.com",
        "b6.share-dns.net"
    ]
}

Questions about icloud-jpz.xyz

Is icloud-jpz.xyz legit?

PhishDestroy rates icloud-jpz.xyz as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-08. Stored VirusTotal result: 7/92 engines flagged. malicious: 7. suspicious: 0. Analysis time (as stored): 2026-11-08T07:24:40Z. Retrieved (as stored): 2026-11-08T14:24:02Z. Google Safe Browsing flags it. Listed by external blocklists: Phishunt. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is icloud-jpz.xyz safe to connect a wallet?

This report does not record which wallet requests icloud-jpz.xyz makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used icloud-jpz.xyz?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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.

Explore

Blocklist matchesPhishDestroy · Phishunt · no match in the other 10 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Checked, no match

Last checked

Stored Capture · 2 captures

URLScan · 2026-11-08 1 / 2 Used in the analysis Source file SHA-256: 4ae3dc078244fb9f72824614370d7e13114214c77dc36171f4256c3efc29e68f SHA-256 of the prepared copy given to the model: 5974109e5ca7a9cc7c619a9673dbe96c32793f460b44643c4b6564ed8851050c
SourceURLScan · 2026-11-08
Recorded
StateStored capture
HTTP status200
Final URLhttps://icloud-jpz.xyz/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
TLS Certificate
Issued by VM-NRZqp1Fd · stored validity ends in 364 days

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Nov 8, 2026
IP Reputation Japan154.213.181.7 abuse score 0/100 0 reports checked Nov 8, 2026
Registrar Gname SG(SG)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for icloud-jpz.xyz →
RegistrationExpires Nov 7, 2027
WHOIS statusserverTransferProhibitedclientTransferProhibitedaddPeriod
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 8, 2026
DOM Analysisanalyzed Nov 8, 2026score 0/100
Submitted URLhttps://icloud-jpz.xyz/
Favicon Hash
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Japan154.213.181.7
Network ASN
AS54801
Organization
Zillion Network Inc.
Observed location
JapanTokyo, JP

Nameservers 2

  • a6.share-dns.com
  • b6.share-dns.net

SOA

  • nsname: a.share-dns.com
  • hostmaster: master.share-dns.com
  • serial: 1794091967
  • refresh: 3600
  • retry: 1200
  • expire: 86400
  • minttl: 600

Location describes the IP network.

TLS certificate

Issuer
VM-NRZqp1Fd
Valid from
2026-11-08 00:55:49
Valid until
2027-11-08 00:55:49
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint4aab3e9b47bfca11e1e702310d25b7e00b03eaea38abd0da91e1a3822561cdc1
Certificate names · 1 SAN
  • VM-NRZqp1Fd

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

viewdns.info · 154.213.181.7rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 92 security vendors flagged this domain
View on VT
Last analyzed
CRDF
Lionic
Emsisoft
Fortinet
Netcraft
Google Safe Browsing
Forcepoint ThreatSeeker

Captured network requests

Network requests: 11 SHA-256 hashes: 11 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-08 14:25 UTC.

Open this scan on URLScan 01a1bb4e-ba57-74ff-9972-db42602c8b49 ↗

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. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations1

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. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 15:26:52.903966
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 11. 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: 1 of 1
  • Threat Ingested
    icloud-jpz.xyz detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Automated brand label: Apple · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 7/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: Phishunt
  • Automated brand label: Apple
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    icloud-jpz.xyz

    View source
  3. URLScan

    Malicious · engine verdict · score 99

    View source
  4. VirusTotal

    7/92 engine detections

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

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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.

icloud-jpz.xyz

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 7 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Certificate hostname mismatch CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • 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

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 icloud-jpz.xyz)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/icloud-jpz.xyz"
  title="PhishDestroy threat report for icloud-jpz.xyz"
  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>