Verdict
The site blocked our scan, so nothing was confirmed either way. Treat it as unknown and verify who runs it another way.
crypto-qfm.netlify.app blocked our automated scan and could not be verified.
- Needs Review: The site blocked or cut short the capture, so no verdict was reached.
| How the site describes itself | Autogenerated Netlify 404 'Site not found' page indicating a missing or broken link. No forms, no credential requests, and no active monetization present. |
|---|
Evidence status and limitations
Evidence completeness: IncompleteThis says whether every check on the site was recorded as finished. The site blocked or cut short our capture, so the result needs review.
- Capture was incomplete or blocked; this result requires review.
- The real-world operator identity was not independently verified.
At a glance
The checks that decide most of this verdict.
| Malware engines | None flagged itVirusTotal | Clear |
|---|---|---|
| Google Safe Browsing | Not listedGoogle | Clear |
| Abuse reports on the CDN edge address | 1% 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 observed | Noted |
| Domain age | Not availableNo registration record was returned | Noted |
| Web archive | Never archivedNo public history of this site | Watch |
| Certificate | Encrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 | Noted |
The page as captured
Key findings
- The site blocked automated access, so TrustSniffer could not collect enough evidence to assign a score.
Full analysis
Overview
This website is an autogenerated Netlify “Site not found” page presented as a hosting error rather than an operating commercial service. It informs visitors that the requested path is missing, provides Netlify deployment guidance, and contains no visible transaction, credential-collection, or monetization workflow.
Scam/Impersonation Risk
No confirmed phishing, impersonation, malicious-content, or other contradiction was observed. The captured page is consistent with a legitimate Netlify error response and does not solicit credentials or money. However, behavioral testing recorded hidden forms and password-form signals across repeated runs, together with substantial post-interaction page changes; these findings warrant clarification even though the visible page contained no corresponding active form. Four abuse reports were associated with a shared Amazon content-delivery IP rather than specifically attributed to the website, so that signal is reputational context rather than evidence of site-level abuse. Overall, the site presents an established-looking hosting error surface, but the real-world operator identity remains unverified.
- The homepage capture returned a Netlify “Site not found” page with no visible forms, credential requests, or monetization.
- Behavioral testing recorded hidden forms in 3 of 3 runs, password-form signals in 3 runs, and a maximum post-interaction DOM difference of 4,132 changes.
- External reputation data recorded 4 abuse reports against shared Amazon CDN infrastructure; the attribution identified the shared provider IP as the subject rather than the website operator.
Regulatory Verification Notes
The available page does not provide an operating-company identity, legal terms, licensing statement, or service-specific regulatory disclosure. Because the captured content is only a hosting error page, this is a verification gap rather than evidence of a deceptive financial or commercial operation. The transport and hosting indicators are technically credible: the site resolves through Amazon infrastructure and presents an Organization Validated certificate issued to Netlify, Inc. These signals support the conclusion that the page is hosted on established infrastructure, but they do not independently establish who controls the specific subdomain.
- The site is served from AS16509, Amazon-02 — Amazon.com, Inc., US.
- The TLS certificate uses OV validation, was issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1, identifies Netlify, Inc. as the subject organization, and is valid to 2027-03-19.
- The captured page contains no company, licensing, terms, or regulated-service disclosure.
What to Verify Next
Before any credential or payment interaction, independently confirm the intended operator through an official, separately sourced channel and ensure that the destination presents consistent legal, support, refund, and payment-protection information. If the page is expected to host a live service, the responsible operator should also confirm that the missing path has been restored and that any forms observed during testing are intentional and securely implemented.
- The requested path produced an error page rather than an identifiable operating service.
- No live account, payment, support, or contractual workflow was available for independent review.
- The observed behavioral form signals should be reconciled against the intended production deployment before sensitive interaction.
Summary Verdict
The available evidence is consistent with an established, apparently legitimate hosting endpoint, and no scam or impersonation contradiction was observed. The appropriate posture is needs review because the captured content does not independently connect the endpoint to a verified real-world operator and behavioral findings are not fully explained.
Infrastructure Integrity
The site is protected by AWS and Cloudflare CDN/WAF infrastructure, with observed traffic terminating on CDN edge servers and no origin candidate identified in the analysis. This layered hosting arrangement reduces direct origin exposure and is a mitigating technical control, but it is not proof of operator legitimacy.
Closing Assessment
Ordinary independent identity, service, return-policy, and payment-protection checks should be completed before credentials or funds are committed.
Written analysis generated 2026-10-19 by the TrustSniffer Analysis Engine from the evidence in this report.
What the analysis found
6 findings contributed to this verdict, raised by behaviour in a sandbox.
01 Behaviour in a sandbox
- The page contained a form a visitor cannot see.Behaviour in a sandbox
rule:BEHAV_HIDDEN_FORMS - The page contained a form a visitor cannot see in more than one sandbox session.Behaviour in a sandbox
rule:BEHAV_HIDDEN_FORMS_REPEAT - Most of the files the page loaded (scripts, images, fonts) came from other domains. This is about where its content is hosted, not about data being sent elsewhere.Behaviour in a sandbox
rule:BEHAV_EXTERNAL_RATIO_HIGH - The page replaced a large part of its own content during the sandbox session.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 - The structure of the page changed sharply during the sandbox session.Behaviour in a sandbox
rule:BEHAV_DOM_DENSITY_SPIKE
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
| Status | UNVERIFIED |
|---|
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-qfm.netlify.app.
- The request stayed on crypto-qfm.netlify.app. It was not redirected to another domain. Clear
- It is hosted on AMAZON-02, a network registered in US. Noted
Domain intelligence
| Registrar | Not available |
|---|---|
| Hosting | AMAZON-02 - Amazon.com, Inc. |
| Network registered in | US |
| Server IP | 2a05:d014:58f:6200::258 (a CDN edge address; the server behind it was not observed) |
| Name servers | Not available |
| CDN / edge network | Detected (aws, cloudflare) |
| Resolved IP addresses | 8 |
| Edge IP addresses | 8 |
| Likely origin IP addresses | 0 |
| SSL issuer | DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
| SSL expiry | 2027-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 expiry | Not available |
| Archive first seen | Not available |
| Archive snapshots | 0 |
| Reputation | VirusTotal: 0 malicious | 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-qfm.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.