Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-11-06T05:49:48Z. Retrieved (as stored): 2026-11-06T18:22:23Z. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
governance.hyperecosystms.com favicon

governance.hyperecosystms.com

In short

On 2026-11-04, governance.hyperecosystms.com displayed a page branded with the Hyperliquid logo, headlined "Where should $HYPE Season 3 rewards lead?" The page describes a Season 3 community allocation of 38.8M HYPE and shows statistics of 48.2K users voted with a 15% quorum threshold. A sidebar titled "Cast your vote" presents a countdown timer and four reward direction options with percentages: Perps traders 34.0%, HLP & liquidity 27.0%, HyperEVM apps 22.0%, and Spot & HIP-3 markets 17.0%, each with a vote button.

“HYPE Season 3 Vote”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United Kingdom188.114.96.1CloudFLARENET-EU · CDN
Registered
Nov 3, 2026
First observed
Nov 6, 2026
PhishDestroy assessment High
66/100
Evidence score
Availability Last known active Latest stored reachability observation Observed URLScan
Risk signals
VirusTotal detections: 4/92 Stored blocklist matches: 2 Young domain: 2 days old
VirusTotal
4 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
engine verdict · score 31
Page captures
3
open gallery
Domain age
2 days
registered 2026-11-03 according to WHOIS
Nov 6, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded governance.hyperecosystms.com on 2026-11-06. Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-11-06T05:49:48Z. Retrieved (as stored): 2026-11-06T18:22:23Z. Listed by external blocklists: MetaMask, SEAL. Risk: high (66/100). Registrar: Dynadot. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

High
Status
Last known active
VirusTotal
4 / 92
Blocklist matches
2
Scam type (automated label)
Crypto Drainer
Hosting
United Kingdom188.114.96.1CloudFLARENET-EU · CDN
Registrar
United StatesDynadot
Registered
Nov 3, 2026
Page captures
3
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-04T15:53:32Z
SHA-256: 5605460f0caa4510b82571201321652cd48d94ce4cb8f6d12b790e00fdaf7a3f

PhishDestroy analysis, reviewed version

On 2026-11-04, governance.hyperecosystms.com displayed a page branded with the Hyperliquid logo, headlined "Where should $HYPE Season 3 rewards lead?" The page describes a Season 3 community allocation of 38.8M HYPE and shows statistics of 48.2K users voted with a 15% quorum threshold. A sidebar titled "Cast your vote" presents a countdown timer and four reward direction options with percentages: Perps traders 34.0%, HLP & liquidity 27.0%, HyperEVM apps 22.0%, and Spot & HIP-3 markets 17.0%, each with a vote button.

The stored VirusTotal domain result reports 4 detections out of 92 engines. SOCRadar reported "phishing"; Kaspersky reported "phishing".

Source evidenceVirusTotal 4 / 92 8 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
4
Suspicious
0
Undetected
34

Vendor labels

SOCRadar
phishing
Kaspersky
phishing
Gridinsoft
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::ac43:b0ec
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.51.66
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::6815:3342
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.176.236

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.hyperecosystms.com
  • hyperecosystms.com
Issuer
Let's Encrypt / YE1
Serial
6d7144c5cd83762237c1f88c86f06dc061e
SHA-256
f528f8bb3915dec64b80786bfc800ce221d7f11386342c3884e60ac9df6a1a2a
Subject
hyperecosystms.com
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • leo.ns.cloudflare.com
  • lovisa.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-11-03T22:31:19Z
Expires
2027-11-03T22:31:19Z
Updated
2026-11-03T22:35:28Z
First seen
2026-11-04T16:01:39Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:b0ec"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.51.66"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::6815:3342"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.176.236"
    }
]
Dns at
2026-11-06T05:50:03Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.hyperecosystms.com",
        "hyperecosystms.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6d7144c5cd83762237c1f88c86f06dc061e",
    "sha256": "f528f8bb3915dec64b80786bfc800ce221d7f11386342c3884e60ac9df6a1a2a",
    "subject": "hyperecosystms.com",
    "valid_to": "2027-02-01T21:40:15Z",
    "valid_from": "2026-11-03T21:40:16Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-11-03T22:31:19Z",
    "updated": "2026-11-03T22:35:28Z",
    "expires": "2027-11-03T22:31:19Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "leo.ns.cloudflare.com",
        "lovisa.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
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
4
denominator
92
malicious
null
suspicious
null
vendors
["Forcepoint ThreatSeeker","Gridinsoft","Kaspersky","SOCRadar"]
observed_at
2026-11-06 05:49:48
checked_at
2026-11-06 19:22:25
fetched_at
2026-11-06 18:22:26
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 31

