Skip to security report
hedgeindexfunds.com favicon
Domain security and threat intelligence

hedgeindexfunds.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded hedgeindexfunds.com on 2026-11-22. Stored VirusTotal result: 1/92 engines flagged. Analysis time (as stored): 2026-11-22 10:59 UTC. Retrieved (as stored): 2026-11-22 11:02 UTC.

Page title: “hedgeindexfunds.com”

More about the sources
Recorded security signals

Stored VirusTotal result: 1/92 engines flagged. Analysis time (as stored): 2026-11-22 10:59 UTC. Retrieved (as stored): 2026-11-22 11:02 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 1/92
Registrar
United StatesSpaceship
Resolved IP
United States23.153.104.17Aquiryn LLC
First seen by PhishDestroy
2026-11-22
OTX
community references
Page captures
open gallery
Reports sent
view timeline
OTX: 1 ref 2026-11-22 1 Report Sent

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded hedgeindexfunds.com on 2026-11-22. Stored VirusTotal result: 1/92 engines flagged. Analysis time (as stored): 2026-11-22 10:59 UTC. Retrieved (as stored): 2026-11-22 11:02 UTC. Risk: high (evidence score 55/100). Registrar: Spaceship. Hosting: Aquiryn LLC. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
VirusTotal
1 / 92
Hosting
United States23.153.104.17Aquiryn LLC
Registrar
United StatesSpaceship
OTX
1 community ref
Page captures
5

Recorded source summary

PhishDestroy first observed hedgeindexfunds.com on Nov 22, 2026. The captured page title is “hedgeindexfunds.com”. Current evidence score: 55/100 (high).

One source contains a positive finding: VirusTotal. VirusTotal recorded 1 detections among 92 engines: Netcraft on Nov 22, 2026 at 10:59 UTC. Additional recorded evidence: AlienVault OTX listed 1 community pulse reference (not vendor detections) on Nov 22, 2026 at 11:03 UTC.

The collector marked the hostname reachable on Nov 22, 2026 at 11:01 UTC, but did not retain the HTTP response code. Registration records for the domain list Spaceship, Inc. as the registrar and Nov 20, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 23.153.104.17 on AS32561 (Aquiryn LLC). The recorded endpoint location is Sheridan, US. The stored server header is LiteSpeed. DOM analysis on Nov 22, 2026 at 11:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 5 visual captures from PhishDestroy, URLScan, Cloudflare Radar, and URLQuery. TLS metadata lists Let's Encrypt / YR2 as the certificate issuer with validity through Feb 19, 2027; checked Nov 22, 2026 at 11:02 UTC.

Stored content provides classification context alongside the positive source finding.

Source evidenceVirusTotal 1 / 92 · OTX 1 references 4 sources

VirusTotal

1 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
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
Result state
observed
Numerator
1
Denominator
92
Vendors
Netcraft
Observed at
2026-11-22 10:59:15
Checked at
2026-11-22 12:02:33
Fetched at
2026-11-22 11:02:34

OTX

1 community reference

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields
Separate stored summary: clean

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

Verdict
clean
Source path
phishdestroy.technologies.cf_radar
Scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

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: 16 fields

Mail configuration

MX records
  • hedgeindexfunds.com
SPF record
v=spf1 +a +mx +ip4:192.168.168.2 ~all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
2

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
4
Archived days
10
Snapshots per day
0
Average page size, bytes
1175

Page title and metadata

Page title
Bot Verification

Ports

Open ports
  • 110
  • 443
  • 993
  • 995

Carbon estimate

Bytes
1968
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    198.251.89.201
    Host
    ns8.my-control-panel.com
  • IP address
    23.153.104.16
    Host
    ns7.my-control-panel.com
DNS zone
hedgeindexfunds.com

Location

IP address
23.153.104.17
ASN
32561
Organization
Aquiryn LLC
Country
US

DNS records

