Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
staking-zama.xyz favicon

staking-zama.xyz

In short

PhishDestroy stores a record for staking-zama.xyz. Source observations are dated separately; missing checks do not establish safety.

“Zama: The Confidential Blockchain Protocol”

Review the evidence
Registrar
United StatesEranet International
Resolved IP
Canada172.67.187.2Cloudflare, Inc. · CDN
Registered
Sep 27, 2026
First observed
Sep 29, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Stored blocklist matches: 2
VirusTotal
4 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLQuery
62
detections
URLScan
Malicious
engine verdict · score 98
Cloudflare Radar
Phishing
Page captures
7
open gallery
Domain age
32 days
registered 2026-09-27 according to RDAP
Reports sent
1
view timeline
Sep 29, 2026 1 Report Sent CDN
X Telegram API

Questions about staking-zama.xyz

Is staking-zama.xyz legit?

PhishDestroy stores a record for staking-zama.xyz. Source observations are dated separately; missing checks do not establish safety.

Is staking-zama.xyz safe to connect a wallet?

This report does not record which wallet requests staking-zama.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 staking-zama.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

Source evidenceVirusTotal 4 / 92 8 sources

VirusTotal

4 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
2
Suspicious
2
Undetected
35

Vendor labels

CRDF
malicious
SOCRadar
suspicious
alphaMountain.ai
suspicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

ERANET INTERNATIONAL LIMITED

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::6815:13ab
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::ac43:bb02
  • TTL, seconds
    21600
    Type
    NS
    Value
    seamus.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    seamus.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.19.171
  • TTL, seconds
    21600
    Type
    NS
    Value
    wanda.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.187.2

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.staking-zama.xyz
  • staking-zama.xyz
Issuer
Let's Encrypt / YE2
Serial
57138b43ed95d0d8a1ab96af257d9505991
SHA-256
cf1a6840c6a9d491980272911282508a30efc669178b92abd24cd656df044f45
Subject
staking-zama.xyz
Valid until
Valid from

Registration record

Registrar
ERANET INTERNATIONAL LIMITED
Registrar IANA ID
1868
Registrar URL
http://www.eranet.com
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
  • serverTransferProhibited
Nameservers
  • seamus.ns.cloudflare.com
  • wanda.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 2,
    "suspicious": 2,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "suspicious",
    "alphaMountain.ai": "suspicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
ERANET INTERNATIONAL LIMITED
Created
2026-09-28T04:25:20Z
Expires
2027-09-27T23:59:59Z
Updated
2026-09-28T00:00:00Z
First seen
2026-09-27T22:35:31Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::6815:13ab"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:bb02"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "seamus.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "seamus.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.19.171"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "wanda.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.187.2"
    }
]
Dns at
2026-09-28T09:17:00Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.staking-zama.xyz",
        "staking-zama.xyz"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "57138b43ed95d0d8a1ab96af257d9505991",
    "sha256": "cf1a6840c6a9d491980272911282508a30efc669178b92abd24cd656df044f45",
    "subject": "staking-zama.xyz",
    "valid_to": "2026-12-26T19:58:43Z",
    "valid_from": "2026-09-27T19:58:44Z"
}
Registration record
{
    "registrar": "ERANET INTERNATIONAL LIMITED",
    "registrar_iana_id": "1868",
    "registrar_url": "http://www.eranet.com",
    "created": "2026-09-27T20:25:20Z",
    "updated": "2026-09-27T20:25:21Z",
    "expires": "2027-09-27T00:00:00Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "seamus.ns.cloudflare.com",
        "wanda.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 2 malicious + 2 suspicious / 92 · 2026-10-14 06:44:27 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-14T06:44:27Z
fetched_at
2026-10-21T16:44:01Z
stats
{"timeout":0,"harmless":53,"malicious":2,"suspicious":2,"undetected":35}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

32a9cdb6-6fdb-4f8c-bc89-af36b2937dcd

Final URL

https://staking-zama.xyz/

HTTP response

200

Navigation history

  • URL
    https://staking-zama.xyz/
    Status
    200

DOM structure hash

df7dac5dd211e7923d5bc3882ad456f56e89ecaa8a1680df29ea759a6488b66b

Document hash

00787777303c35f24cb8d86946522e96d858ff65e027c1958fbcb94a284e041b

Phishing classifier result

  • phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    staking-zama.xyz
    Type
    A
    Value
    172.67.187.2
  • Name
    staking-zama.xyz
    Type
    A
    Value
    104.21.19.171
  • Name
    staking-zama.xyz
    Type
    AAAA
    Value
    2606:4700:3033::6815:13ab
  • Name
    staking-zama.xyz
    Type
    AAAA
    Value
    2606:4700:3031::ac43:bb02

DNSSEC valid

No

IP address

172.67.187.2

Registration record

Registrar
Eranet International Limited
Registered
Updated
Expires
Nameservers
  • seamus.ns.cloudflare.com
  • wanda.ns.cloudflare.com
Original source fields · JSON
Uuid
32a9cdb6-6fdb-4f8c-bc89-af36b2937dcd
Final url
https://staking-zama.xyz/
Status
200
History
[
    {
        "url": "https://staking-zama.xyz/",
        "status": 200
    }
]
DOM structure hash
df7dac5dd211e7923d5bc3882ad456f56e89ecaa8a1680df29ea759a6488b66b
Document hash
00787777303c35f24cb8d86946522e96d858ff65e027c1958fbcb94a284e041b
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "staking-zama.xyz",
        "type": "A",
        "value": "172.67.187.2"
    },
    {
        "name": "staking-zama.xyz",
        "type": "A",
        "value": "104.21.19.171"
    },
    {
        "name": "staking-zama.xyz",
        "type": "AAAA",
        "value": "2606:4700:3033::6815:13ab"
    },
    {
        "name": "staking-zama.xyz",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:bb02"
    }
]
Dnssec valid
false
Ip
172.67.187.2
Registration record
{
    "registrar": "Eranet International Limited",
    "created": "2026-09-27T20:25:20Z",
    "updated": "2026-09-27T20:25:21Z",
    "expires": "2027-09-27T23:59:59Z",
    "nameservers": [
        "seamus.ns.cloudflare.com",
        "wanda.ns.cloudflare.com"
    ]
}
Separate stored summary: suspicious · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
suspicious
categories
["Security Risks"]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious · engine verdict · score 98

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a0eb23-5454-72fd-873d-c4f8271788c0

