Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T15:32:55Z. Retrieved (as stored): 2026-10-31T23:16:25Z. 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
wormhole-foundation.us favicon

wormhole-foundation.us

In short

PhishDestroy first recorded wormhole-foundation.us on 2026-10-31. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T15:32:55Z. Retrieved (as stored): 2026-10-31T23:16:25Z. Listed by external blocklists: MetaMask, SEAL.

“wormhole-foundation.us”

Review the evidence
Registrar
Gandi SAS
Resolved IP
France217.70.184.38GANDI SAS
Registered
Oct 22, 2025
First observed
Oct 31, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 2/92 Stored blocklist matches: 2
VirusTotal
2 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
OTX
4
community references
URLScan
Malicious
engine verdict · score 33
Page captures
2
open gallery
Domain age
379 days
registered 2025-10-22 according to WHOIS · source data differ
OTX: 4 refs Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded wormhole-foundation.us on 2026-10-31. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T15:32:55Z. Retrieved (as stored): 2026-10-31T23:16:25Z. Listed by external blocklists: MetaMask, SEAL. Risk: critical (80/100). Registrar: Gandi SAS. Status: Last known active. Hosting: GANDI SAS. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
2 / 92
Blocklist matches
2
Hosting
France217.70.184.38GANDI SAS
Registrar
Gandi SAS
Registered
Oct 22, 2025
OTX
4 community refs
Page captures
2
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for wormhole-foundation.us. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 2 / 92 · OTX 4 references 7 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
1
Suspicious
1
Undetected
35

Vendor labels

Gridinsoft
suspicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    10800
    Type
    NS
    Value
    ns-1-a.gandi.net
  • TTL, seconds
    10800
    Type
    MX
    Value
    spool.mail.gandi.net
    Priority
    10
  • TTL, seconds
    10800
    Type
    MX
    Value
    fb.mail.gandi.net
    Priority
    50
  • TTL, seconds
    10800
    Type
    A
    Value
    217.70.184.38
  • TTL, seconds
    10800
    Type
    NS
    Value
    ns-246-c.gandi.net
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    hostmaster.gandi.net
    Value
    ns1.gandi.net
  • TTL, seconds
    10800
    Type
    TXT
    Value
    v=spf1 include:_mailcust.gandi.net ?all
  • TTL, seconds
    10800
    Type
    NS
    Value
    ns-79-b.gandi.net

