Is crypto-qbh.netlify.app a scam? 5/100

crypto-qbh.netlify.app

Is it safe to use? An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Download PDF Check another site How we score
Ask your AI about this report

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

Verdict

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

5 OUT OF 100
Critical Risk

crypto-qbh.netlify.app shows critical-risk indicators.

Sensitive Interaction Risk Governance Risk
  • Sensitive Interaction Risk: This label is given when the overall risk is high. The captured page did not ask for a password, card number or other sensitive details; if it ever does, entering them here could be unsafe.
  • Governance Risk: The governance checks raised a concern: a threat-intelligence listing limits the score; as a site on netlify.app, this address has no registration record of its own (the platform's domain is registered, not the site). The findings below give the detail.

Evidence captured 2026-10-20, re-scored 2026-11-15 by automated analysis. Evidence confidence 64%.

How the site describes itselfThe captured page contains only the text 'redirecting..' and no other content. No services, forms, links or identity signals are available for analysis.

Evidence status and limitations

Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.

  • The evidence was captured on 2026-10-20 and re-scored on 2026-11-15. The certificate, the registration age and the page content describe the site as it was on 2026-10-20.
  • One external source flagged this site when the evidence was captured (a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-18)). No second source confirms it. The alert is from the evidence captured on 2026-10-20; it was not re-queried for this version and is treated as unconfirmed. On its own the alert would limit the score to at most 49; the threat-listing ceiling holds it at 5, because the listing names the site itself as the source.
  • The real-world operator identity was not independently verified.

How to read these numbers

The trust score runs from 0 to 100, higher is safer. 5/100 rates the evidence found, not the probability that the site is a scam.

Evidence confidence (64%) measures how much of TrustSniffer's evidence set this site produced: the page reading, the browser sandbox, the web archive, the registration record and the reputation services. It falls when a check returns nothing, as listed above, and it does not change the score.

At a glance

The checks that decide most of this verdict.

What limits the scoreThreat-listing ceilingA threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-18), and that listing caps the score. The unconfirmed alert ceiling (at most 49) also applies, but the score is below it.Risk
Malware enginesNone malicious; 1 marked it suspiciousVirusTotalWatch
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address1% confidenceAbuseIPDB, 4 reports; shared hosting inflates reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
First seen1 month before captureWeb archive; a site on netlify.app has no registration of its ownRisk
Web archive1 snapshot1 snapshot; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted

The page as captured

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

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • First seen: less than 1 year before capture (web archive; a site on netlify.app has no registration of its own).
  • No security engine marked this domain as malicious and Google Safe Browsing does not list it; some engines marked it suspicious, which TrustSniffer does not count as a listing. Its hosting IP carries AbuseIPDB reports below the confidence level TrustSniffer treats as a flag.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Overview

This website is a subdomain on Netlify's free hosting platform. When captured, its homepage showed a single line of text, "redirecting..", and nothing else: no title, services, products, forms, links or described business. It reads as a redirect placeholder, so its purpose and business model cannot be determined from what it presented. It was captured on 20 October 2026.

Scam/Impersonation Risk

The most serious finding is that a threat-intelligence feed listed this address as distributing phishing, and the listing was last seen on 18 October 2026, two days before capture. The listing names the site itself as the actor, not as a victim. That places the address at critical risk. It is a single-source alert, and the score is held down by the threat-listing ceiling. One security engine rated the address suspicious and none rated it malicious. That is not a detection, but it points the same way as the feed listing. No brand impersonation or conflicting legal identities were observed. The address is a tenant name on Netlify's platform, and the site is not Netlify. The page's only content is a redirect message, so a visitor could be sent to a destination that was not captured and cannot be assessed. Behavioural testing showed no cross-site requests, forms, hidden forms or wallet interactions, but that testing covered only the placeholder page and says nothing about wherever the redirect leads.

Evidence
  • Threat-intelligence feed: the address was listed as a phishing distributor, role "actor", last seen 18 October 2026.
  • VirusTotal: 1 engine rated the address suspicious and 0 rated it malicious. No Google Safe Browsing listing was found.
  • Homepage: the only visible text is "redirecting..", with no forms, login fields or links.
  • Archive and registration record: the address was first seen about 43 days before capture, with a single web-archive snapshot recorded.

Regulatory Verification Notes

The homepage is the only page that was read. On that page, no contact channel and no terms or privacy statement were found. These are the disclosures expected of any site, and without them the operator cannot be tied to any person or business. No licence, registration number or regulatory claim appears on the page either. Because the address sits on a free platform subdomain, the site has no domain registration of its own to examine, and the real-world identity behind it remains unverified. The transport-encryption certificate belongs to the hosting platform, not to the site's operator, so it says nothing about who runs the site. No third-party broker or regulator record was matched.

Evidence
  • Homepage, the only page read: no contact channels and no terms or privacy statement were found on it.
  • Hosting: the site is served from AS16509 (AMAZON-02, Amazon.com, Inc.).
  • Transport encryption: the certificate was issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 at organisation-validated level to Netlify, Inc, and was valid to 19 March 2027.
  • Address: a free-platform subdomain, so the registration record identifies no operator.

