VirusTotal
10 / 92
kntq-staking.com was listed on the MetaMask external blocklist as of 2026-10-12, reflecting its inclusion in recent security monitoring. The domain was also observed in other security sources within days of its registration.
On 2026-10-12, MetaMask and SEAL both recorded kntq-staking.com on their external blocklists. VirusTotal checked the domain on 2026-10-11, documenting 10 detections out of 92 total scanners. OTX included the domain in 2 pulses as of 2026-10-12. PhishDestroy internally listed kntq-staking.com on 2026-10-12. The domain was registered on 2026-09-27 with NICENIC INTERNATIONAL GROUP CO., LIMITED.
VirusTotal provides a detection count from a wide range of security scanners, offering a quantitative measurement of how the domain was evaluated at the time of its scan. PhishDestroy contains an internal listing, which documents the domain's presence in its monitoring records. The MetaMask and SEAL blocklist entries represent external references that identify kntq-staking.com in their respective security databases.
For kntq-staking.com, preserve the VirusTotal, OTX, and PhishDestroy records for ongoing comparison and reference. Review the MetaMask and SEAL blocklist entries to monitor any future changes. Retain all dated source records to maintain a clear context for future assessments.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Edge-IP reputation is not attributed to this domain.
leanna.ns.cloudflare.comLocation describes the IP network.
Google PageSpeed Insights — mobile performance audit of kntq-staking.com · checked Oct 12, 2026
104.21.56.58. 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.
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