VirusTotal
5 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“teaprotocol.community”
Assessment based on the stored source evidence below. Review sources →
No stored capture is available for this domain.
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.
5 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
16 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
Analysis of the domain teaprotocol.community indicates it is an active phishing site targeting users of the Tea Protocol, a decentralized project. The domain was registered on June 8, 2026, through an undisclosed registrar. As of July 29, 2026, the domain is flagged by 6 of 91 security vendors on VirusTotal, suggesting detection by a minority of engines but still warranting caution. It appears on three security blocklists, including PhishDestroy, MetaMask, and SEAL, which classify it as malicious infrastructure.
No associated IP addresses, hosting providers, or autonomous system numbers (ASNs) are currently documented in available intelligence. The domain's classification as a phishing site is supported by its inclusion in multiple blocklists, though the exact nature of the phishing content remains unconfirmed due to the absence of page-level analysis. The name 'teaprotocol.community' closely resembles the legitimate Tea Protocol branding, which may be leveraged to deceive users into disclosing credentials, private keys, or other sensitive information.
Defenders are advised to treat this domain as high-risk and implement blocking measures at the network and endpoint levels. Organizations should monitor for connections to this domain in logs and alert users who may have interacted with it. Further investigation into the hosting infrastructure and any linked campaigns is recommended to assess the full scope of the threat.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://teaprotocol.community/; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
randall.ns.cloudflare.comLocation describes the IP network.
2fa6c4c9f55ccc3d8019f14595778ed2c6c235b7274262ecf280a314820dbef0Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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
Reported by 1 community member, first seen Jun 4, 2026
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