A
  • 23.153.104.17
MX
  • Mail server
    hedgeindexfunds.com
    Priority
    0
NS
  • ns8.my-control-panel.com
  • ns7.my-control-panel.com
SOA
Primary nameserver
ns7.my-control-panel.com
Hostmaster
admin.my-control-panel.com
Serial
2026112201
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 +a +mx +ip4:192.168.168.2 ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
23.153.104.17
IP version
4

Redirects

Redirect chain
  • https://hedgeindexfunds.com

TXT records

Records
  • v=spf1 +a +mx +ip4:192.168.168.2 ~all

Registration record

Registrar
Spaceship, Inc.
Registrar IANA ID
3862
Registrar URL
http://www.spaceship.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns7.asurahosting.com
  • ns8.asurahosting.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
LiteSpeed
Content-Type
text/html
X-Frame-Options
SAMEORIGIN
Original source fields · JSON
Mail configuration
MX: hedgeindexfunds.com; Spf: v=spf1 +a +mx +ip4:192.168.168.2 ~all; Dkim: default; Dmarc: ✓; Dkim bits: 2048; Spf lookups: 2
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-22T11:04:00Z; First: 2011-02-08T01:54:26Z; Changes: 4; Days archived: 10; Scans per day: 0; Avg page bytes: 1175
Page title and metadata
Title: Bot Verification
Ports
Open: 110, 443, 993, 995
Carbon
Bytes: 1968; Co2 grams: 0.0001; Cleaner than: 95
DNS server
NS: (IP: 198.251.89.201; Host: ns8.my-control-panel.com), (IP: 23.153.104.16; Host: ns7.my-control-panel.com); Zone: hedgeindexfunds.com
Location
IP: 23.153.104.17; ASN: 32561; Org: Aquiryn LLC; Country: US
DNS records
A: 23.153.104.17; MX: Exchange: hedgeindexfunds.com; Priority: 0; NS: ns8.my-control-panel.com, ns7.my-control-panel.com; Soa: Nsname: ns7.my-control-panel.com; Hostmaster: admin.my-control-panel.com; Serial: 2026112201; Refresh: 3600; Retry: 1800; Expire: 1209600; Minttl: 86400; Txt: v=spf1 +a +mx +ip4:192.168.168.2 ~all
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
HTTP security policies
Xframeoptions: SAMEORIGIN; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 23.153.104.17; Family: 4
Redirects
Chain: https://hedgeindexfunds.com
Txt records
Records: v=spf1 +a +mx +ip4:192.168.168.2 ~all
Registration record
Registrar: Spaceship, Inc.; Registrar iana ID: 3862; Registrar URL: http://www.spaceship.com; Created: 2026-11-20T18:25:30Z; Updated: 2026-11-20T20:50:02Z; Expires: 2027-11-20T18:25:30Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: ns7.asurahosting.com, ns8.asurahosting.com; Dnssec: unsigned
HTTP headers
Headers: Server: LiteSpeed; Content type: text/html; X frame options: SAMEORIGIN

Questions about hedgeindexfunds.com

Is hedgeindexfunds.com legit?

PhishDestroy rates hedgeindexfunds.com as high risk (evidence score 55/100) from the recorded evidence; it was first recorded on 2026-11-22. Stored VirusTotal result: 1/92 engines flagged. Analysis time (as stored): 2026-11-22 10:59 UTC. Retrieved (as stored): 2026-11-22 11:02 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is hedgeindexfunds.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on hedgeindexfunds.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used hedgeindexfunds.com?

  • 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
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)

Domain details

Domain
Registrar Spaceship US(US)
Hosting abuse contact abuse@aquiryn.com Aquiryn LLC · AS32561
RegistrationExpires 2027-11-20
Technical detailsProvenance & timestamps
First Detected2026-11-22
DOM Analysisanalyzed 2026-11-22score 0/100
Submitted URLhttps://hedgeindexfunds.com/
Case ID
Observed page title
hedgeindexfunds.com
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 88 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States23.153.104.17
Network ASN
AS32561
Organization
Aquiryn LLC
Observed location
United StatesSheridan, US
Server header
LiteSpeed

