Skip to security report
Domain security and threat intelligence
extrafi.digital favicon

extrafi.digital

“Stake EXTRA Tokens & Earn Rewards | ExtraFi”

Registrar
PDR
Resolved IP
188.114.97.3
Registered
May 15, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 6/91 Stored blocklist matches: 3 URLQuery threat systems: 1 alert Automated brand label: MetaMask
Sep 2, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 6 / 91 6 sources

VirusTotal

6 / 91 engine detections

Open report

URLQuery

1 threat-system alert

Open report

OTX

no 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
DNS4EU extrafi.digital malicious Sinkholed

Analysis

Critical
VirusTotal
6 / 91
Page captures
3

PhishDestroy threat report

Overview

extrafi.digital posed as ExtraFi, presenting itself as the place to "Stake EXTRA Tokens & Earn Rewards." It targeted holders of the EXTRA token and DeFi users looking for staking yield. PhishDestroy first flagged it on 2026-09-02. The site has been offline since 2026-09-11, and its DNS was still inactive when we last checked on 2026-10-19.

How the scam works

A fake staking dashboard gives victims a reason to connect a wallet and approve transactions, because that is exactly what a real staking portal asks for. On a page like this, the "stake" or "claim rewards" button can trigger a token approval, a permit signature or a direct transfer instead of a deposit into ExtraFi's contracts. Once that is signed, the operator can move the approved tokens out of the wallet, and EXTRA is not the only asset at risk. The domain name and page title echo the real brand closely enough that a hurried user may not notice the different address.

Evidence

Four blocklists list the domain: PhishDestroy, MetaMask, ScamSniffer and SEAL. This matters because MetaMask's list can trigger a warning inside the wallet itself. On VirusTotal, 6 of 91 engines flagged it on 2026-09-02: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft and Kaspersky. Most general-purpose scanners missed it, so the crypto-focused blocklists are the stronger signal here.

Infrastructure

The domain was registered on 2026-05-15 through PDR Ltd. (PublicDomainRegistry.com), about 110 days before we detected it. That gap suggests it was held in reserve or ran quietly before drawing attention. The site sat behind Cloudflare (AS13335, US), which hides the real origin server. It used a free Let's Encrypt certificate, so the padlock in the browser said nothing about whether the site was legitimate.

What to do

If you connected a wallet to extrafi.digital, open a token-approval checker and revoke any allowances or permits you granted around the time of your visit. If you signed anything unfamiliar or tokens have already left your wallet, move your remaining funds to a fresh wallet. Treat any seed phrase you typed into the site as compromised. In the future, reach ExtraFi only through addresses you have verified independently. Defenders should block the domain and check wallet and DNS logs for connections made between 2026-09-02 and 2026-09-11.

Blocklist matchesMetaMask · ScamSniffer · PhishDestroy · SEAL 4
MetaMask Listed View source
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

Observed page title
Stake EXTRA Tokens & Earn Rewards | ExtraFi
Automated brand references
MetaMask
TLS Certificate
Issued by Let's Encrypt · stored validity ends in 45 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.
Registrar PDR (Unknown)
RegistrationCreated May 15, 2026 (156d) — Expires May 15, 2027
Time to First Unavailability 8 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 2, 2026
Submitted URLhttp://extrafi.digital/
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
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • amos.ns.cloudflare.com
  • nola.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-07-20 05:58:06
Valid until
2026-10-18 05:58:05
Validity
Stored certificate expired
Collection time
2026-09-02 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfa04af9532613ce8748deb9dccc8d08aef1a451351016baf53d33a10e59c4ce3

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 08:21:20 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-19 01:13:38 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-02 22:16:13 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-02 22:16:13 UTC → 2026-09-30 16:14:55 UTC · 665.98h midpoint estimate ≈ 2026-09-16 19:15:34 UTC · precision low · basis bounded
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 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
CRDF
ESET
Forcepoint ThreatSeeker
Gridinsoft
Kaspersky

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of extrafi.digital · checked Sep 2, 2026

77
Needs Work
Performance
FCP
3.9s
First Contentful Paint
LCP
3.9s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
665.98
Estimate basis
Bounded by observations
Estimate precision
Low

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

Stored observation history12

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→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. Abuse report sent

    PD-20260902-7F88ED

    abuse@publicdomainregistry.com
  3. VirusTotal

    6/91 engine detections

    View source
  4. Added to PhishDestroy

    extrafi.digital

    View source
  5. 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.

extrafi.digital

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260902-7F88ED Recipient: abuse@publicdomainregistry.com
PDF notice generated Notice text archived (348 chars)
Abuse notice text as sent to the provider
Registrar: PublicDomainRegistry (PDR Ltd.) (India)
Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice
Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Content unavailable
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 extrafi.digital)
  • 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/extrafi.digital"
  title="PhishDestroy threat report for extrafi.digital"
  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>