VirusTotal
4 / 91 engine detections
Open reporttoyowfoundation.center is a blocklisted domain detected by PhishDestroy on 2026-02-12. Risk: high (65/100). Registrar: NiceNIC. Status: Reachable · access restricted. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. VirusTotal: 4/91 engines flag it. Do not enter credentials or connect a wallet.
4 / 91 engine detections
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain toyowfoundation.center is a generic phishing site posing as an NFT scam. It does not impersonate a known brand or use a recognized drainer kit but is designed to deceive users into disclosing sensitive information or transferring digital assets. As of the latest verification, toyowfoundation.center has been taken offline, though it previously exhibited elevated risk indicators typical of phishing operations.
Technical analysis of toyowfoundation.center reveals limited but notable detection. The domain was flagged by 2 of 95 security vendors on VirusTotal, including Fortinet and SOCRadar, while appearing on 1 security blocklist (PhishDestroy). Registered through NiceNIC International Group Co., Limited on February 21, 2026, it resolved to the IP address 104.21.32.110, hosted by Cloudflare in the US (AS13335). The SSL certificate was issued by Google Trust Services (WE1), and the observed page title was 'Just a moment...'. Technologies detected include HSTS, Cloudflare, and HTTP/3, with nameservers dana.ns.cloudflare.com and johnny.ns.cloudflare.com.
Users who interacted with toyowfoundation.center should assume potential exposure. For NFT-related risks, revoke any token approvals granted to unknown contracts and transfer remaining assets to a new wallet. If credentials were entered, change passwords immediately, enable two-factor authentication, and monitor accounts for unauthorized activity. Report the domain to platforms like Google Safe Browsing, PhishTank, or local cybersecurity authorities to aid in broader mitigation efforts.
No. PhishDestroy classifies toyowfoundation.center as a blocklisted domain (risk: high, 65/100); it was first detected on 2026-02-12. VirusTotal: 4/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on toyowfoundation.center. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
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.
johnny.ns.cloudflare.comLocation describes the IP network.
bbbd85290f25bd7947ed5fa61e5e3d2f5d2da9cbdae0655b1d03f3f3518f6ec5Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
toyowfoundation.center
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unavailable→Reachable
https://radar.cloudflare.com/scan/55147452-f85c-4174-a06c-8cb86ee1f7fb
Reachable→Unavailable
4/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcetoyowfoundation.center
View sourceReported by 1 community member, first seen Feb 12, 2026
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
toyowfoundation.center)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.