SHA-256 d2f9cc2c8ea377ef3002af95dfa0db54c5cc7bd47402acfb51592b1e689f5fb8

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a1a743-da59-716c-868f-62febbce05d3

Final URL

https://governance.hyperecosystms.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://governance.hyperecosystms.com/
    From
    http://governance.hyperecosystms.com/
    Status
    307

IP address

2a06:98c1:3121::3

Contacted domains

  • svc-981946ae.cf-8noj7k34.workers.dev
  • fonts.reown.com
  • fonts.gstatic.com
  • base.meowrpc.com
  • 1rpc.io
  • base.drpc.org
  • rpc.ankr.com
  • base-rpc.publicnode.com
  • mainnet.base.org
  • api.web3modal.org
  • fonts.googleapis.com

Contacted IP addresses

  • 104.18.18.237
  • 188.114.96.3
  • 104.26.10.181
  • 188.114.97.3
  • 2606:4700:10::6814:2eb4
  • 2605:6441:1:439::
  • 2606:4700:10::6814:1875
  • 2a06:98c1:3109::ac40:9367
  • 142.251.14.94
  • 2a00:1450:4001:c15::5f
  • 2606:4700:10::ac42:9231
  • 2a06:98c1:3121::3

Autonomous systems (ASN)

  • 13335
  • 396356
  • 15169

Server countries

  • DE
  • US

Linked domains

  • app.hyperliquid.xyz
  • hyperliquid.gitbook.io
  • x.com
  • discord.gg

Social media links

  • https://x.com/HyperliquidX
  • https://discord.gg/hyperliquid

Document hash

d2f9cc2c8ea377ef3002af95dfa0db54c5cc7bd47402acfb51592b1e689f5fb8

Script hashes

  • 789b2d4a637d7e86c38789eb78d32c2bedcb9bea84576f3d40f04f24e04a3c7e
  • 551f94d095481f27281fdb03f80daa5f949c50f3cde270e61aed04f1def7eaf8

JavaScript globals

  • CONFIG
  • c71J_Mp
  • TrustProxy
  • SMtbOmb
  • PP
  • sMC0uYy
  • JXVAji
  • _isSlowGpu
  • MT
  • wgDxWk
  • w7QiMf
  • UI
  • WC
  • _walletConnectCore__count
  • downloadLogsBlobInBrowser
  • _walletConnectCore_
  • options
  • cast
  • selection

Browser storage keys

  • _le184af
  • vid
  • _wl_cache

TLS session and certificate

Subject alternative names
  • *.hyperecosystms.com
  • hyperecosystms.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
hyperecosystms.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

89

Page requests

