Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 28 hours 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.
metamask[.]io[.]secure[.]login[.]bitstek[.]io
“Not Acceptable!”
metamask.io.secure.login.bitstek.io is a subdomain of bitstek.io. PhishDestroy first observed the hostname on Aug 26, 2026. The hostname explicitly references MetaMask; stored content metadata identifies the same apparent target. The captured page title is “Not Acceptable!”. Stored page analysis classifies the content as credential phishing. Current evidence score: 95/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, MetaMask, and SEAL. VirusTotal recorded 17 detections among 91 engines: ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CTX AI, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, SOCRadar, Sophos, VIPRE, Webroot on Aug 27, 2026 at 05:08 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 27, 2026 at 14:20 UTC. Non-positive and contextual checks: URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Aug 27, 2026 at 17:08 UTC. URLScan completed without a malicious verdict (score 0) on Aug 26, 2026 at 11:08 UTC.
The collector marked the hostname reachable on Aug 26, 2026 at 11:01 UTC, but did not retain the HTTP response code. Registration records for the registrable domain bitstek.io list GoDaddy.com, LLC as the registrar and Apr 23, 2022 as the creation date. At collection time, the hostname resolved to 216.10.252.225 on AS394695 (PDR). The recorded endpoint location is Mumbai, IN. The stored server header is Apache. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Oct 27, 2026; checked Aug 26, 2026 at 22:02 UTC.
The content indicators and 3 positive source findings support the current MetaMask-themed credential phishing classification.
Threat Response Pipeline
Public Blocklist Status
Technologies · 1 identified
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
nginx.org 100% confidenceVirusTotal Analysis
Evidence & External Reports
PD-20260826-5413AD Recipient: abuse@publicdomainregistry.com Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive