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

crypto-v7s.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-v7s.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 47%.

How the site describes itselfThe captured page shows only the text 'redirecting..' and no substantive content. The final destination could not be observed, so no service, offer, or identity can be assessed.

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 (47%) 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
Domain ageNot availableNo registration record was returnedNoted
Web archiveNever archivedNo public history of this siteWatch
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted

The page as captured

https://crypto-v7s.netlify.app/
Screenshot of the crypto-v7s.netlify.app homepage captured during the TrustSniffer assessment
What crypto-v7s.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.
  • 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

The address crypto-v7s.netlify.app is a subdomain on the free Netlify hosting platform, with a crypto-themed name. When captured on 20 October 2026, its homepage showed a single 13-character line of text reading "redirecting..", with no title, description, links, forms or visible offer. It presents no identifiable product, operator or business model. The page served only an interstitial placeholder, and its final destination was not observed.

Scam/Impersonation Risk: The negative finding is a threat listing against the site itself. A threat-intelligence feed lists this address as the actor in a phishing campaign, last seen on 18 October 2026, two days before the capture. The listing comes from a single source and is not a multi-source confirmation. It is not a confirmed blacklist. It is still the reason the score is held down at the threat-listing ceiling, and it places the site at critical risk. The analysis found no conflicting identities and no sign of impersonation of a named brand, but the site's real-world identity is unverified, so this absence of contradiction is not evidence of legitimacy. The domain sits under the platform's shared address space. Nothing observed indicates that the site is operated by Netlify itself. A redirect-only page is also a typical way to hide where a visitor ends up, so the lack of a visible destination offers no reassurance. One engine in the reputation panel rated the address suspicious and none rated it malicious. That is a weak signal on its own and is not treated as a detection. The page's behaviour during the three sandbox runs was uneventful: no forms, no login prompt, and no requests to other hosts. Those runs show only that the placeholder did nothing further. They do not show where the redirect leads.

Regulatory Verification Notes: On the page read, the homepage, no contact channels, terms or privacy statement, company name, licence or registration number were found. The business type could not be determined, so no sector-specific licensing expectation applies. Because the address is a free-platform subdomain, there is no registration record of its own to tie it to a named owner. No operator could be identified from the evidence, and that absence weighs on the score. No regulatory standing could be assessed. No third-party broker or regulator record matched this address, and that absence is neither a positive nor a negative signal. The transport certificate is organisation-validated in the hosting platform's name, so it identifies the platform, not whoever published this page.

What to Verify Next: The first step is to establish through an independent, offline route how the address reached the user, for example the sender of a message or advertisement, and whether that party confirms it. Any claim that it belongs to a particular company or service should be checked directly with that company through channels obtained independently of this site. If a page with real content, a licence claim or contact details later appears here, the licence should be checked at the issuing registry before any reliance on it. Nothing the site displays can serve as proof of identity.

Summary Verdict: The overall posture is one of critical risk. The site shows no demonstrable function or accountable operator, and a single-source threat-intelligence listing identifies it as a participant in phishing. The technical hygiene of its platform does not offset the listing.

Infrastructure Integrity: Four addresses were observed, all on Amazon's network and all at the edge. No origin server was identified. One negative signal is visible here and is not hidden: four abuse reports (confidence score 1, not whitelisted) were recorded against the IP address 2a05:d014:58f:6200::258. It is operated by Amazon Data Services Ireland Ltd and classed as a Content Delivery Network. The reports are attributed to shared infrastructure, because they apply to the shared provider IP and not to this site specifically. The signal was not discounted, so it stays on record, but it is not evidence of wrongdoing by this site. The presence of a CDN is treated as neutral, neither a mitigating factor nor a risk.

Closing Assessment: The address should not be visited, relied upon, or shared, and any message or advertisement that directed someone here should be treated as a possible phishing lure.

Evidence
  • Threat-intelligence listing: phishing class, the site as actor, last seen 2026-10-18; evidence captured 2026-10-20.
  • Reputation panel: 0 engines malicious and 1 suspicious.
  • Homepage: the only page read; it contained the text "redirecting.." and no forms, links or metadata.
  • Sandbox: 3 of 3 runs completed, with 0 external requests and 0 forms.
  • Homepage: contact channels and terms or privacy disclosures were missing on the page read.
  • TLS certificate: issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 (OV), subject organisation Netlify, Inc, valid to 2027-03-19.
  • Hosting: served from AS16509 (AMAZON-02, Amazon.com, Inc.).
  • Homepage: it offered no named operator, onward link or destination to check.
  • Page reading: only the root page was read, and the final redirect target was never observed.

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

What the analysis found

6 findings contributed to this verdict, raised by governance, page content, 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 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-v7s.netlify.app.

  • The request stayed on crypto-v7s.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)Not available (the web archive has no record of this address; a site on netlify.app has no registration of its own)
Domain expiryNot available
Archive first seenNot available
Archive snapshots0
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-v7s.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-v7s.netlify.app

Is crypto-v7s.netlify.app a scam?

TrustSniffer's assessment of crypto-v7s.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-v7s.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-v7s.netlify.app?

crypto-v7s.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