Is donutclientss.netlify.app a scam? TrustSniffer's high-risk assessment: 0/100

donutclientss.netlify.app
Download PDF Check another site How we score

Verdict

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

0 OUT OF 100
Critical Risk

donutclientss.netlify.app shows high-risk / scam indicators.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-22 by automated analysis. Classification confidence 55%.

Evidence status and limitations

Evidence completeness: Not recorded

  • The real-world operator identity was not independently verified.
  • Module-level completeness metadata is unavailable for this legacy report.

At a glance

The checks that decide most of this verdict.

Malware engines2 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 2 reports; shared hosting inflates reportsClear
Domain ageNot availableNo registration record was returnedNoted
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted
Hosted byAMAZON-02Server in USNoted

The page as captured

https://donutclientss.netlify.app/
Screenshot of the donutclientss.netlify.app homepage captured during the TrustSniffer assessment
What donutclientss.netlify.app served when TrustSniffer captured it on 2026-10-22. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.

Full analysis

Overview

The captured homepage of this Netlify-hosted subdomain is a generic "Site not found" error page with only a few hundred characters of text. It shows no products, brand, services or business model. The address resolves to a free-form subdomain on a shared static-hosting platform, and no operator or commercial purpose can be read from what the page shows. Its apparent purpose is therefore indeterminate.

Scam/Impersonation Risk

The evidence contains confirmed adverse reputation signals. Several independent threat-intelligence engines classify the domain as malicious or suspicious, and it also carries an external blacklist listing. These are the decisive findings, and they support a clearly cautionary posture. No brand impersonation, conflicting legal identities or confirmed phishing page were observed. The page content supplied nothing to examine for those, because it is an error page. Automated browser sessions did show behavior that does not fit a dormant error page. Hidden form elements, including password-type fields, were present in every session. The page also produced very heavy DOM rewriting after interaction, and almost all network activity went to external destinations. Wallet-connection prompts, clipboard tampering, fingerprinting and content cloaking were not observed. A hosted subdomain that carries concealed credential-capture-capable forms behind a "not found" front, and is already listed by threat-intelligence sources, matches a staging or credential-harvesting pattern. This is an inference from the behavior, not a confirmed phishing finding. Two abuse reports were also recorded against a provider-operated address in the same hosting range. They are discounted, since they relate to shared provider infrastructure and are not attributable to this site. Evidence:

  • Homepage: the captured page returned a "Site not found" error with minimal text, so no product, brand or identity claims could be assessed.
  • Behavioral sessions: hidden forms were detected in 3 of 3 runs, with 3 password-type forms, 21 outbound POST requests, and up to 99.6% of requests going to external hosts.
  • Behavioral sessions: 4,130 DOM mutations followed interaction on the otherwise near-empty page.
  • Reputation sources: 2 engines rated the domain malicious and 1 suspicious, alongside an external blacklist hit. The 2 abuse reports relate to a shared provider address and are discounted.

Regulatory Verification Notes

No legal, terms, privacy or about content was available on the captured page. No licence, registration number or corporate entity is therefore disclosed, and the site cannot be linked to any real-world organisation. That alone would be a verification gap rather than proof of wrongdoing, but here it coincides with the adverse reputation findings above. The TLS certificate is organisation-validated, but its subject is the hosting platform and not the site's operator. It confirms encrypted transport and says nothing about who runs the site. No broker-reputation record was matched, and no third-party regulatory standing was established. Evidence:

  • Homepage: no company name, licence, registration number or legal documentation appeared on the captured page.
  • Transport encryption: the certificate was issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 (OV), names Netlify, Inc as subject, and is valid to 2027-03-19.
  • Hosting: the site is served from AS16509 (AMAZON-02, Amazon.com, Inc., US).

What to Verify Next

Any contact with this address should start from an independently sourced route to the supposed operator. Confirm through a separately known, offline channel whether the organisation or person behind this subdomain exists. Check with the hosting platform's abuse process whether the deployment is a known project or has been reported. Re-test the address after the owner has had a chance to remove the hidden forms and the reputation listings. Any official support or contact details should be taken from an authoritative source outside this site. Evidence:

  • Homepage: the error page offers no verifiable operator, so independent identification is the only available route.
  • Behavioral sessions: the hidden password-type forms reappeared in every run, so a single clean re-test would not be conclusive.
  • Reputation sources: the listings are current and would need to be delisted before the address can be reassessed.

Summary Verdict

Available evidence places this site in an elevated-risk category. Confirmed negative reputation findings and concealed credential-capable form behavior outweigh the technical hygiene signals, and no real-world operator identity could be established. The site should be treated as unsafe for any sensitive interaction.

Infrastructure Integrity