DNS records observed

Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 1,
    "suspicious": 1,
    "undetected": 35
}
Vendor labels
{
    "Gridinsoft": "suspicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2025-10-22T00:00:00Z
Updated
2025-10-22T00:00:00Z
First seen
2025-10-25T16:05:00Z
DNS records
[
    {
        "ttl": 10800,
        "type": "NS",
        "value": "ns-1-a.gandi.net"
    },
    {
        "ttl": 10800,
        "type": "MX",
        "value": "spool.mail.gandi.net",
        "priority": 10
    },
    {
        "ttl": 10800,
        "type": "MX",
        "value": "fb.mail.gandi.net",
        "priority": 50
    },
    {
        "ttl": 10800,
        "type": "A",
        "value": "217.70.184.38"
    },
    {
        "ttl": 10800,
        "type": "NS",
        "value": "ns-246-c.gandi.net"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "hostmaster.gandi.net",
        "value": "ns1.gandi.net"
    },
    {
        "ttl": 10800,
        "type": "TXT",
        "value": "v=spf1 include:_mailcust.gandi.net ?all"
    },
    {
        "ttl": 10800,
        "type": "NS",
        "value": "ns-79-b.gandi.net"
    }
]
Dns at
2026-10-31T15:39:12Z
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
6
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","CRDF","Forcepoint ThreatSeeker","Gridinsoft","SOCRadar","VIPRE"]
observed_at
null
checked_at
2026-11-05 04:04:39
fetched_at
2026-11-05 03:04:39
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 33

SHA-256 a2ff2223ed33434ffd1b3e4b264b1c4794b29d3a1d83a1edd746e35ac009965c

Open report
URLScanOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Report ID

01a19420-c59b-715d-bde7-949718fe95c4

Final URL

http://wormhole-foundation.us/

HTTP response

200

Redirects

  • To
    https://wormhole-foundation.us/
    From
    http://wormhole-foundation.us/
    Status
    307
  • To
    http://wormhole-foundation.us/
    From
    https://wormhole-foundation.us/
    Status
    307

IP address

217.70.184.38

Reverse DNS (PTR)

webredir.vip.gandi.net

Contacted IP addresses

  • 217.70.184.38

Autonomous systems (ASN)

  • 29169

Server countries

  • FR

Linked domains

  • whois.gandi.net
  • www.gandi.net

Document hash

578fe256b4d23db6b631a02b3e12f8500dc41de3be52d9a9199f046b4a73b82c

Domain age, days

0

Differs from the registration date in WHOIS (2025-10-22), which gives 374 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

0

Differs from the registration date in WHOIS (2025-10-22), which gives 374 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Page requests

6

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html
Content-security-policy
default-src 'self'; script-src 'nonce-cfd7e09f00e94c4dbfffb86fd223d168';
Original source fields · JSON
Uuid
01a19420-c59b-715d-bde7-949718fe95c4
Final url
http://wormhole-foundation.us/
Status
200
Redirects
[
    {
        "to": "https://wormhole-foundation.us/",
        "from": "http://wormhole-foundation.us/",
        "status": 307
    },
    {
        "to": "http://wormhole-foundation.us/",
        "from": "https://wormhole-foundation.us/",
        "status": 307
    }
]
Ip
217.70.184.38
Ptr
webredir.vip.gandi.net
Contacted IP addresses
[
    "217.70.184.38"
]
Asns
[
    "29169"
]
Countries
[
    "FR"
]
Linked domains
[
    "whois.gandi.net",
    "www.gandi.net"
]
Document hash
578fe256b4d23db6b631a02b3e12f8500dc41de3be52d9a9199f046b4a73b82c
Domain age days
0

Differs from the registration date in WHOIS (2025-10-22), which gives 374 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
0

Differs from the registration date in WHOIS (2025-10-22), which gives 374 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 33,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "content-security-policy": "default-src 'self'; script-src 'nonce-cfd7e09f00e94c4dbfffb86fd223d168';"
}
Separate monitor record · 2026-11-01 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a19420-c59b-715d-bde7-949718fe95c4
score
0
malicious
false
result_at
2026-11-01T04:30:19Z
enriched_at
2026-11-02T09:14:31Z
source_timestamps
{"urlscan_result_at":"2026-11-01 05:30:19","urlscan_enriched_at":"2026-11-02 10:14:31"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

f589cb0e-b4a3-4ea8-b899-f7e19f12f6f4
Original source fields · JSON
Uuid
f589cb0e-b4a3-4ea8-b899-f7e19f12f6f4

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-31T23:20:14Z

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-10-31T23:20:14Z
source_timestamp
2026-11-01 00:20:14
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
Website checksOriginal source recordRetrieved: 10 fields

Mail configuration

MX records
  • fb.mail.gandi.net
  • spool.mail.gandi.net
SPF record
v=spf1 include:_mailcust.gandi.net ?all
SPF lookups
2

CAA records

Domain
wormhole-foundation.us

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Ports

Open ports
  • 80

DNS servers

Nameservers
  • IP address
    217.70.187.247
    Host
    ns-246-c.gandi.net
  • IP address
    213.167.230.80
    Host
    ns-79-b.gandi.net
  • IP address
    173.246.100.2
    Host
    ns-1-a.gandi.net
DNS zone
wormhole-foundation.us

Location

IP address
217.70.184.38
ASN
29169
Organization
GANDI SAS
City
Paris
Country
FR

DNS records

A
  • 217.70.184.38
MX
  • Mail server
    spool.mail.gandi.net
    Priority
    10
  • Mail server
    fb.mail.gandi.net
    Priority
    50
NS
  • ns-246-c.gandi.net
  • ns-1-a.gandi.net
  • ns-79-b.gandi.net
SOA
Primary nameserver
ns1.gandi.net
Hostmaster
hostmaster.gandi.net
Serial
1793232000
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
10800
TXT
  • v=spf1 include:_mailcust.gandi.net ?all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
217.70.184.38
IP version
4

Registration record

Registrar
Gandi SAS
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • renewPeriod https://icann.org/epp
Nameservers
  • ns-1-a.gandi.net
  • ns-79-b.gandi.net
  • ns-246-c.gandi.net
Original source fields · JSON
Mail configuration
{
    "mx": [
        "fb.mail.gandi.net",
        "spool.mail.gandi.net"
    ],
    "spf": "v=spf1 include:_mailcust.gandi.net ?all",
    "spf_lookups": 2
}
Caa records
{
    "domain": "wormhole-foundation.us"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Ports
{
    "open": [
        80
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "217.70.187.247",
            "host": "ns-246-c.gandi.net"
        },
        {
            "ip": "213.167.230.80",
            "host": "ns-79-b.gandi.net"
        },
        {
            "ip": "173.246.100.2",
            "host": "ns-1-a.gandi.net"
        }
    ],
    "zone": "wormhole-foundation.us"
}
Location
{
    "ip": "217.70.184.38",
    "asn": "29169",
    "org": "GANDI SAS",
    "city": "Paris",
    "country": "FR"
}
DNS records
{
    "A": [
        "217.70.184.38"
    ],
    "MX": [
        "{\"exchange\": \"spool.mail.gandi.net\", \"priority\": 10}",
        "{\"exchange\": \"fb.mail.gandi.net\", \"priority\": 50}"
    ],
    "NS": [
        "ns-246-c.gandi.net",
        "ns-1-a.gandi.net",
        "ns-79-b.gandi.net"
    ],
    "SOA": "{\"nsname\": \"ns1.gandi.net\", \"hostmaster\": \"hostmaster.gandi.net\", \"serial\": 1793232000, \"refresh\": 10800, \"retry\": 3600, \"expire\": 604800, \"minttl\": 10800}",
    "TXT": [
        "v=spf1 include:_mailcust.gandi.net ?all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "217.70.184.38",
    "family": 4
}
Registration record
{
    "registrar": "Gandi SAS",
    "created": "2025-10-22T06:25:03Z",
    "updated": "2026-10-28T07:20:03Z",
    "expires": "2028-10-22T06:25:03Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp",
        "renewPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "ns-1-a.gandi.net",
        "ns-79-b.gandi.net",
        "ns-246-c.gandi.net"
    ]
}

Questions about wormhole-foundation.us

Is wormhole-foundation.us legit?

PhishDestroy rates wormhole-foundation.us as critical risk (80/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T15:32:55Z. Retrieved (as stored): 2026-10-31T23:16:25Z. 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 wormhole-foundation.us safe to connect a wallet?

This report does not record which wallet requests wormhole-foundation.us 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 wormhole-foundation.us?

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

Stored capture 1 / 2
SourceStored capture
Recorded
StateStored capture
Position1 / 2
Open capture Wayback Download
All capture links and hashes (2)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 33 report ↗
IP Reputation France217.70.184.38 abuse score 0/100 3 reports PhishingWeb SpamEmail SpamPort Scan checked Nov 1, 2026 last reported
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Gandi SAS
Abuse contactabuse@gandi.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wormhole-foundation.us →
Hosting abuse contact abuse@gandi.net GANDI SAS · AS29169
RegistrationCreated Oct 22, 2025 — Expires Oct 22, 2028
Registrant countryCayman Islands VirusTotal WHOIS
Registrant7bee164ca4df02bc3eb290a118d964e2s@contact.gandi.net VirusTotal WHOIS
WHOIS statusclientTransferProhibitedrenewPeriod
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1002 brand signals
Submitted URLhttp://wormhole-foundation.us/
Favicon Hash
Observed page title
wormhole-foundation.us
Automated brand references
Foundation Wormhole

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
France217.70.184.38
Network ASN
AS29169
AS name
GANDI-AS GANDI SAS, FR
Organization
GANDI SAS
Observed location
FranceParis, FR
Server header
nginx

Nameservers 3

  • ns-1-a.gandi.net
  • ns-246-c.gandi.net
  • ns-79-b.gandi.net

SOA

  • nsname: ns1.gandi.net
  • hostmaster: hostmaster.gandi.net
  • serial: 1793232000
  • refresh: 10800
  • retry: 3600
  • expire: 604800
  • minttl: 10800

Mail routing 2 MX records

  • spool.mail.gandi.netpriority 10
  • fb.mail.gandi.netpriority 50

Location describes the IP network.

viewdns.info · 217.70.184.38rapiddns.io

Latest Classified Outcome 2026-11-05 02:31:01 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-05 02:31:01 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 02:31:01 UTC last content: 2026-11-05 02:31:01 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
Gridinsoft
Forcepoint ThreatSeeker
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://wormhole-foundation.us/
wormhole-foundation.us
This domain name has been registered with Gandi.net. It is currently parked by the owner.
Response
HTTP 200
HTML body
2.3 KB
Compressed
1.1 KB
Links
1 internal · 1 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Content-Security-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 2ca8a7d5bf257b1522cc51f7c192f63132bead19555afd3149bfb63d5203ac5a
Saved response-header values · 8
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'self'; script-src 'nonce-cb3e28900fe442aba95da7cfeb1c9464';
Content-Type
text/html
Date
Sat, 31 Oct 2026 22:45:13 GMT
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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: 6 SHA-256 hashes: 6 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-31 22:49 UTC.

Open this scan on URLScan 01a19420-c59b-715d-bde7-949718fe95c4 ↗

Stored observation history6

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 1
  1. Domain monitor · First collection record

    Reachable

All retained availability observations19

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:01.000000
    Evidence SHA-256
    a987a4cc40f75ba49a293e3571ba2ffffd76e7c4dd2c9d8a955ef239c7597b0e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:31:01
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:01.000000
    Evidence SHA-256
    a987a4cc40f75ba49a293e3571ba2ffffd76e7c4dd2c9d8a955ef239c7597b0e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:31:01
    Evidence reason
    alive_content
  3. 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-11-04 23:33:57.507178
    Evidence SHA-256
    88889b50c6a46b5bfe067798e8d5b1b458bdfd09ccac17ea178a280bc22e10e3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:33:57.507178
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:07:16.000000
    Evidence SHA-256
    c11a6a150cca41f9a386695473bb7af02495cb2d64678e20eef3417e772ac238
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:07:16
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:07:16.000000
    Evidence SHA-256
    c11a6a150cca41f9a386695473bb7af02495cb2d64678e20eef3417e772ac238
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:07:16
    Evidence reason
    alive_content
  6. 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-11-03 23:33:53.720874
    Evidence SHA-256
    aea6a11223bdc60e237ee10c278d2bc47d9eb0893481092d584258b8839d2728
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:33:53.720874
    Evidence reason
  7. 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-11-02 23:33:36.629046
    Evidence SHA-256
    0726bd26e43e4d7d238a159c0116f3a42369220f2c48c7f62f70e1fa3436c65f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:33:36.629046
    Evidence reason
  8. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    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-02 12:00:35.000000
    Evidence SHA-256
    8824bfcdb6b41431f4e74cd964592c6d14b895b0f2d8542c8746cc55e82bd3a1
    Evidence timestamp as recorded
    2026-11-02 12:00:35
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:00:35.000000
    Evidence SHA-256
    a54a5fc80da18b2cbcfea0666e9c28f65ea5b09cb10f38d3322d4252b53478f1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:00:35
    Evidence reason
    alive_content
  10. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:02:00.000000
    Evidence SHA-256
    be9e6a644e840a4175d6249f91f6bc862bf71716f5dc817797f44a88c387242b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:02:00
    Evidence reason
    alive_content
  11. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:02:00.000000
    Evidence SHA-256
    be9e6a644e840a4175d6249f91f6bc862bf71716f5dc817797f44a88c387242b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:02:00
    Evidence reason
    alive_content
  12. 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-11-01 23:32:58.613423
    Evidence SHA-256
    59b27e3292854a15689d14e242d8445dc6019e41fc8d1fd9ec24edac1f29a46f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:32:58.613423
    Evidence reason
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:02:18.000000
    Evidence SHA-256
    ef6afaaafd12aabff83ac9b28194f6670846518dfdf9ed1c6bc715cbdf542bb3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:02:18
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:02:18.000000
    Evidence SHA-256
    ef6afaaafd12aabff83ac9b28194f6670846518dfdf9ed1c6bc715cbdf542bb3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:02:18
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 01:11:28.000000
    Evidence SHA-256
    347c2bf021dad97e9efdb420ba9938ea29c39eddd52f37b5d7e36b7aea9b0596
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:28
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 01:11:28.000000
    Evidence SHA-256
    347c2bf021dad97e9efdb420ba9938ea29c39eddd52f37b5d7e36b7aea9b0596
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:28
    Evidence reason
    alive_content
  17. current_state_backfillunknown
    Observation source
    current_state_backfill
    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-31 23:44:15.000000
    Evidence SHA-256
    c1bea4a372c04b1cd82164c0af6e6d2eadb9fa35eb73704a165f72bb8ec5e3f3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:44:15
    Evidence reason
  18. 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-31 23:44:15.000000
    Evidence SHA-256
    c1bea4a372c04b1cd82164c0af6e6d2eadb9fa35eb73704a165f72bb8ec5e3f3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:44:15
    Evidence reason
  19. 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-31 23:31:41.538396
    Evidence SHA-256
    d507886309fe7925b612af112c97b5593f8ff1d1bd6793149e30d59a14244ced
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:31:41.538396
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    wormhole-foundation.us detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Automated brand label: Wormhole · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 33
  • 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: 2/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: Wormhole
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Added to PhishDestroy

    wormhole-foundation.us

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    2/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

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

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

wormhole-foundation.us

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery SSL Labs CF Radar Open report OTX 4 refs 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?

4 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 wormhole-foundation.us)
  • 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/wormhole-foundation.us"
  title="PhishDestroy threat report for wormhole-foundation.us"
  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>