VirusTotal
6 / 91
“Can’t Find the Server”
The domain metamaskteam.io was first observed on 2026-10-04 and was listed on both the MetaMask and SEAL external blocklists as of 2026-10-05. Phishdestroy also recorded an internal listing for this domain.
On 2026-10-05, metamaskteam.io appeared on the MetaMask and SEAL external blocklists. Phishdestroy internally listed the domain, and it was registered with ENOM, INC. on 2026-09-30. An SSL certificate from Let's Encrypt / YR1 was scanned on 2026-10-04.
The presence of metamaskteam.io on the MetaMask and SEAL blocklists, along with its internal listing by Phishdestroy, indicates that multiple sources have recorded this domain for reference. The registration and SSL scan dates provide additional context for when these records were created.
For metamaskteam.io, retain the MetaMask and SEAL blocklist entries and the Phishdestroy internal listing for ongoing monitoring. Keep the registration and SSL certificate records available for comparison with future source updates.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
ApacheScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Apache
mdns1.hostwindsdns.commdns2.hostwindsdns.commdns3.hostwindsdns.commdns4.hostwindsdns.comLocation describes the IP network.
62a9cd437a33c012953e5b8b365b816915f3e60539873a5aad55505958c53c51www.metamaskteam.ioSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of metamaskteam.io · checked Oct 5, 2026
192.142.53.152. 10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
79 stored lookalike domains
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
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