Skip to security report
Domain security and threat intelligence
westandard.appwrite.network favicon

westandard.appwrite.network

In short

westandard.appwrite.network is a Wetransfer impersonation page detected by PhishDestroy on 2026-03-18. Risk: critical (100/100). Registrar: Appwrite. Status: Last known active. Hosting: FASTLY - Fastly, Inc., US. PhishDestroy sent 1 abuse report. VirusTotal: 10/91 engines flag it. Do not enter credentials or connect a wallet.

“WeTransfer”

Registrar
Appwrite
Resolved IP
2a04:4e42::820
Registered
Jun 28, 2022
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 10/91 URLQuery threat systems: 7 alerts Automated brand label: Wetransfer
Mar 18, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 10. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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; 7 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.

Elapsed since first report
7 months
Reports sent
1
Latest case ID
PD-20260318-A43E28
Current status
HTTP 308 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 10 / 91 8 sources

VirusTotal

10 / 91 engine detections

Open report

URLQuery

7 threat-system alerts

Open report

PhishStats

checked — no match recorded

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
Threat Detection Systems 7 alerts
Detection System Indicator Verdict Alert
OpenDNS westandard.appwrite.network phishing Phishing Block
DNS4EU westandard.appwrite.network malicious Sinkholed
Cloudflare DNS westandard.appwrite.network malicious Sinkholed
DigiCert UltraDNS westandard.appwrite.network malicious Sinkholed
Hagezi Threat Feed westandard.appwrite.network malicious Sinkholed
Hagezi Threat Feed mk2-b4c8d3.ingress-earth.ewp.live malicious Sinkholed
Quad9 DNS mk2-b4c8d3.ingress-earth.ewp.live malicious Sinkholed
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing (detected) Phishing

Analysis

Critical
VirusTotal
10 / 91
Page captures
3

PhishDestroy threat report

Analysis of westandard.appwrite.network indicates a high‑risk generic phishing operation that remains active as of July 12 2026. The domain was registered on March 17 2026 through the Appwrite platform and resolves to the IPv6 address 2a04:4e42::820, which is owned by AS54113 Fastly, Inc. in the United States. HTTP requests return a 403 status, suggesting the front‑end is intentionally restricted or misconfigured, while the SSL certificate is identified as an intermediate R1 chain. Infrastructure fingerprints reveal the presence of Varnish, Cloudflare, Bootstrap, jQuery, HSTS, and several CDN libraries (Google Hosted Libraries, cdnjs, Popper), indicating a typical content‑delivery setup used to host malicious pages. Reputation services flag the domain severely: Gridinsoft assigns a trust score of 0 / 100, Scamadviser records 1 / 100, and it appears on one security blocklist. VirusTotal reports 23 detections out of 94 scanners, confirming malicious activity. The page title returned is “WeTransfer,” but no further content analysis is available, and the domain’s authoritative nameservers could not be resolved. Defenders should prioritize blocking the domain at perimeter firewalls and DNS filtering solutions, monitor for any outbound connections to the associated IP range, and consider adding the domain to internal threat intelligence feeds. Continuous re‑evaluation is advised, as the lack of visible nameserver data and the 403 response may conceal additional payloads that could be revealed if the site becomes accessible.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-03-18T10:41:00Z

Observed: · Retrieved:

Uuid
019d0088-aad6-77fc-bcba-38cd971e0262
Final url
https://westandard.appwrite.network/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://westandard.appwrite.network/",
        "from": "http://westandard.appwrite.network/",
        "status": 307
    }
]
Ip
2a04:4e42::820
Contacted domains
[
    "stackpath.bootstrapcdn.com",
    "ajax.googleapis.com",
    "maxcdn.bootstrapcdn.com",
    "cdnjs.cloudflare.com",
    "code.jquery.com",
    "prod-cdn.wetransfer.net",
    "i.ibb.co",
    "mk2-b4c8d3.ingress-earth.ewp.live"
]
Contacted IP addresses
[
    "2a00:1450:4001:817::200a",
    "104.18.10.207",
    "104.17.25.14",
    "2a04:4e42:600::649",
    "3.174.46.55",
    "45.43.142.6",
    "104.18.11.207",
    "2a04:4e42::820"
]
Asns
[
    "15169",
    "13335",
    "54113",
    "16509",
    "16276"
]
Countries
[
    "DE",
    "US",
    "GB"
]
Linked domains
[
    "wetransfer.com",
    "wetransfer.pr.co",
    "wetransfer.homerun.co",
    "twitter.com",
    "www.facebook.com",
    "www.instagram.com",
    "www.youtube.com",
    "about.wetransfer.com"
]
Social
[
    "https://twitter.com/WeTransfer",
    "https://www.facebook.com/wetransfer",
    "https://www.instagram.com/WeTransfer",
    "https://www.youtube.com/WeTransfer"
]
Document hash
397b51d4837443b5c18b2831ca2761e6488db4647d07de2d29b6281ffeec8f84
Script hashes
[
    "397b51d4837443b5c18b2831ca2761e6488db4647d07de2d29b6281ffeec8f84"
]
Globals
[
    "bootstrap",
    "show",
    "validate",
    "$",
    "jQuery",
    "Popper"
]
Tls
{
    "san": [
        "*.appwrite.network",
        "*.imagine.diy",
        "appwrite.network",
        "imagine.diy"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "Certainly Intermediate R1",
    "subject": "appwrite.network",
    "protocol": "TLS 1.3",
    "valid_to": "2026-04-10T08:09:00Z",
    "valid_from": "2026-03-11T08:09:01Z"
}
Domain age days
122
Apex age days
122
Tls age days
7
Tls valid days
29
Requests
23
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "wetransfer",
            "genericemail"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "WeTransfer",
            "Generic Email"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "swoole-http-server",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "x-content-type-options": "nosniff"
}
Cloudflare Radar · 2026-03-18T10:43:26Z