45

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Content-security-policy
frame-ancestors http: https:
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a1a743-da59-716c-868f-62febbce05d3
Final url
https://governance.hyperecosystms.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://governance.hyperecosystms.com/",
        "from": "http://governance.hyperecosystms.com/",
        "status": 307
    }
]
Ip
2a06:98c1:3121::3
Contacted domains
[
    "svc-981946ae.cf-8noj7k34.workers.dev",
    "fonts.reown.com",
    "fonts.gstatic.com",
    "base.meowrpc.com",
    "1rpc.io",
    "base.drpc.org",
    "rpc.ankr.com",
    "base-rpc.publicnode.com",
    "mainnet.base.org",
    "api.web3modal.org",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "104.18.18.237",
    "188.114.96.3",
    "104.26.10.181",
    "188.114.97.3",
    "2606:4700:10::6814:2eb4",
    "2605:6441:1:439::",
    "2606:4700:10::6814:1875",
    "2a06:98c1:3109::ac40:9367",
    "142.251.14.94",
    "2a00:1450:4001:c15::5f",
    "2606:4700:10::ac42:9231",
    "2a06:98c1:3121::3"
]
Asns
[
    "13335",
    "396356",
    "15169"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "app.hyperliquid.xyz",
    "hyperliquid.gitbook.io",
    "x.com",
    "discord.gg"
]
Social
[
    "https://x.com/HyperliquidX",
    "https://discord.gg/hyperliquid"
]
Document hash
d2f9cc2c8ea377ef3002af95dfa0db54c5cc7bd47402acfb51592b1e689f5fb8
Script hashes
[
    "789b2d4a637d7e86c38789eb78d32c2bedcb9bea84576f3d40f04f24e04a3c7e",
    "551f94d095481f27281fdb03f80daa5f949c50f3cde270e61aed04f1def7eaf8"
]
Globals
[
    "CONFIG",
    "c71J_Mp",
    "TrustProxy",
    "SMtbOmb",
    "PP",
    "sMC0uYy",
    "JXVAji",
    "_isSlowGpu",
    "MT",
    "wgDxWk",
    "w7QiMf",
    "UI",
    "WC",
    "_walletConnectCore__count",
    "downloadLogsBlobInBrowser",
    "_walletConnectCore_",
    "options",
    "cast",
    "selection"
]
Storage keys
[
    "_le184af",
    "vid",
    "_wl_cache"
]
Tls
{
    "san": [
        "*.hyperecosystms.com",
        "hyperecosystms.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "hyperecosystms.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-02-01T21:40:15Z",
    "valid_from": "2026-11-03T21:40:16Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
45
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 31,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "content-security-policy": "frame-ancestors http: https:",
    "x-content-type-options": "nosniff"
}
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
01a1a743-da59-716c-868f-62febbce05d3
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: 11 fields

Observed: · Retrieved:

Report ID

6b793adc-a709-40b3-86a5-3e5d82ff0e8e

Final URL

https://governance.hyperecosystms.com/

HTTP response

200

Navigation history

  • URL
    https://governance.hyperecosystms.com/
    Status
    200

DOM structure hash

11e22f6c166f7ed4474b7396dd9d3c778ea12e1ca1556e1aacb196ceeddecb9e

Document hash

d2f9cc2c8ea377ef3002af95dfa0db54c5cc7bd47402acfb51592b1e689f5fb8

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    governance.hyperecosystms.com
    Type
    A
    Value
    188.114.97.0
  • Name
    governance.hyperecosystms.com
    Type
    A
    Value
    188.114.96.0
  • Name
    governance.hyperecosystms.com
    Type
    AAAA
    Value
    2a06:98c1:3120::
  • Name
    governance.hyperecosystms.com
    Type
    AAAA
    Value
    2a06:98c1:3121::

DNSSEC valid

No

IP address

127.0.1.12

127.0.1.12 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • leo.ns.cloudflare.com
  • lovisa.ns.cloudflare.com
Original source fields · JSON
Uuid
6b793adc-a709-40b3-86a5-3e5d82ff0e8e
Final url
https://governance.hyperecosystms.com/
Status
200
History
[
    {
        "url": "https://governance.hyperecosystms.com/",
        "status": 200
    }
]
DOM structure hash
11e22f6c166f7ed4474b7396dd9d3c778ea12e1ca1556e1aacb196ceeddecb9e
Document hash
d2f9cc2c8ea377ef3002af95dfa0db54c5cc7bd47402acfb51592b1e689f5fb8
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "governance.hyperecosystms.com",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "governance.hyperecosystms.com",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "governance.hyperecosystms.com",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "governance.hyperecosystms.com",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
127.0.1.12

127.0.1.12 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-11-03T22:31:19Z",
    "updated": "2026-11-03T22:35:28Z",
    "expires": "2027-11-03T22:31:19Z",
    "nameservers": [
        "leo.ns.cloudflare.com",
        "lovisa.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 100 · heuristic score · 2 brand references · 1 classification

Open report
Separate monitor score · 15 / 100 · 2026-11-06T19:02:54Z

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
15
analyzed_at
2026-11-06T19:02:54Z
source_timestamp
2026-11-06 20:02:54
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
governance.hyperecosystms.com: Hyperliquid Season 3 rewards governance vote page
ai_description
PhishDestroy records governance.hyperecosystms.com showing a Hyperliquid-branded Season 3 $HYPE rewards vote page with voting options and countdown timer.
ai_summary
On 2026-11-04, governance.hyperecosystms.com displayed a page branded with the Hyperliquid logo, headlined "Where should $HYPE Season 3 rewards lead?" The page describes a Season 3 community allocation of 38.8M HYPE and shows statistics of 48.2K users voted with a 15% quorum threshold. A sidebar titled "Cast your vote" presents a countdown timer and four reward direction options with percentages: Perps traders 34.0%, HLP & liquidity 27.0%, HyperEVM apps 22.0%, and Spot & HIP-3 markets 17.0%, each with a vote button. The stored VirusTotal domain result reports 4 detections out of 92 engines. SOCRadar reported "phishing"; Kaspersky reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-06 19:58:46
revision
5bb0225f423687ed15e6f848a36d933330389e50890ee082e41e39e502f621be
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: 22 fields

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Page title and metadata

Page title
HYPE Season 3 Vote

Trackers

Requests
15
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    4

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2030
TLS
36
Waiting
121
Connection
19
Download
90
Response time, ms
2296

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
133255
CO₂, grams
0.0049
Cleaner than, %
16

DNS servers

Nameservers
  • IP address
    108.162.194.39
    Host
    lovisa.ns.cloudflare.com
  • IP address
    172.64.35.241
    Host
    leo.ns.cloudflare.com
DNS zone
hyperecosystms.com

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
hyperecosystms.com

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
1; mode=block
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
frame-ancestors http: https:
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://governance.hyperecosystms.com

Page links

External link addresses
  • https://hyperliquid.gitbook.io/
  • https://app.hyperliquid.xyz/trade
  • https://x.com/HyperliquidX
  • https://discord.gg/hyperliquid
External links
4
Internal links
3

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • leo.ns.cloudflare.com
  • lovisa.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Content-security-policy
frame-ancestors http: https:
X-content-type-options
nosniff
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-06T18:32:38Z",
    "first": "2026-11-06T18:32:38Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 74784
}
Page title and metadata
{
    "title": "HYPE Season 3 Vote"
}
Trackers
{
    "requests": 15,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2030,
        "tls": 36,
        "wait": 121,
        "connect": 19,
        "download": 90
    },
    "response_ms": 2296
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 133255,
    "co2_grams": 0.0049,
    "cleaner_than": 16
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.194.39",
            "host": "lovisa.ns.cloudflare.com"
        },
        {
            "ip": "172.64.35.241",
            "host": "leo.ns.cloudflare.com"
        }
    ],
    "zone": "hyperecosystms.com"
}
Location
{
    "ip": "2a06:98c1:3121::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "hyperecosystms.com"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": "1; mode=block",
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "frame-ancestors http: https:",
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://governance.hyperecosystms.com"
    ]
}
Page links
{
    "external": [
        "https://hyperliquid.gitbook.io/",
        "https://app.hyperliquid.xyz/trade",
        "https://x.com/HyperliquidX",
        "https://discord.gg/hyperliquid"
    ],
    "external_count": 4,
    "internal_count": 3
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-11-03T22:31:19Z",
    "updated": "2026-11-03T22:35:28Z",
    "expires": "2027-11-03T22:31:19Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "leo.ns.cloudflare.com",
        "lovisa.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
        "content-security-policy": "frame-ancestors http: https:",
        "x-content-type-options": "nosniff"
    }
}