What to Verify Next

Nothing on the page supports further engagement with the site. If the address reached a visitor by message, advertisement or search result, the origin of that link is the more useful thing to check, along with whether the sender expected it to lead to a redirect page. If a business or brand is claimed in that context, its official website should be located through an independent route and compared with this address. A genuine operator would be expected to publish contact details and terms on a domain of its own. Any later capture of the redirect destination should be assessed separately, since this analysis did not observe it.

Evidence
  • Homepage: the redirect message gave no destination, no named business and no claim to verify.
  • Page structure: no outbound links, forms or social profiles were present to trace.
  • Address: the Netlify tenant name carries no operator identity.

Summary Verdict

The site is assessed as critical risk, and the posture is firmly negative. The score is held down by the threat-listing ceiling. The page offered no content, identity or disclosures that could support any positive reading, and its operator is unidentified.

Infrastructure Integrity

The site is delivered through AWS content-delivery infrastructure on four edge addresses, and no origin server address was observed. Four abuse reports exist for one of those edge addresses, which is a shared provider address. They are attributed to the shared infrastructure, not to this site specifically, and are noted only as context. The use of a content-delivery network is neutral and does not support or weaken the assessment.

Closing Assessment

The site should not be treated as legitimate. A visitor should not follow its redirect or interact with it further. If the link arrived through an unsolicited message, that message should be treated as suspect and reported to the party it claimed to come from.

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

What the analysis found

8 findings contributed to this verdict, raised by governance, page content, hosting and network, history in the web archive, and registration and ownership.

01 Governance

  • A threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-18), and that listing caps the score.Governance rule:gov_active_threat_listing

02 Page content

  • The page loaded on its own domain but had no readable content.Page content rule:PAGE_CONTENT_EMPTY
  • The page runs on a free hosting-platform address instead of a domain of its own, a setup common to short-lived phishing and claim pages.Page content rule:PAGE_FREE_PLATFORM_ADDRESS
  • The page has no title, which almost every website sets.Page content rule:PAGE_TITLE_MISSING
  • The browser raised a warning while loading the page.Page content rule:PAGE_BROWSER_FLAGS_SUSPICIOUS

03 Hosting and network

  • The domain was registered, or a site on a hosting platform was first seen, less than three months before capture.Hosting and network rule:DNS_NEW_DOMAIN_90D

04 History in the web archive

  • The web archive has almost no record of this domain, which fits a site that is new.History in the web archive rule:ARCH_PEN_YOUNG_AND_SPARSE

05 Registration and ownership

  • As a site on netlify.app, this address has no registration record of its own (the platform's domain is registered, not the site).Registration and ownership rule:KF_WHOIS_INCOMPLETE

How related findings were counted

Some findings above describe the same underlying fact, and some are weak on their own. TrustSniffer counts each such group under one shared limit, so one fact is not counted several times and weak signals stay bounded.

  • Page quality: 2 findings share one limit, because each is weak evidence on its own. Together they stayed under the limit.

Noted, not counted

Recorded during the assessment, but not counted against the site.

  • AbuseIPDB: 4 reports on hosting IP 2a05:d014:58f:6200::258 (AMAZON-02), 1% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

Identity verification

StatusUNVERIFIED

The operator behind the site could not be connected to a real-world brand or person. What the page shows, if anything, is listed below; none of it was independently checked.

  • No contact detail, company registration number or linked social profile was extracted from the page for checking. Any operator the page names in its own words (see how the site describes itself, above) is not verified here.

What TrustSniffer observed

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

  • The request stayed on crypto-qbh.netlify.app. It was not redirected to another domain. Clear
  • It is hosted on AMAZON-02, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingAMAZON-02 - Amazon.com, Inc.
Network registered inUS
Server IP2a05:d014:58f:6200::258 (a CDN edge address; the server behind it was not observed)
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
First seen (web archive)44 days before capture; a site on netlify.app has no registration of its own
Domain expiryNot available
Archive first seenNot available
Archive snapshots1
ReputationVirusTotal: 0 malicious, 1 suspicious | AbuseIPDB (CDN edge address, not the host): 1% confidence, 4 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about crypto-qbh.netlify.app at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A high score means the signals were consistent with a legitimately operated site; a low or critical score means several risk patterns were present. It is a starting point for your own judgement, 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 crypto-qbh.netlify.app

Is crypto-qbh.netlify.app a scam?

TrustSniffer's assessment of crypto-qbh.netlify.app found strong scam indicators. It scored 5 out of 100 on 2026-11-15, which is the critical-risk band. The specific signals are listed in the evidence above.

Is crypto-qbh.netlify.app safe to use?

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

What is the trust score of crypto-qbh.netlify.app?

crypto-qbh.netlify.app scored 5 out of 100 on 2026-11-15, 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.
Questions about this report? Ask your AI

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-11-15 · how we assess · report a mistake