VirusTotal
7 / 89 engine detections
PhishDestroy first recorded j3.appwrite.network on 2026-03-03. Stored VirusTotal result: 7/89 engines flagged.
Page title: “Sign~in to view”
Stored VirusTotal result: 7/89 engines flagged. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@fastly.com. The latest stored availability evidence still shows the domain reachable; 8 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
PhishDestroy analysis, earlier unreviewed version
The domain j3.appwrite.network is flagged as a high-risk generic phishing site, currently active as of July 12, 2026. This domain was registered through Fastly on March 03, 2026, and is known to resolve to the IP address 151.101.131.52. The page title 'Sign~in to view' suggests that the site may be designed to mimic a legitimate sign-in page, potentially to trick users into providing sensitive credentials. The domain appears on one security blocklist and is blocked by PhishDestroy, indicating a level of suspicion and risk associated with it. VirusTotal reports that 11 out of 95 security vendors flag this domain, which, while not a consensus, suggests that there is a notable concern among security professionals. The domain uses several technologies, including Varnish, Bootstrap, Cloudflare, jQuery, HSTS, Google Hosted Libraries, cdnjs, and Popper, which are commonly employed in both legitimate and malicious web operations. The Gridinsoft trust score for this domain is 0 out of 100, reinforcing the high-risk assessment. While the exact content and target of the phishing attempt are not yet fully analyzed, the combination of a low trust score, partial security vendor consensus, and the use of a plausible sign-in page title indicates a significant threat. Defenders should block this domain at the network level and educate users to be wary of unsolicited sign-in requests, especially those that redirect to unfamiliar URLs. Regular monitoring of this domain and any associated IP addresses is recommended to track potential changes in the threat landscape.
7 / 89 engine detections
6 threat-system alerts
Open reportPhishing
Open report5/14
1/100
Trust score, lower = worse
Open reportMalicious
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
78 / 100 · heuristic score · 1 brand reference · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| YARAhub by abuse.ch | onedriveverification.surge.sh/jquerys.js | malware | Detects file containing Telegram Bot API |
| OpenDNS | j3.appwrite.network | phishing | Phishing Block |
| DNS4EU | j3.appwrite.network | malicious | Sinkholed |
| Cloudflare DNS | j3.appwrite.network | malicious | Sinkholed |
| DigiCert UltraDNS | j3.appwrite.network | malicious | Sinkholed |
| Quad9 DNS | j3.appwrite.network | malicious | Sinkholed |
PhishDestroy rates j3.appwrite.network as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-03-03. Stored VirusTotal result: 7/89 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on j3.appwrite.network. A confirmed blockchain transaction cannot be reversed.
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
661cab1c9bbcfe08b8ad11b6ad1fbc513d489b643a5a28c84ca33c6215723aeb · 143319 bytes a2cbf78b8705af0deaef000ad2058ac3df4ef4020d9ca96bab895d73a6229c37 · 76821 bytes a2cbf78b8705af0deaef000ad2058ac3df4ef4020d9ca96bab895d73a6229c37 · 76821 bytes 6ea9f21a0280086e0d689758eee0c68760a0516770b5e653804114124032432f · 7859 bytes 95505cb54dd59500ac00ac305d60312358d9ffcace9a9a7ca56d40a6dc85f110 · 6911 bytes 04e505de695f22b447597544fd257b129cec656d5f27261069dd6d17260d448f · 205884 bytes 
Registrable domain behind this subdomain: appwrite.network. 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.
rosalyn.ns.cloudflare.comLocation describes the IP network.
ab4fe143debe5caf2b0aa57ac75528529aeb3af669856693135c7cb3a266e788appwrite.networkimagine.diySaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was reachable but behind an access challenge at the latest check.
Google PageSpeed Insights — mobile performance audit of j3.appwrite.network ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://j3.appwrite.network/https://j3.appwrite.network/Cache-Control: no-cache, no-store, must-revalidateContent-Type: text/html; charset=UTF-8Server: swoole-http-serverbytesno-cache, no-store, must-revalidatekeep-alive10243text/html; charset=UTF-8Fri, 30 Oct 2026 11:25:38 GMT0no-cacheswoole-http-server1.1 varnish0bBHNYBByXcKOErbUf2l16--F_fra16989b77600387e287806siteMISS00.21138787269592framissmisscache-ber1080020-BERS1793359539.718897,VS0,VE248Values retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 12 SHA-256 hashes: 12 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 05:31 UTC.
Open this scan on URLScan 019cb3ab-b0d2-7315-9798-acf06419defe ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
j3.appwrite.network Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 31. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 1344 d 2 h after registration
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Reported by 1 community member, first seen 2026-03-03
PD-20260303-2FBCB0 Recipient: abuse@fastly.com Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
j3.appwrite.network)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.