Questions about governance.hyperecosystms.com

Is governance.hyperecosystms.com legit?

PhishDestroy rates governance.hyperecosystms.com as high risk (66/100) from the recorded evidence; it was first recorded on 2026-11-06. Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-11-06T05:49:48Z. Retrieved (as stored): 2026-11-06T18:22:23Z. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is governance.hyperecosystms.com safe to connect a wallet?

This report does not record which wallet requests governance.hyperecosystms.com 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 governance.hyperecosystms.com?

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 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 · 3 captures

URLScan · 2026-11-04 1 / 3 Used in the analysis Source file SHA-256: 5605460f0caa4510b82571201321652cd48d94ce4cb8f6d12b790e00fdaf7a3f SHA-256 of the prepared copy given to the model: a73b7c2d8a220841ccbdc9655f50a478a556d6799b68a3047dbf9a220773e080
SourceURLScan · 2026-11-04
Recorded
StateStored capture
HTTP status200
Final URLhttps://governance.hyperecosystms.com/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)

Domain details

Domain
IP Context United Kingdom188.114.96.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for hyperecosystms.com →
Registration (base domain)hyperecosystms.com · Created Nov 3, 2026 (2d · Brand New!) — Expires Nov 3, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 6, 2026
DOM Analysisanalyzed Nov 6, 2026score 15/1002 brand signals
Submitted URLhttp://governance.hyperecosystms.com/
Favicon Hash
Observed page title
HYPE Season 3 Vote
Automated brand references
Across Discord
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.1
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • leo.ns.cloudflare.com
  • lovisa.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-11-03 21:40:16
Valid until
2027-02-01 21:40:15
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf528f8bb3915dec64b80786bfc800ce221d7f11386342c3884e60ac9df6a1a2a
Certificate names · 2 SANs
  • *.hyperecosystms.com
  • hyperecosystms.com

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

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

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
SOCRadar
Kaspersky
Gridinsoft
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of governance.hyperecosystms.com · checked Nov 6, 2026

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

Captured network requests

Network requests: 45 SHA-256 hashes: 39 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-06 18:23 UTC.

Open this scan on URLScan 01a1a743-da59-716c-868f-62febbce05d3 ↗

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-06 19:24:35.362698
    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: 10. 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
    governance.hyperecosystms.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 31
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • 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. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    governance.hyperecosystms.com

    View source
  3. VirusTotal

    4/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 31

    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.

governance.hyperecosystms.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 4 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid 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 governance.hyperecosystms.com)
  • 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/governance.hyperecosystms.com"
  title="PhishDestroy threat report for governance.hyperecosystms.com"
  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>