The site is delivered through Amazon-operated edge infrastructure, and the observed addresses are all provider edge servers. The origin server was not observable. This is protective, mainstream infrastructure and a mild mitigating factor, but it is shared and gives no assurance about the site's operator. It cannot offset the reputation findings, and edge-only visibility can mask rapid content changes behind the same address.

Closing Assessment

Limit interaction to passive viewing at most. Do not enter credentials, log in or make any payment or financial transaction on this site until the operator has been independently identified and the threat-intelligence listings have been cleared.

Written analysis generated 2026-10-22 by the TrustSniffer Analysis Engine from the evidence in this report.

What the analysis found

2 findings contributed to this verdict, raised by external reputation, behaviour in a sandbox.

01 External reputation

  • Several malware engines flagged this domain.External reputation rule:EXT_BLACKLIST_HIGH

02 Behaviour in a sandbox

  • The page contained a form a visitor cannot see.Behaviour in a sandbox rule:BEHAV_HIDDEN_FORMS
  • Most of what the page loaded came from other domains rather than from this one.Behaviour in a sandbox rule:BEHAV_EXTERNAL_RATIO_HIGH
  • The page replaced a large part of its own content after loading.Behaviour in a sandbox rule:BEHAV_DOM_CHANGE_HIGH
  • The page rewrote itself after it was interacted with, so what a visitor first sees is not what they end up on.Behaviour in a sandbox rule:BEHAV_DOM_DIFF_AFTER_INTERACTION

Signals weighed against the site

  • AbuseIPDB: 2 reports on hosting IP 2a05:d014:58f:6200::259 (Amazon Data Services Ireland Ltd, Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

Identity verification

StatusUNKNOWN
Identity score50/100
Identity verification confidence30%
  • AI page analysis unavailable (page captured; identity not AI-verified)

Identity verification measures whether the site can be independently connected to a real-world brand or person. It is separate from the classification confidence.

What TrustSniffer observed

First-party facts recorded during the assessment of donutclientss.netlify.app.

  • The request stayed on donutclientss.netlify.app. It was not redirected to another domain. Clear
  • It is hosted on AMAZON-02, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingAMAZON-02 - Amazon.com, Inc., US
CountryUS
Server IP2a05:d014:58f:6200::259
Name serversNot available
CDN / edge networkDetected (aws)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerDigiCert Global G2 TLS RSA SHA256 2020 CA1
SSL expiry2027-03-19
Domain ageNot available (no registration date was returned)
Domain expiryNot available
Archive first seenNot available
Archive snapshotsNot counted (archive lookup incomplete)
ReputationVirusTotal: 2 flagged | AbuseIPDB: 0% confidence, 2 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about donutclientss.netlify.app at assessment time. It is a starting point for your own judgement, not a guarantee: a high score means the signals were consistent with a legitimately operated site, a low or critical score means several risk patterns were present.

TrustSniffer assesses a website from the evidence it can collect at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A score is a summary of that evidence, not a guarantee and not a legal finding. There is no human rating and no user review in it. A site can change after it is assessed.

Already paid or signed in? Do this now

Act fast. The sooner your bank knows, the better the chance of stopping the payment.

  1. Call your bank or card company now. Use the number on the back of your card. Ask them to stop or reverse the payment.
  2. Paid with crypto? Contact the exchange or wallet app you sent it from today. Give them the address you paid.
  3. Signed in or shared a password? Change it now, on every site where you use it, and turn on two-step sign-in.
  4. Report it to the police. In the US you can also report at reportfraud.ftc.gov and ic3.gov. In other countries, use your national police or fraud reporting service.
  5. Keep the evidence. Save screenshots, receipts, emails and chat messages. Your bank and the police will ask for them.
  6. Ignore anyone who offers to get your money back for a fee. These "recovery" offers are often a second scam.

Looking for the real site? Type the company name into a search engine yourself, or use the web address printed on your card, bill or letter. Do not use links from messages or ads.

Common questions about donutclientss.netlify.app

Is donutclientss.netlify.app a scam?

TrustSniffer's assessment of donutclientss.netlify.app found strong scam indicators. It scored 0 out of 100 on 2026-10-22, which is the critical-risk band. The specific signals are listed in the evidence above.

Is donutclientss.netlify.app safe to use?

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

What is the trust score of donutclientss.netlify.app?

donutclientss.netlify.app scored 0 out of 100 on 2026-10-22, which places it in the critical-risk band. The score is built from the domain's age and registration history, its hosting and certificate, the content of the site itself, and third-party reputation data. There is no human rating and no user review in it.

Download this report as PDF Free, no account needed. Create one to keep a history of the sites you check.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-22 · how we assess · report a mistake