VirusTotal
20 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“410 Gone”
Assessment based on the stored source evidence below. Review sources →
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.
20 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
no 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.
stored report
View stored capture ↗A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA 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 bafkreiew7fbnac76pnq2nkw5you7mrwbzcgmgdb664vklfxmjb75p2xq2e.ipfs.dweb.link shows a consistent pattern of malicious activity associated with generic phishing. The domain was created on February 24, 2017 and is registered through CSC Corporate Domains, Inc. Infrastructure inspection reveals that the hostname resolves to the IPv4 address 209.94.90.2, a server that is currently listed on at least one security blocklist. The same host is also flagged by PhishDestroy, indicating that it has been identified as part of a phishing infrastructure.
VirusTotal scans have returned 20 positive detections out of 91 security vendors, confirming that a notable portion of commercial scanners consider the domain malicious. No additional public intelligence such as Safe Browsing verdicts, OTX entries, SSL certificate details, HTTP response codes, or page‑title information is available at this time, so the exact content served by the site remains unverified. Defenders should treat the domain as high‑risk: block any outbound connections to the address 209.94.90.2, add the full hostname to DNS‑based blocklists, and monitor for any internal use of the domain in authentication workflows.
Continuous re‑evaluation is advised, especially if new telemetry surfaces from sandbox analysis or if the domain begins to appear in further vendor feeds. Until more contextual evidence emerges, the precautionary stance is to deny traffic to this host and to include it in existing phishing detection rules.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
Edge-IP reputation is not attributed to this domain.
tate.ns.cloudflare.comLocation describes the IP network.
d0288eee53fe6cd1f9f87a81913f8588e1bbf669ffed10b93856374fa095bdf3dweb.linkSaved 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 bafkreiew7fbnac76pnq2nkw5you7mrwbzcgmgdb664vklfxmjb75p2xq2e.ipfs.dweb.link · checked Jul 29, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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://bafkreiew7fbnac76pnq2nkw5you7mrwbzcgmgdb664vklfxmjb75p2xq2e.ipfs.dweb.link/; server=cloudflare
209.94.90.2.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
Unknown
probe_inconclusive
Unavailable→Reachable
Reachable→Unavailable
Unknown
9 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.
Reported by 1 community member, first seen Jun 9, 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