Nameservers 2

  • ns7.my-control-panel.com
  • ns8.my-control-panel.com

SOA

  • nsname: ns7.my-control-panel.com
  • hostmaster: admin.my-control-panel.com
  • serial: 2026112201
  • refresh: 3600
  • retry: 1800
  • expire: 1209600
  • minttl: 86400

Mail routing 1 MX record

  • hedgeindexfunds.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-11-21 04:47:12
Valid until
2027-02-19 04:47:11
Hostname match
Yes
Validity
Within stored validity dates
Collection time
2026-11-22 11:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd3186e1e8bd953d9c8c5f5a7e656f7091f8dc1b9c1e17c73bb3829617459f5fb
Certificate names · 2 SANs
  • *.hedgeindexfunds.com
  • hedgeindexfunds.com

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

Recorded subdomains3

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • crypto.hedgeindexfunds.comDomain record
  • en.hedgeindexfunds.comDomain record
  • www.hedgeindexfunds.comDomain record
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed
Netcraft

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

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: https://hedgeindexfunds.com/
Bot Verification
Response
HTTP 200
HTML body
1.9 KB
Compressed
863 B
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html
Content-Encoding: gzip
Server: LiteSpeed
Cache-Control: no-cache,no-store,private
Security headers present
X-Frame-Options
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 36a9e7f1c95b82ffb99743e0c5c4ce95d83c9a430aac59f84ef3cbfab6145068
Saved response-header values · 10
Alt-Svc
h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
Cache-Control
no-cache,no-store,private
Connection
close
Content-Encoding
gzip
Content-Length
1143
Content-Type
text/html
Date
Sun, 22 Nov 2026 11:02:13 GMT
Server
LiteSpeed
Vary
Accept-Encoding
X-Frame-Options
SAMEORIGIN

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

Registration & observation details1

Availability observations

Last reachable observation

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

All stored data89
Open complete records

Captured network requests

Network requests: 26 SHA-256 hashes: 10 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-22 11:03 UTC.

Open this scan on URLScan 01a202ea-7001-718b-b016-73c1f23d1661 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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 backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    stale
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 12:01:44.000000
    Evidence SHA-256
    278a860426d367cdf9eac60ddf1619557bdd72f31c8dded31ecb4f421bd26e03
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 12:01:44
  2. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 12:01:44.000000
    Evidence SHA-256
    278a860426d367cdf9eac60ddf1619557bdd72f31c8dded31ecb4f421bd26e03
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 12:01:44

Threat Response Pipeline

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

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
  • Threat Ingested
    hedgeindexfunds.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Spaceship, Inc.. Abuse contacts: 1.
    • abuse@spaceship.com
Publication & AvailabilityDestroyList Published recorded

Recorded activity

7 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+40 h 33 min
  3. Added to PhishDestroy+2 min
  4. First abuse report sent+1 min

Reported 40 h 37 min after registration

  1. Wayback Machine

    Page archived

    same minute
  2. AlienVault OTX

    1 community references

    same minute
  3. Abuse report sent

    PD-F706BE196E905A58CA65 · Receipt 85587

    abuse@spaceship.com
    same minute
  4. Cloudflare Radar

    Phishing

    same minute
  5. Added to PhishDestroy

    hedgeindexfunds.com

    same minute
  6. URLScan

    Page captured

    +2 min
  7. VirusTotal

    1/92 engine detections

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.

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.

hedgeindexfunds.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-F706BE196E905A58CA65 Recipient: abuse@spaceship.com
Page title stored with report: hedgeindexfunds.com
PDF notice generated
Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 hedgeindexfunds.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

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.

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