Final URL

https://staking-zama.xyz/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://staking-zama.xyz/
    From
    http://staking-zama.xyz/
    Status
    307

IP address

2606:4700:3031::ac43:bb02

Contacted domains

  • gateway.irys.xyz
  • esm.sh
  • arbitrum.meowrpc.com
  • arbitrum.gateway.tenderly.co
  • arbitrum.drpc.org
  • rpc.ankr.com
  • arbitrum-one.publicnode.com
  • arb1.arbitrum.io
  • fonts.gstatic.com
  • 5jrjgp2nl37gpefz75hgo6idl2q2frezh2ewvezllzssodeldc3a.mainnet-1.datasprite-cdn.com
  • hxjnnbfgmzureusmhjgltavcqubaut2yzqx23rrlalgrwm4nynga.mainnet-1.datasprite-cdn.com
  • 7hle7g76hwhzkcgcytuleelhk7lwp5k2ivnywsyp5umgak26bktq.mainnet-1.datasprite-cdn.com
  • abnsx7str6j5sa3pdbm5r66xojf3es2dyofcb7tsun2spudnhioq.mainnet-1.datasprite-cdn.com
  • l2kourp7xt2ar7nw3fpgqmxu3mvfli4qxvsvx3cacditkaifq6rq.mainnet-1.datasprite-cdn.com
  • crwj4ebgvb7k4zcwmmxrnzxbs2gaegjyku7rc4eqjkvdnsvrehsa.mainnet-1.datasprite-cdn.com
  • y2me6bz5xzrin5vis76bc53hqcyzeg6ccrbutd74zgrtsncobg6q.mainnet-1.datasprite-cdn.com
  • rahqtny5jec73ifzc2gg5x3d5s6bznpxhj4g3ky25pp5g2l7y7pq.mainnet-1.datasprite-cdn.com
  • 4xy5hycubobxyykm63sfnbkjznatsbung7ttetuoehkqf7ozquma.mainnet-1.datasprite-cdn.com
  • qofpup6nmdjajko4dxgkt5mq2htvoe4uqxfbycxyrybfw7p5to7a.mainnet-1.datasprite-cdn.com
  • 7ohnisscwweqylohacphls5cmyhfuuworva4o7nypw42xdl6i63a.mainnet-1.datasprite-cdn.com
  • b6ktecz7yjy6fzgzlivivwfm4xtjvavuqbddceaslq46lxbuw2wq.mainnet-1.datasprite-cdn.com
  • muyovc3b2336fg4hlwg73n6w7lve6xi5wwagbq3mkm34hz3fufcq.mainnet-1.datasprite-cdn.com
  • 3zda2p33cro63eoev6gcult7nzm6vegrll7kg6cknocqfq4tavva.mainnet-1.datasprite-cdn.com
  • el2hrgbroeyi4qgvgvj2lqoggwyiygesvezu3i5thvntgjewgylq.mainnet-1.datasprite-cdn.com
  • tuahnjjbd4ptq2z3dq73mmxdcdpdxt5sjs4uwfluwoxw2i3zrv4q.mainnet-1.datasprite-cdn.com
  • h5mmvwl7o3g5kseh6ibvzgyebxak4j4qgqqczbevmgdtkhvbbhaq.mainnet-1.datasprite-cdn.com
  • fd7xqs6fnkfawh6qvkmjuuwvub4cbuycyxx3q3romqtbcbt6o4kq.mainnet-1.datasprite-cdn.com
  • qyxbba7uefsmigd4oki3zm3hcmilt5fjudhha7n37oeygwrgdcua.mainnet-1.datasprite-cdn.com
  • lipjimvtizvuyifeddgmjfapysx6npsrkjjwfy5zxmvkhkoal6ea.mainnet-1.datasprite-cdn.com
  • ch75ckxualkloc7t5fsfem56e5odt55sl7lel66ksibigpvzxsda.mainnet-1.datasprite-cdn.com

