Verdict
This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.
crypto-oht.netlify.app shows high-risk / scam indicators.
| What this site appears to be | Netlify-hosted 404 page indicating the requested site/path was not found, with a suggestion to visit Netlify support and to start building a site. |
|---|
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 engines | 2 flagged itVirusTotal | Risk |
|---|---|---|
| Google Safe Browsing | Not listedGoogle | Clear |
| Abuse reports on the host | 1% confidenceAbuseIPDB, 4 reports; shared hosting inflates reports | Clear |
| Domain age | 15 days oldMost scam domains are under a year old | Risk |
| Web archive | Archived since 20261 snapshot | Clear |
| Certificate | Encrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 | Noted |
The page as captured
Key findings
- Automated classification: Sensitive Interaction Risk.
- Domain age: less than 1 year (registration continuity).
- Public web-archive history exists since 2026.
- At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.
Full analysis
Overview
The website currently presents a Netlify “Site not found” page for a domain using a cryptocurrency-themed name, directing visitors to Netlify support and site-building guidance rather than offering an identifiable business, product, or financial service.
Scam/Impersonation Risk
The site presents a critical interaction risk. External reputation evidence records a confirmed blacklist hit and malicious detections, which are decisive contradictions despite the captured page being a benign-looking 404 page with no visible login or payment function. Behavioral testing also detected hidden forms across all observed runs and substantial post-interaction page changes. Four abuse reports were associated with a shared content-delivery IP rather than uniquely attributed to the site, so that signal is contextual; it does not, however, offset the confirmed blacklist status. No conflicting legal-entity names or direct brand impersonation were observed in the supplied page content.
- The homepage returned HTTP 404 content stating “Site not found” and provided Netlify troubleshooting and site-building guidance.
- External reputation checks recorded a blacklist hit, with 2 malicious and 1 suspicious detections.
- Behavioral testing detected hidden forms in 3 of 3 runs and a maximum post-interaction DOM difference of 4,132 elements.
- The domain was first observed in 2026 and is approximately 0.04 years old; archival coverage consists of 1 snapshot spanning 2026–2026, with 1 year tracked.
Regulatory Verification Notes
The captured site does not provide an identifiable operator, legal entity, licensing statement, registration number, terms, privacy disclosure, or regulated-service explanation. This is a material transparency gap for any site that might later request credentials, funds, or other sensitive information, while the operator’s real-world identity remains unverified. The available broker-context check produced no match, but that does not establish licensing or regulatory standing. The transport certificate is technically valid and organization-validated, but certificate issuance confirms encrypted transport, not the legitimacy of the operator or its activities.
- The only captured page is a 404/error page and contains no business identity, license disclosure, registration number, or customer-facing legal terms.
- The site is served from AS16509, Amazon.com, Inc. (AMAZON-02), United States.
- The TLS certificate is Organization Validation, issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1, with subject organization Netlify, Inc., valid through 2027-03-19.
- No broker-dataset match was identified; this is reputational context only and is not a regulatory determination.
What to Verify Next
Before any sensitive interaction, an independent party should confirm that the domain is intentionally operated by a known organization through an offline or independently sourced contact route, and should confirm any claimed authorization directly with the relevant financial or digital-asset regulator. The blacklist detections should be independently resolved and documented before the domain is permitted into an enterprise allowlist. Until those checks are complete, activity should remain limited to passive observation, with no credential submission, authentication, downloads, or financial transfer.
- The site’s captured content does not identify an operator or provide a verifiable regulatory reference.
- The domain has only 1 recorded archive snapshot and is approximately 14 days old according to the available registration-continuity evidence.
- The observed page contains no visible login or payment workflow, while separate behavioral testing detected hidden forms.
Summary Verdict
The overall posture is critical and unsuitable for sensitive interaction. The available evidence does not independently establish a legitimate real-world operator, and the external threat contradictions outweigh the otherwise ordinary hosting and transport characteristics. The site should not be treated as an approved destination for account access, credentials, downloads, or financial activity.
Infrastructure Integrity
The site is protected by AWS CDN/WAF infrastructure, and all observed addresses were CDN edge addresses; no origin server address was identified in the analysis. This provides a mitigating layer against direct origin exposure and can support operational resilience, but it does not validate the site’s operator or neutralize the external reputation findings.
Closing Assessment
Enterprise controls should block sensitive interaction with the domain pending independent identity, regulatory, and reputation-remediation confirmation; any subsequent approval should require documented security review and monitoring.
Written analysis generated 2026-10-19 by the TrustSniffer Analysis Engine from the evidence in this report.
What the analysis found
5 findings contributed to this verdict, raised by external reputation, behaviour in a sandbox, hosting and network, history in the web archive, page content.
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
03 Hosting and network
- The domain was registered less than three months ago.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 Page content
- The page appears to present itself as a known brand it is not verified to belong to.Page content
rule:PAGE_BRAND_SUSPECTED
Signals weighed against the site
- AbuseIPDB: 4 reports on hosting IP 2a05:d014:58f:6200::258 (Amazon Data Services Ireland Ltd, Content Delivery Network), 1% confidence. The reports are attributed to shared infrastructure, not specifically to this website.
Identity verification
| Status | UNVERIFIED |
|---|---|
| Identity score | 30/100 |
| Identity verification confidence | 50% |
- No on-site identity signals detected
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 crypto-oht.netlify.app.
- The request stayed on crypto-oht.netlify.app. It was not redirected to another domain. Clear
- The earliest public archive of this site is from 2026-10-05. Clear
- It is hosted on AMAZON-02, from a server in US. Noted
Domain intelligence
| Registrar | Not available |
|---|---|
| Hosting | AMAZON-02 - Amazon.com, Inc., US |
| Country | US |
| Server IP | 2a05:d014:58f:6200::258 |
| Name servers | Not available |
| CDN / edge network | Detected (aws) |
| Resolved IP addresses | 4 |
| Edge IP addresses | 4 |
| Likely origin IP addresses | 0 |
| SSL issuer | DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
| SSL expiry | 2027-03-19 |
| Domain age | 0.04 years (continuous registration) |
| Domain expiry | Not available |
| Archive first seen | 2026-10-05 |
| Archive snapshots | 1 |
| Reputation | VirusTotal: 2 flagged | AbuseIPDB: 1% confidence, 4 reports | Google Safe Browsing: 0 matches |
About this assessment
A trust score summarises the evidence TrustSniffer could collect about crypto-oht.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.