Skip to security report
Domain security report
metamaskverifyweb3.com favicon

metamaskverifyweb3.com

“Wallet verification”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 23/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: MetaMask
OTX: 17 refs Jun 25, 2026 MetaMask 1 Report Sent
API
Registrar
Hosting Concepts
Resolved IP
176.123.0.199
Registered
Jun 22, 2026
2 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 23. 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@registrar.eu. The latest stored availability evidence still shows the domain reachable; 3 months 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
3 months
Reports sent
1
Latest case ID
PD-20260625-739D3A
Current status
HTTP 200 at latest stored check

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
23 det.
OTX references
URLScan
URLScan
TLS Certificate
Expired or unverified dates -28d
Let's Encrypt / YR2 · Hostname coverage not recorded
Age
4 mo
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

23 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLScan verdict

malicious

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

17 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
23/89
OTX
17 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

This domain is flagged as a high-risk credential harvesting site specifically designed to impersonate MetaMask, a widely used cryptocurrency wallet service. The threat type involves brand impersonation with the intent to harvest sensitive wallet credentials, seed phrases, and private keys from unsuspecting users through deceptive verification workflows. Analysis indicates the domain is engineered to exploit trust in the MetaMask brand, potentially leading to unauthorized asset transfers and irreversible financial losses. Infrastructure analysis reveals multiple high-confidence indicators of malicious activity. The domain was registered on June 22, 2026, through Hosting Concepts B.V. d/b/a Registrar.eu, and currently resolves to IP address 176.123.0.199 located in Moldova under AS200019 (ALEXHOST SRL). VirusTotal reports 20 out of 95 security vendors flagging the domain as malicious, while it appears on four distinct security blocklists including PhishDestroy, MetaMask's internal systems, SEAL, and Phishunt. The SSL certificate, issued by Let's Encrypt (serial YR2), provides basic encryption but does not validate legitimacy, as fraudulent sites commonly use free certificates to appear authentic. The domain remains active despite widespread detection, suggesting persistent operational intent. Mitigation requires immediate action from both end users and network defenders. Users should never enter wallet credentials, seed phrases, or private keys on any verification page, particularly those not hosted on the official metamask.io domain. Network-level protections should include DNS sinkholing for 176.123.0.199, AS200019 route filtering where feasible, and implementation of blocklist entries for the domain across security gateways. Organizations handling cryptocurrency transactions should deploy strict domain validation policies and educate users on recognizing impersonation attempts, focusing on URL inspection, SSL certificate details, and verification of official communication channels. Given the irreversible nature of cryptocurrency transactions, proactive blocking of this infrastructure is critical to prevent credential compromise and subsequent asset theft.

Data coverage & collection

19 · datasets with records / 12 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
23 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
17 · community references
External blocklists
2 · external matches
Spamhaus DBL
DBL_PHISH
Domain registration
Hosting Concepts B.V. d/b/a Registrar.euCollection time not recorded
Network & DNS
176.123.0.199 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YR2
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
95/100 · mobile performance
Response records
1 · outgoing report records
Availability history
26 · stored state changes
Source observation history
2 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • Cloudflare Radar
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Hosting Concepts B.V. d/b/a Registrar.eu · 176.123.0.199 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: MetaMask report ↗
IP Reputation abuse score 2/100 9 reports Phishing checked Sep 23, 2026
OTX tags 2026-06activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Hosting Concepts NL(NL)
RegistrationCreated Jun 22, 2026 (117d) — Expires Jun 22, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedJun 25, 2026
DOM Analysisanalyzed Jun 25, 2026score 100/1001 brand signal
Submitted URLhttp://metamaskverifyweb3.com/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
176.123.0.199
Network ASN
AS200019
Organization
ALEXHOST SRL
Observed location
Chisinau, MD
Server header
LiteSpeed
Nameservers 2
  • courtney.ns.cloudflare.com
  • guy.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-06-22 08:05:07
Valid until
2026-09-20 08:05:06
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-10-17 04:03:55 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfafd697b759f593436ee805c70191094f62a74b5d93eb9a53ed75f3a48553365

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-17 02:15:26 UTC

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-10-17 02:15:26 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 02:15:26 UTC last content: 2026-10-17 02:15:26 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

23 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 23 detections
ChainPatrol
Criminal IP
alphaMountain.ai
BitDefender
Certego
Chong Lua Dao
CRDF
CyRadar
Ermes
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of metamaskverifyweb3.com · checked Sep 13, 2026

95
Good
Performance
FCP
0.97s
First Contentful Paint
LCP
2.04s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
50ms
Total Blocking Time
SI
5.34s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Server header seen by scanner
Caddy

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Caddy

Title shown to the security scannermetamaskverifyweb3.com
Title shown to a browser visitorWallet verification
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Unreachable

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-08-06 22:14:56 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-08-06 10:23:36 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
Stored observation history28

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

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 23
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    origin_unreachable · http_5xx

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · Recorded state

    live_content→Unknown

    origin_unreachable · http_5xx

  18. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  19. Availability monitor · Recorded state

    live_content→Unknown

    origin_unreachable · http_5xx

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unavailable→Reachable

  23. Availability monitor · Recorded state

    Reachable→Unavailable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
metamaskverifyweb3.com detected and queued for full analysis
Jun 25, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Sep 24, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Jun 26, 2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
Jul 29, 2026
VirusTotal
23/89 recorded on VirusTotal
Sep 19, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
OTX Community References
17 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 3, 2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Jun 26, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Aug 7, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 502); the cause was not independently established.
Aug 6, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Hosting Concepts B.V. d/b/a Registrar.eu, 2 abuse contacts
abuse@registrar.euabuse@alexhost.com
Jun 25, 2026
DestroyList Published
Jun 25, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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.

Related infrastructure

Shared hosting, registrar records and related domains

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

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260625-739D3A Recipient: abuse@registrar.eu
PDF notice generated Notice text archived (608 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (NL):
Dutch Criminal Code - Article 326 (Computer Fraud)
Dutch Criminal Code - Article 326c (Phishing)
GDPR
Netherlands law explicitly criminalizes phishing and computer fraud.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 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 metamaskverifyweb3.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

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: metamaskverifyweb3.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Wallet verification”. Apparent target: MetaMask.

VirusTotal detections for metamaskverifyweb3.com: 23 (2026-09-19 02:34:33 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

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