Observed: · Retrieved:

Uuid
18256619-97cf-424c-9236-6d479386ba22
Final url
https://westandard.appwrite.network/
Status
200
History
[
    {
        "url": "https://westandard.appwrite.network/",
        "status": 200
    }
]
DOM structure hash
a19099b551854b7e8283adb7b2eb20a5cfd679bc558e7b33f737460f0f3bcf09
Document hash
397b51d4837443b5c18b2831ca2761e6488db4647d07de2d29b6281ffeec8f84
Phishing
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
DNS records
[
    {
        "name": "westandard.appwrite.network",
        "type": "CNAME",
        "value": "fastly.appwrite.systems"
    },
    {
        "name": "westandard.appwrite.network",
        "type": "CNAME",
        "value": "fastly.appwrite.systems"
    }
]
Dnssec valid
false
Ip
151.101.67.52
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2022-06-28T10:31:56Z",
    "updated": "2025-05-06T11:00:56Z",
    "expires": "2027-06-28T10:31:56Z",
    "nameservers": [
        "rosalyn.ns.cloudflare.com",
        "renan.ns.cloudflare.com"
    ]
}

Questions about westandard.appwrite.network

Is westandard.appwrite.network legit?

No. PhishDestroy classifies westandard.appwrite.network as a Wetransfer impersonation page (risk: critical, 100/100); it was first detected on 2026-03-18. VirusTotal: 10/91 engines flag it. Treat the site as unsafe.

Is westandard.appwrite.network safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on westandard.appwrite.network. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used westandard.appwrite.network?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Observed page title
WeTransfer
Automated brand references
Wetransfer
TLS Certificate
Issued by Certainly Intermediate R1

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Wetransferbrand: Genericemail report ↗
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Appwrite (Unknown)
Registration (base domain)appwrite.network · Created Jun 28, 2022 — Expires Jun 28, 2027
HTTP Status308 Permanent Redirect
Technical detailsProvenance & timestamps
First DetectedMar 18, 2026
DOM Analysisanalyzed Mar 24, 2026score 88/1001 brand signal
Submitted URLhttp://westandard.appwrite.network/
Favicon Hash
Case ID
ICANN OVERSIGHT Registration: appwrite.network

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain appwrite.network behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
2a04:4e42::820
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
San Francisco, US
Server header
swoole-http-server

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Certainly Intermediate R1
Valid from
2026-05-10 05:21:52
Valid until
2026-06-08 05:21:52
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate names · 4 SANs
  • *.appwrite.network
  • *.imagine.diy
  • appwrite.network
  • imagine.diy

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-23 10:48:29 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-23 10:48:29 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:48:29 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 8 identified
V
Varnish
Google Hosted Libraries
C
cdnjs
P
Popper
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 13 detections
alphaMountain.ai
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
Lionic
Sophos
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of westandard.appwrite.network · checked Mar 18, 2026

55
Needs Work
Performance
FCP
17.11s
First Contentful Paint
LCP
33.63s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
17.11s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

No cloaking flag in this check

redirect: raw=redirect_308; http=308; via=http_proxy; location=https://westandard.appwrite.network/; server=swoole-http-server

westandard.appwrite.network
Saved result
Cloaked / Filtered
Stored observation history23

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unavailable→Reachable

  3. Availability monitor · Recorded state

    Reachable→Unavailable

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unavailable→Reachable

Earlier observations 18
  1. Availability monitor · Recorded state

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  6. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  8. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  9. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  10. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  11. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  12. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  13. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  14. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  15. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  16. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  17. Availability monitor · Recorded state

    protected

    http_access_restricted · access_restriction

  18. VirusTotal · Detection count

    0→22

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    10/91 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Added to PhishDestroy

    westandard.appwrite.network

    View source
  5. Abuse report sent

    PD-20260318-A43E28

    abuse@fastly.com

Community reports

Reported by 1 community member, first seen Mar 18, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260318-A43E28 Recipient: abuse@fastly.com
Page title stored with report: WeTransfer
PDF notice generated Notice text archived (1,212 chars)
Abuse notice text as sent to the provider
Policy Violations:
Acceptable Use Policy (AUP): The domain westandard.appwrite.network is engaged in phishing activities, which directly contravenes the AUP's prohibition against illegal activities, fraud, and deception.
Terms of Service (TOS): The registrar reserves the right to suspend or terminate services for violations, and the use of this domain for phishing constitutes a clear violation of these terms.
Applicable Laws (Unknown):
Computer Fraud and Abuse Act (CFAA): This U.S. federal law prohibits unauthorized access to computers and networks, which is relevant given the phishing nature of the domain.
Wire Fraud Statute (18 U.S.C. § 1343): This law criminalizes schemes to defraud others through electronic communications, applicable to the fraudulent activities associated with this domain.
CAN-SPAM Act: This act regulates commercial email and prohibits misleading information, which is pertinent to the deceptive practices of phishing.
Regulatory Note: Failure to take immediate action against this domain may expose your organization to liability under applicable laws and could result in regulatory scrutiny. Compliance with your AUP and TOS is not only a best practice but a legal obligation.
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including westandard.appwrite.network)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/westandard.appwrite.network"
  title="PhishDestroy threat report for westandard.appwrite.network"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>