Contacted IP addresses

  • 2a00:1450:4001:c17::5e
  • 2606:4700:3037::ac43:a31a
  • 2606:4700:3035::6815:f9e
  • 2606:4700:10::6814:1faa
  • 2a00:1450:4001:c13::5f
  • 104.26.12.205
  • 2606:4700:20::ac43:46de
  • 2a04:4e42::485
  • 2606:4700:3037::6815:11cb
  • 104.26.11.181
  • 35.227.193.242
  • 2606:4700::6812:a3b
  • 2605:6441:1:439::
  • 2606:4700:10::ac42:96a2
  • 2606:4700:10::ac42:ab2d

Autonomous systems (ASN)

  • 15169
  • 13335
  • 54113
  • 396982
  • 396356

Server countries

  • DE
  • US

Linked domains

  • www.zama.org
  • app.zama.org
  • dune.com
  • www.blog.blockscout.com
  • docs.zama.org
  • staking.zama.org
  • bridge.zama.org
  • status.zama.org
  • github.com
  • x.com
  • t.me
  • www.linkedin.com
  • jobs.zama.org

Social media links

  • https://github.com/zama-ai
  • https://github.com/zama-ai/awesome-zama
  • https://x.com/zama
  • https://t.me/zama_on_telegram

Document hash

28be9c1877b32c3af4fe1c50db1fbb0e5f84b6ccb24bfb838f9beab3eb317634

Script hashes

  • 3b140ada1b7c80c5c61b809b0c131ac6e2613610f1f8e33934b6e3483d56f126

JavaScript globals

  • requestResize
  • __earlyClickAction
  • __removeEarlyClick
  • Cap
  • downloadLogsBlobInBrowser

Cookies

  • PHPSESSID

TLS session and certificate

Subject alternative names
  • *.staking-zama.xyz
  • staking-zama.xyz
Cipher
AES_128_GCM
Issuer
YE2
Subject
staking-zama.xyz
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

1

Certificate validity, days

89

Page requests

148

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html
Original source fields · JSON
Uuid
01a0eb23-5454-72fd-873d-c4f8271788c0
Final url
https://staking-zama.xyz/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://staking-zama.xyz/",
        "from": "http://staking-zama.xyz/",
        "status": 307
    }
]
Ip
2606:4700:3031::ac43:bb02
Contacted domains
[
    "gateway.irys.xyz",
    "esm.sh",
    "arbitrum.meowrpc.com",
    "arbitrum.gateway.tenderly.co",
    "arbitrum.drpc.org",
    "rpc.ankr.com",
    "arbitrum-one.publicnode.com",
    "arb1.arbitrum.io",
    "fonts.gstatic.com",
    "5jrjgp2nl37gpefz75hgo6idl2q2frezh2ewvezllzssodeldc3a.mainnet-1.datasprite-cdn.com",
    "hxjnnbfgmzureusmhjgltavcqubaut2yzqx23rrlalgrwm4nynga.mainnet-1.datasprite-cdn.com",
    "7hle7g76hwhzkcgcytuleelhk7lwp5k2ivnywsyp5umgak26bktq.mainnet-1.datasprite-cdn.com",
    "abnsx7str6j5sa3pdbm5r66xojf3es2dyofcb7tsun2spudnhioq.mainnet-1.datasprite-cdn.com",
    "l2kourp7xt2ar7nw3fpgqmxu3mvfli4qxvsvx3cacditkaifq6rq.mainnet-1.datasprite-cdn.com",
    "crwj4ebgvb7k4zcwmmxrnzxbs2gaegjyku7rc4eqjkvdnsvrehsa.mainnet-1.datasprite-cdn.com",
    "y2me6bz5xzrin5vis76bc53hqcyzeg6ccrbutd74zgrtsncobg6q.mainnet-1.datasprite-cdn.com",
    "rahqtny5jec73ifzc2gg5x3d5s6bznpxhj4g3ky25pp5g2l7y7pq.mainnet-1.datasprite-cdn.com",
    "4xy5hycubobxyykm63sfnbkjznatsbung7ttetuoehkqf7ozquma.mainnet-1.datasprite-cdn.com",
    "qofpup6nmdjajko4dxgkt5mq2htvoe4uqxfbycxyrybfw7p5to7a.mainnet-1.datasprite-cdn.com",
    "7ohnisscwweqylohacphls5cmyhfuuworva4o7nypw42xdl6i63a.mainnet-1.datasprite-cdn.com",
    "b6ktecz7yjy6fzgzlivivwfm4xtjvavuqbddceaslq46lxbuw2wq.mainnet-1.datasprite-cdn.com",
    "muyovc3b2336fg4hlwg73n6w7lve6xi5wwagbq3mkm34hz3fufcq.mainnet-1.datasprite-cdn.com",
    "3zda2p33cro63eoev6gcult7nzm6vegrll7kg6cknocqfq4tavva.mainnet-1.datasprite-cdn.com",
    "el2hrgbroeyi4qgvgvj2lqoggwyiygesvezu3i5thvntgjewgylq.mainnet-1.datasprite-cdn.com",
    "tuahnjjbd4ptq2z3dq73mmxdcdpdxt5sjs4uwfluwoxw2i3zrv4q.mainnet-1.datasprite-cdn.com",
    "h5mmvwl7o3g5kseh6ibvzgyebxak4j4qgqqczbevmgdtkhvbbhaq.mainnet-1.datasprite-cdn.com",
    "fd7xqs6fnkfawh6qvkmjuuwvub4cbuycyxx3q3romqtbcbt6o4kq.mainnet-1.datasprite-cdn.com",
    "qyxbba7uefsmigd4oki3zm3hcmilt5fjudhha7n37oeygwrgdcua.mainnet-1.datasprite-cdn.com",
    "lipjimvtizvuyifeddgmjfapysx6npsrkjjwfy5zxmvkhkoal6ea.mainnet-1.datasprite-cdn.com",
    "ch75ckxualkloc7t5fsfem56e5odt55sl7lel66ksibigpvzxsda.mainnet-1.datasprite-cdn.com"
]
Contacted IP addresses
[
    "2a00:1450:4001:c17::5e",
    "2606:4700:3037::ac43:a31a",
    "2606:4700:3035::6815:f9e",
    "2606:4700:10::6814:1faa",
    "2a00:1450:4001:c13::5f",
    "104.26.12.205",
    "2606:4700:20::ac43:46de",
    "2a04:4e42::485",
    "2606:4700:3037::6815:11cb",
    "104.26.11.181",
    "35.227.193.242",
    "2606:4700::6812:a3b",
    "2605:6441:1:439::",
    "2606:4700:10::ac42:96a2",
    "2606:4700:10::ac42:ab2d"
]
Asns
[
    "15169",
    "13335",
    "54113",
    "396982",
    "396356"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "www.zama.org",
    "app.zama.org",
    "dune.com",
    "www.blog.blockscout.com",
    "docs.zama.org",
    "staking.zama.org",
    "bridge.zama.org",
    "status.zama.org",
    "github.com",
    "x.com",
    "t.me",
    "www.linkedin.com",
    "jobs.zama.org"
]
Social
[
    "https://github.com/zama-ai",
    "https://github.com/zama-ai/awesome-zama",
    "https://x.com/zama",
    "https://t.me/zama_on_telegram"
]
Document hash
28be9c1877b32c3af4fe1c50db1fbb0e5f84b6ccb24bfb838f9beab3eb317634
Script hashes
[
    "3b140ada1b7c80c5c61b809b0c131ac6e2613610f1f8e33934b6e3483d56f126"
]
Globals
[
    "requestResize",
    "__earlyClickAction",
    "__removeEarlyClick",
    "Cap",
    "downloadLogsBlobInBrowser"
]
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "*.staking-zama.xyz",
        "staking-zama.xyz"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "staking-zama.xyz",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-26T19:58:43Z",
    "valid_from": "2026-09-27T19:58:44Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
