VirusTotal
1 / 89
“Seedify Fund”
seedify-fund-burn.vercel.app was observed to return HTTP status 200 during a check on 2026-10-01. The domain was first recorded on 2026-09-01, providing a clear timeline for reference.
On 2026-10-01, ScamSniffer listed seedify-fund-burn.vercel.app on its external blocklist. VirusTotal, as of 2026-09-15, reported 1 detection out of 89 scanners. The SSL certificate was issued by Google Trust Services / WR1 and scanned on 2026-09-13. PhishDestroy internally listed the domain, and PageSpeed measured a performance score of 22 on 2026-09-13.
The records from ScamSniffer, VirusTotal, and PhishDestroy provide separate perspectives, each captured on different dates, which allows for a chronological comparison of observations. Since the HTTP status, SSL scan, and performance score were recorded at distinct times, each fact should be considered as a snapshot rather than a continuous state.
Retain all dated evidence for seedify-fund-burn.vercel.app, including blocklist and scanner results, to support future comparisons. When reviewing the domain, store new findings alongside these records and avoid submitting any sensitive information during analysis.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
VercelScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093Saved 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 seedify-fund-burn.vercel.app · checked Sep 13, 2026
7 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