Skip to security report
Domain security and threat intelligence
starkware.company favicon

starkware.company

Registrar
Dynadot
Resolved IP
104.21.32.9
Registered
Jun 8, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 5/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 URLQuery threat systems: 1 alert Automated brand label: MetaMask
OTX: 4 refs Aug 26, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dynadot.com. The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260826-B35C3C
Current status
HTTP 301 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 5 / 91 · OTX 4 references 8 sources

VirusTotal

5 / 91 engine detections

Open report

URLQuery

1 threat-system alert

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
Quad9 DNS starkware.company malicious Sinkholed

Analysis

Critical
VirusTotal
5 / 91
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

starkware.company is a phishing domain that borrows the name of StarkWare, the company behind the Starknet ecosystem, to lure crypto users who expect an official StarkWare property. PhishDestroy first flagged it on 2026-08-26. As of 2026-10-19 the domain was still alive and redirecting visitors elsewhere, so the threat remains active.

How the scam works

Brand-impersonation sites like this one rely on a convincing lookalike address. The domain is StarkWare's own name under an unrelated extension, which users mistake for the real company. The page shows only the title "Loading…", which suits a site that hands visitors off through a redirect rather than serving its own content. Schemes built on a Starknet-related brand typically promise token claims, airdrops or account tools, then ask the visitor to connect a wallet, sign transactions or reveal a seed phrase. Any of those steps can give the operator control over the victim's funds.

Evidence

Five of 91 VirusTotal engines flag the domain as of 2026-10-02: ChainPatrol, alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That count is modest, but it includes ChainPatrol, a crypto-focused vendor. The domain also sits on the MetaMask and SEAL blocklists, both maintained by teams that track wallet-targeting fraud. Spamhaus lists it in its DBL as a phishing domain, and four AlienVault OTX pulses reference it.

Infrastructure

The domain was registered through Dynadot Inc on 2026-06-08, about eleven weeks before PhishDestroy detected it. That gap suggests it was set up in advance and possibly kept quiet before use. It resolves to an address hosted in Germany. Its certificate comes from Google Trust Services (WE1), an automated issuer, so the padlock in the browser says nothing about who runs the site.

What to do

If you connected a wallet or signed anything here, move your assets to a fresh wallet. Then use a token-approval checker to revoke any permissions granted during the visit. If you typed a seed phrase or private key, treat that wallet as compromised and stop using it. Reach StarkWare and Starknet resources only through bookmarks you saved yourself or links from their verified official channels. Security teams should block the domain at DNS and proxy level and add it to wallet and browser protection lists.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

TLS Certificate
Issued by Google Trust Services · stored validity ends in 69 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot (Unknown)
RegistrationCreated Jun 8, 2026 (134d) — Expires Jun 8, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedAug 26, 2026
DOM Analysisanalyzed Oct 9, 2026score 95/100
Submitted URLhttp://starkware.company/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.32.9
Observed location
Frankfurt am Main, DE
Server header
CDN77-Turbo

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • coleman.ns.cloudflare.com
  • sarah.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-10-04 08:00:00
Valid until
2027-01-02 08:59:46
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:13 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2d81028a4eac8f31b668b259f56f4e22cab5c5cf142aa1f6f8a1f2a95da481d9

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

Latest Classified Outcome 2026-10-19 10:07:48 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 10:07:48 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-19 10:07:48 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.
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
Registration & observation details2

Availability observations

Last reachable 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.

Stored observation history27

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

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 22
  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Unavailable→Reachable

  8. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  9. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  10. Availability monitor · Recorded state

    Reachable→Unavailable

  11. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    Unavailable→Reachable

  16. Availability monitor · Recorded state

    Reachable→Unavailable

  17. Availability monitor · Recorded state

    Unavailable→Reachable

  18. Availability monitor · Recorded state

    Reachable→Unavailable

  19. Availability monitor · Recorded state

    Unavailable→Reachable

  20. Availability monitor · Recorded state

    Reachable→Unavailable

  21. VirusTotal · Detection count

    0→5

  22. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    5/91 engine detections

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. Abuse report sent

    PD-20260826-B35C3C

    abuse@dynadot.com
  5. Added to PhishDestroy

    starkware.company

    View source
  6. URLScan

    Page captured

    View source

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

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

starkware.company

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260826-B35C3C Recipient: abuse@dynadot.com
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Deep Analysis
Help & reporting

Were You Affected by This Site?

7 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

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 →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 starkware.company)
  • 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

Live Threat Feed Appeal This Listing
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.

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