148
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Separate monitor record · 2026-09-29 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a0e6c7-0f15-70c3-a809-5c19dd7156b8
score
0
malicious
false
result_at
2026-09-29T03:30:06Z
enriched_at
2026-09-29T08:12:06Z
source_timestamps
{"urlscan_result_at":"2026-09-29 05:30:06","urlscan_enriched_at":"2026-09-29 10:12:06"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

93 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-09-29T06:20:12Z

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
10
analyzed_at
2026-09-29T06:20:12Z
source_timestamp
2026-09-29 08:20:12
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/zama_on_telegramStored page reference

IoC extraction recorded 2026-09-29 04:00:08 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded
StateStored capture
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)
Observed page title
Zama: The Confidential Blockchain Protocol
Automated brand references
MetaMask
TLS Certificate
Issued by YE2 · stored validity ends in 57 days
staking-zama.xyz: Crypto scam — Blocked by MetaMask, flagged by SEAL, 2/91 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card staking-zama.xyz: Crypto scam — Blocked by MetaMask, flagged by SEAL, 2/91 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 26a1dda59614

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Context Canada172.67.187.2 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Eranet International US(US)
Abuse contact["info@todaynic.com", "861faf47766f9650s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for staking-zama.xyz →
RegistrationCreated Sep 27, 2026 (32d · New) — Expires Sep 27, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant1f8f4166599d23ee861faf47766f9650s@ VirusTotal WHOIS
Time to First Unavailability 19h
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 29, 2026
DOM Analysisanalyzed Sep 29, 2026score 93/1001 brand signal
IoC Extractionscanned Sep 29, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://staking-zama.xyz/
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.

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

Shared CDN edge
Resolved IP
Canada172.67.187.2
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • seamus.ns.cloudflare.com
  • wanda.ns.cloudflare.com

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-09-27 19:58:44
Valid until
2026-12-26 19:58:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintcf1a6840c6a9d491980272911282508a30efc669178b92abd24cd656df044f45
Certificate names · 2 SANs
  • *.staking-zama.xyz
  • staking-zama.xyz

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

viewdns.info · 172.67.187.2rapiddns.io
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
CRDF
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of staking-zama.xyz · checked Sep 29, 2026

51
Needs Work
Performance
FCP
4.13 s
First Contentful Paint
LCP
4.16 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1218 ms
Total Blocking Time
SI
4.7 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.

Captured network requests

Network requests: 148 SHA-256 hashes: 106 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-10-29 02:31 UTC.

Open this scan on URLScan 01a0eb23-5454-72fd-873d-c4f8271788c0 ↗

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 · Recorded state

    Reachable→Unavailable

All retained availability observations55

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_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 17:03:05.221734
    Evidence SHA-256
    2f984a79e84ab655d11fb271d10d9444f6b23d40b345ed653cfbb2faf803b616
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 17:03:05.221734
    Evidence reason
  2. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:32:27.000000
    Evidence SHA-256
    3659b2ebb662bab7afbddbe3ec3eeca2c19d8b60924fb6151f046571fed8765f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:32:27
    Evidence reason
    unavailable
  3. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:32:27.000000
    Evidence SHA-256
    3659b2ebb662bab7afbddbe3ec3eeca2c19d8b60924fb6151f046571fed8765f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:32:27
    Evidence reason
    unavailable
  4. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 09:55:10.533471
    Evidence SHA-256
    d7c171c3bc25387a314e97b9f8de814f4cae02ff9867fec22f1e7258a5a26a48
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 09:55:10.533471
    Evidence reason
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 09:55:08.586816
    Evidence SHA-256
    fa8e9b8de0fa2ff3f2c60817f493162c8480eb1a7ff0a28e0a7abc823995c62f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 09:55:08.586816
    Evidence reason
  6. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 03:46:59.000000
    Evidence SHA-256
    cc435ef69c9c1117118c36c98429c85e8f0dfc8be7865850238b7756bc944000
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 03:46:59
    Evidence reason
    unavailable
  7. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-27 03:46:59.000000
    Evidence SHA-256
    f53ef2e6cd7051eab9b4d6411aa87a891782faacce52e167ed5d66ab0a9609b9
    Evidence timestamp as recorded
    2026-10-27 03:46:59
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:55:08.299319
    Evidence SHA-256
    37b5c19af06da555fb6055130c267aaeda09ed615e57f17df294ffe2591f7ef9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 09:55:08.299319
    Evidence reason
  9. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:42:58.000000
    Evidence SHA-256
    6bc74934733ee515cfebef9f5a2b095fc961ccefcb18d550b03d1c5eb8143753
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:42:58
    Evidence reason
    unavailable
  11. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-25 03:42:58.000000
    Evidence SHA-256
    712d9d7f323c191cceebc93bfe692068ae1d688a1c2d939788dea6f8b4d1f9f2
    Evidence timestamp as recorded
    2026-10-25 03:42:58
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  12. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 22:56:16.207510
    Evidence SHA-256
    c5f098587335747ecb0284c1aaf394d9a7f57967b624ae64d7c6e3e96d6d5417
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 22:56:16.207510
    Evidence reason
  13. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-23 04:22:43.000000
    Evidence SHA-256
    5065ee1d2a6ec5511c5462d1be4260c8f67ca99a812768684f69c08320a969de
    Evidence timestamp as recorded
    2026-10-23 04:22:43
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  14. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:22:43.000000
    Evidence SHA-256
    e2da5e84f7ba788b5b47fc33ebb73379d26c6a8ff9c50225c4d59c5cf94cc462
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 04:22:43
    Evidence reason
    unavailable
  15. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 22:55:15.888363
    Evidence SHA-256
    3b646e5bc1bac379c47f59c89fb9159326ef6c40d3366eb6dfd5fa43e677c4aa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:55:15.888363
    Evidence reason
  16. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 16:53:36.928467
    Evidence SHA-256
    80d44683077929d57cc69d3d485aa4d0ee469673c8067e794714c21730456f32
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 16:53:36.928467
    Evidence reason
  17. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 04:18:22.000000
    Evidence SHA-256
    b20388a495f23734429764803b13855846e247fbb1029f9e82efe7bb874a9f7b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 04:18:22
    Evidence reason
    unavailable
  18. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-21 04:18:22.000000
    Evidence SHA-256
    b9b0037e2186f768f90d3a642d64ee13f9bc4a4ef2879f78cf08c99f59d2908f
    Evidence timestamp as recorded
    2026-10-21 04:18:22
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  19. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 10:21:37.183325
    Evidence SHA-256
    f6ebc34c637ae5924f85300e39eeddc978e4821086a9222c87005e67a3b0d797
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-20 10:21:37.183325
    Evidence reason
  20. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 10:21:20.392196
    Evidence SHA-256
    470b54ea6ccbe7f04a3825ada981b64179b616b50f8ee2944c5c5cf09876edf4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 10:21:20.392196
    Evidence reason
  21. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 04:12:25.000000
    Evidence SHA-256
    11b857f83cb5bf12faef49fbe31fbc471454d150e6d4f4ce979124b36a0b970c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 04:12:25
    Evidence reason
    unavailable
  22. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-19 04:12:25.000000
    Evidence SHA-256
    6bc6cf937bfd2d35b5e0d83eacf88cbca6c5b80cb6e6bf0713a22d4e9edbda82
    Evidence timestamp as recorded
    2026-10-19 04:12:25
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  23. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-18 10:21:15.144873
    Evidence SHA-256
    d137b34b07ce5d4f8c2c0144bb3a689c0914216b2acecc6045167a7531565b2d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-18 10:21:15.144873
    Evidence reason
  24. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-17 04:02:28.000000
    Evidence SHA-256
    37ea2fa1ceecec2db2ca0e185c580c85de8bcfd32978cff62fc935f6ebec16ca
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-17 04:02:28
    Evidence reason
    unavailable
  25. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-17 04:02:28.000000
    Evidence SHA-256
    e1ed10d579e88b682c34f65bac5d0779767060934e70b17889766d1d078d82c2
    Evidence timestamp as recorded
    2026-10-17 04:02:28
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  26. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-16 22:22:38.733165
    Evidence SHA-256
    715151e070bd7bc191e99245412b910620c301fbdb64cf388d91d23b9dbf29da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-16 22:22:38.733165
    Evidence reason
  27. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 22:22:19.692675
    Evidence SHA-256
    6c278207335eea35544133b166242cb2e0215578c9ef66df1220a947d8ab535c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 22:22:19.692675
    Evidence reason
  28. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-15 04:06:30.000000
    Evidence SHA-256
    a000ad80826f021be9a781659619e08214d359d763dbe1e203021a6be220bc56
    Evidence timestamp as recorded
    2026-10-15 04:06:30
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  29. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 04:06:30.000000
    Evidence SHA-256
    a343aba4e9ec0d23c12ee99974b9a8b6c23ab3687012af60d21fcddea64276e7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 04:06:30
    Evidence reason
    unavailable
  30. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-14 22:21:26.687207
    Evidence SHA-256
    84b3890be530ef4dfe4674dbe40cf3c017c8e665cc7af4be1060bb48d22e958e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-14 22:21:26.687207
    Evidence reason
  31. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 22:21:07.146269
    Evidence SHA-256
    d402eaa2a918551b0c13724c34dc7c6f5747360d1b3897bd73ccc2aa9d2e9da2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 22:21:07.146269
    Evidence reason
  32. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-13 03:34:53.000000
    Evidence SHA-256
    465d97bedf7415f738f0831721b0362df23d5295b46f7d27fd584659323ca3ae
    Evidence timestamp as recorded
    2026-10-13 03:34:53
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  33. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 03:34:53.000000
    Evidence SHA-256
    c80bc8854c43141692773c6e4687e61bc23ea08d81e78391f2ec9636176ddc71
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 03:34:53
    Evidence reason
    unavailable
  34. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-12 22:20:57.953315
    Evidence SHA-256
    b0927403a99131c7bcdd762cc5daf4b5da8ff49029520964407d00c9043f360e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-12 22:20:57.953315
    Evidence reason
  35. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 22:20:50.151913
    Evidence SHA-256
    06138ca909a4f3051eacea3d7a21df5e64801de0f27b809182dd0385032cd5b4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 22:20:50.151913
    Evidence reason
  36. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-11 03:33:54.000000
    Evidence SHA-256
    439a233dede7ac08267a858b4c70f23dbaebfa6536bb7fba4af499c454e9fc04
    Evidence timestamp as recorded
    2026-10-11 03:33:54
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  37. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 03:33:54.000000
    Evidence SHA-256
    d91ec9a5e3c627d2f12e3fe5fca0e79fbcd2a32740a1e57a53ada6e1a2cd4e28
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 03:33:54
    Evidence reason
    unavailable
  38. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-10 22:20:48.858561
    Evidence SHA-256
    11ef8921e63041943b1b74a04946731f8dff73b042235954f632140452c757a1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-10 22:20:48.858561
    Evidence reason
  39. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 22:20:42.401113
    Evidence SHA-256
    a36a067ca705bb74c2c35205661a07c0cfb9775d48d28db2e1eb50c1eb58d9d2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 22:20:42.401113
    Evidence reason
  40. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10-09 03:47:41.000000
    Evidence SHA-256
    757908c0651672d172d2d80262e23cf947b5a6379e6b3205809ee4ee341156db
    Evidence timestamp as recorded
    2026-10-09 03:47:41
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  41. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 03:47:41.000000
    Evidence SHA-256
    8050824a098a5e96a241f0b9743b57b52f6935f839e099d9c8cd521998750aef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 03:47:41
    Evidence reason
    unavailable
  42. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-08 22:20:32.448533
    Evidence SHA-256
    0da49a5add3e494d62c4dd99eadc9a6eb4fa06348e3d5f894716599a81c8b1a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-08 22:20:32.448533
    Evidence reason
  43. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 04:12:42.000000
    Evidence SHA-256
    1185786326bdca35269e746d20ce4943d5cd5d1bd566f6fe238c9b23342fdc58
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-07 04:12:42
    Evidence reason
    transient_502
  44. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    502
    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-10-07 04:12:42.000000
    Evidence SHA-256
    c533125620f0e8a9006a0dfe55ce9f7c88e7009fea527b837625a0b17eadaf5b
    Evidence timestamp as recorded
    2026-10-07 04:12:42
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  45. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 00:13:39.270476
    Evidence SHA-256
    0f399a21e98e0256f98d43c4d230f6dc7ee0a7a8efd7ef9c6c107be031afd218
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-07 00:13:39.270476
    Evidence reason
  46. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-06 00:13:39.266033
    Evidence SHA-256
    73a145cd4429727962b5329d34695921409b9b9666743d039a9cc9ba9e3526c7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-06 00:13:39.266033
    Evidence reason
  47. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-05 00:13:35.837561
    Evidence SHA-256
    74452d0282caf7aefe2eabc79f33c87072b1889a11d214b6860e6b3e5f762831
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-05 00:13:35.837561
    Evidence reason
  48. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 18:16:30.317188
    Evidence SHA-256
    70d02346b5dbc706195b1302376a295ce40556bf1954b2c513314c32a40a1aeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-03 18:16:30.317188
    Evidence reason
  49. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:56:02.000000
    Evidence SHA-256
    8f8a881cf1a7b6691e5a57ad154732ef2afbdc7f37288212b5449a5095bbcf5d
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-03 03:56:02
    Evidence reason
    transient_502
  50. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    502
    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-10-03 03:56:02.000000
    Evidence SHA-256
    abfb4fa31a1a8585840b75e865ad0adf96754d5c6c25c5296dab1ac780ac2b75
    Evidence timestamp as recorded
    2026-10-03 03:56:02
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  51. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-02 18:16:28.238873
    Evidence SHA-256
    83187e78159518c7977f539ffd2603b7d792d43342363046cf38db99dacb648d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-02 18:16:28.238873
    Evidence reason
  52. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 18:16:25.663717
    Evidence SHA-256
    028c1788389f548aae03eebc6ec364be02a41bf49d956382ace6ac5f6bd2196b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-01 18:16:25.663717
    Evidence reason
  53. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    502
    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-10-01 03:58:34.000000
    Evidence SHA-256
    03d895d7ad00b693fd9a86811d5ccf71b515d1fa005294ddf131f8725b654c5c
    Evidence timestamp as recorded
    2026-10-01 03:58:34
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  54. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:58:34.000000
    Evidence SHA-256
    2259ac07cd9827be65f3f331d43cd774942a31074b1bc78967862763d7b79755
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-01 03:58:34
    Evidence reason
    transient_502
  55. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-09-30 18:14:55.856480
    Evidence SHA-256
    846116c132129e5b112ba4a0acda2d143f17093abc1c08a35fa0f050bcd750ea
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-09-30 18:14:55.856480
    Evidence reason

Threat Response Pipeline

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

Recorded events: 14. 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
    staking-zama.xyz detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Automated brand label: MetaMask · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable 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: 98
  • 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: 4/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Automated brand label: MetaMask
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Content Observed Unavailable
    Monitoring recorded an unavailable response; the cause was not independently established.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Eranet International Limited. Abuse contacts: 3.
    • support@eranet.com
    • support@tnet.hk
    • info@todaynic.com
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability Recorded: 3 of 3
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 19

Recorded activity

5 entries
  1. VirusTotal

    4/92 engine detections

    View source
  2. Abuse report sent

    PD-20260929-3987B8 · Receipt 73013

    support@eranet.comsupport@tnet.hkinfo@todaynic.com
  3. URLScan

    Page captured

    View source
  4. Cloudflare Radar

    Phishing

    View source
  5. Added to PhishDestroy

    staking-zama.xyz

    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

Lookalike domains

79 stored lookalike domains

etamask.io omission Internal report A 185.66.140.182MX etamask.ioNS ns13.knownsrv.com meetamask.io repetition Internal report A 185.66.140.182MX meetamask.ioNS ns13.knownsrv.com megamask.io replacement Internal report A 66.96.162.138MX alt1.aspmx.l.google.comNS ns1.domain.com metam.ask.io subdomain Internal report A 15.197.162.184 metamaak.io replacement Internal report A 185.66.140.182MX metamaak.ioNS ns13.knownsrv.com metamadk.io replacement Internal report A 185.66.140.182MX metamadk.ioNS ns13.knownsrv.com metamaks.io transposition Internal report A 185.66.140.182MX metamaks.ioNS ns13.knownsrv.com metamassk.io insertion Internal report A 185.66.140.182MX metamassk.ioNS ns13.knownsrv.com metamsask.io insertion Internal report A 185.66.140.182MX metamsask.ioNS ns13.knownsrv.com metamssk.io replacement Internal report A 185.66.140.182MX metamssk.ioNS ns13.knownsrv.com metanask.io homoglyph Internal report A 185.66.140.182MX metanask.ioNS ns13.knownsrv.com metanmask.io homoglyph Internal report A 185.66.140.182MX metanmask.ioNS ns13.knownsrv.com
Show all (67)
metasmask.io insertion Internal report A 185.66.140.182MX metasmask.ioNS ns13.knownsrv.com metramask.io insertion Internal report A 185.66.140.182MX metramask.ioNS ns13.knownsrv.com mewtamask.io insertion Internal report A 185.66.140.182MX mewtamask.ioNS ns13.knownsrv.com mmetamask.io homoglyph Internal report A 185.66.140.182MX mmetamask.ioNS ns13.knownsrv.com mtamask.io omission Internal report A 185.66.140.182MX mtamask.ioNS ns13.knownsrv.com mwetamask.io insertion Internal report A 185.66.140.182MX mwetamask.ioNS ns13.knownsrv.com nmetamask.io homoglyph Internal report A 185.66.140.182MX nmetamask.ioNS ns13.knownsrv.com metamark.io bitsquatting Internal report A 13.248.213.45MX mx0.123-reg.co.ukNS ns45.domaincontrol.com metamaskj.io addition Internal report A 185.66.140.182MX metamaskj.ioNS ns13.knownsrv.com metammask.io homoglyph Internal report A 185.66.140.182MX metammask.ioNS ns13.knownsrv.com metamnask.io homoglyph Internal report A 185.66.140.182MX metamnask.ioNS ns13.knownsrv.com emtamask.io transposition A 185.66.140.182MX emtamask.ioNS ns13.knownsrv.com m-etamask.io hyphenation A 104.247.81.99NS ns1.parkingcrew.net meamask.io omission A 185.66.140.182MX meamask.ioNS ns13.knownsrv.com meatmask.io transposition A 185.66.140.182MX meatmask.ioNS ns13.knownsrv.com meramask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mertamask.io insertion A 185.66.140.182MX mertamask.ioNS ns13.knownsrv.com metaamask.io repetition A 185.66.140.182MX metaamask.ioNS ns13.knownsrv.com metaamsk.io transposition A 185.66.140.182MX metaamsk.ioNS ns13.knownsrv.com metaask.io omission A 185.66.140.182MX metaask.ioNS ns13.knownsrv.com metalmask.io insertion A 15.197.148.33NS ns37.domaincontrol.com metamaask.io insertion A 185.66.140.182MX metamaask.ioNS ns13.knownsrv.com metamadsk.io insertion A 185.66.140.182MX metamadsk.ioNS ns13.knownsrv.com metamaek.io replacement A 172.65.190.172NS expire1.gname-dns.com metamak.io omission A 185.66.140.182MX metamak.ioNS ns13.knownsrv.com metamas.io omission A 185.66.140.182MX metamas.ioNS ns13.knownsrv.com metamasak.io insertion A 185.66.140.182MX metamasak.ioNS ns13.knownsrv.com metamasdk.io insertion A 185.66.140.182MX metamasdk.ioNS ns13.knownsrv.com metamask-io.com various A 13.248.169.48NS ns1.afternic.com metamasl.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metamasm.io replacement A 91.195.240.94NS ns1cnb.name.com metamsak.io transposition A 185.66.140.182MX metamsak.ioNS ns13.knownsrv.com metamsk.io omission A 185.66.140.182MX metamsk.ioNS ns13.knownsrv.com metamusk.io vowel-swap A 59.149.253.82NS ns1cnb.name.com metamzsk.io replacement A 91.195.240.94NS ns1cnb.name.com metarnask.io homoglyph NS ns15.domaincontrol.com metmaask.io transposition A 185.66.140.182MX metmaask.ioNS ns13.knownsrv.com metmask.io omission A 207.246.78.75NS ns1.dnsowl.com metsamask.io insertion A 185.66.140.182MX metsamask.ioNS ns13.knownsrv.com metsmask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mettamask.io repetition A !ServFailNS !ServFail metwmask.io replacement A 44.230.85.241NS curitiba.ns.porkbun.com metyamask.io insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metzmask.io replacement A 91.195.240.94NS ns1cnb.name.com meyamask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com meytamask.io insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mitamask.io vowel-swap A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mnetamask.io homoglyph A 185.66.140.182MX mnetamask.ioNS ns13.knownsrv.com mretamask.io insertion A 185.66.140.182MX mretamask.ioNS ns13.knownsrv.com mrtamask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mstamask.io replacement A 44.230.85.241NS curitiba.ns.porkbun.com mteamask.io transposition A 185.66.140.182MX mteamask.ioNS ns13.knownsrv.com mwtamask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com rnetamask.io homoglyph A 34.42.100.71NS ns-cloud-a1.googledomains.com matamask.io bitsquatting A 216.245.197.45NS ns1.badgerdns.com mdtamask.io bitsquatting A 91.195.240.94NS ns1cnb.name.com metamasi.io bitsquatting A 91.195.240.94NS ns1cnb.name.com metamasj.io bitsquatting A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metamaska.io addition A 198.185.159.145MX alt1.aspmx.l.google.comNS ns-cloud-e1.googledomains.com metamaskk.io addition A 185.66.140.182MX metamaskk.ioNS ns13.knownsrv.com metamaskl.io addition A 185.66.140.182MX metamaskl.ioNS ns13.knownsrv.com metamaso.io bitsquatting A 44.230.85.241NS curitiba.ns.porkbun.com metamesk.io bitsquatting A 77.247.179.91NS ns1.badgerdns.com metamqsk.io bitsquatting A 91.195.240.94NS ns1cnb.name.com metemask.io bitsquatting A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com netamask.io homoglyph A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com xn--metamas-bhb.io homoglyph A 109.69.20.213NS aldo.ns.cloudflare.com

Check for cloaking

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

staking-zama.xyz

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery 62 det. SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260929-3987B8 Recipient: support@eranet.com, support@tnet.hk, info@todaynic.com
Page title stored with report: Zama: The Confidential Blockchain Protocol
PDF notice generated Notice text archived (653 characters)
Abuse notice text as sent to the provider 
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 (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
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.
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?

5 evidence signal groups linked 1 stored notification records Server error
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 staking-zama.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.

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/staking-zama.xyz"
  title="PhishDestroy threat report for staking-zama.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>