VirusTotal
5 / 91 engine detections
Open report
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.
5 / 91 engine detections
Open report1 threat-system alert
Open reportDBL_PHISH
4 community references
Open reportprovider verdict: clean
Open report80/100
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | starkware.company |
malicious | Sinkholed |
PhishDestroy threat report
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.
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.
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.
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.
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.
Last checked
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.
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.
Edge-IP reputation is not attributed to this domain.
coleman.ns.cloudflare.comsarah.ns.cloudflare.comLocation describes the IP network.
2d81028a4eac8f31b668b259f56f4e22cab5c5cf142aa1f6f8a1f2a95da481d9Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unavailable→Reachable
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Reachable→Unavailable
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unavailable→Reachable
Reachable→Unavailable
Unavailable→Reachable
Reachable→Unavailable
Unavailable→Reachable
Reachable→Unavailable
0→5
Reachable
4 community references
View source5/91 engine detections
View sourceNo threat flag
View sourcePD-20260826-B35C3C
starkware.company
View sourcePage captured
View source79 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
starkware.company
PD-20260826-B35C3C Recipient: abuse@dynadot.com 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
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
starkware.company)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.