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

Security Alert

Fortinet flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

This website, served from the domain app-jtx.trade, could not be viewed as ordinary content during analysis. A security challenge page labelled as a suspected phishing site was returned in place of the homepage, so the site's products and claims could not be observed. The "app" naming and the ".trade" suffix suggest a login-oriented trading or financial application portal, but the evidence does not establish this. The site's business model, operator and purpose remain unconfirmed.

Scam/Impersonation Risk

Contradictory signals are present and are the decisive element of this assessment. The domain is currently blacklisted. Several independent security engines return malicious or suspicious verdicts, including a tier-one security vendor, and the aggregated external reputation check confirms the listing. The homepage request was also intercepted by the hosting provider's own challenge page, titled as a suspected phishing site. This is consistent with the external detections and indicates the site is being treated as hazardous at the network edge. No brand impersonation or conflicting legal identities were established, because no page content could be captured. The absence of that evidence does not mitigate the active blacklisting. Behavioural testing showed a high share of traffic going to external destinations, with many background requests and form submissions leaving the site. All of these went to recognised, whitelisted endpoints. No wallet-connection prompts, clipboard manipulation, hidden forms or external password forms were observed. These observations do not offset the reputational listing. A very recently registered domain, combined with active threat detections, matches the profile of short-lived infrastructure used for phishing or fraud campaigns. Evidence:

• Homepage: access was met with a bot-protection challenge (HTTP 403) titled "Suspected Phishing", so no site content was retrievable.
• External reputation: malicious and suspicious verdicts from multiple engines, including tier-one vendor Fortinet, and a confirmed external blacklist hit.
• Domain provenance: registered 2026-07-13 (~0.29 years, ~105 days old).
• Web archive: 1 snapshot, captured 2026-07-29, with 1 year tracked and no prior history.
• Behavioural sandbox: 25 external XHR calls, 9 external POST requests and 20 console errors across 3 runs, with no wallet-drainer, clipboard or hidden-form activity.

Regulatory Verification Notes

No licensing, registration or regulatory standing could be tied to this site. No third-party broker or regulatory record matches the domain, and the real-world operator is not independently identified. Because no page content was captured, the legal and identity pages could not be assessed, so no entity name or licence claim is available to test. The domain was registered through a commercial registrar with the owner details redacted. This is treated as an administrative detail and not as an identity contradiction. The valid transport encryption is a basic hygiene measure and carries no weight as evidence of legitimacy. Any later claim of financial or trading authorisation by this domain should be treated as unsubstantiated until confirmed with the named regulator. Evidence:

• Registration: registrar NICENIC INTERNATIONAL GROUP CO., LIMITED, owner redacted for privacy, registration expiring 2027-07-13.
• Transport encryption: TLS certificate issued by WE1 (DV, domain-validated only), valid to 2026-12-10.
• Hosting: served from AS13335 (CLOUDFLARENET, Cloudflare, Inc., US).
• No third-party broker or regulator record matched the domain.

What to Verify Next

Anyone who reached this site through an advertisement, message or referral should trace that source and treat it as potentially hostile. If the site claims to represent a known brand or licensed firm, the official domain should be confirmed through an independent route: the brand's own published materials, a regulator's public register, or a previously known contact channel. Any licence or registration number the site asserts should be looked up directly in the relevant registry, never through links on the site itself. Support or contact channels should be confirmed offline before any dealings. Anyone who has already entered credentials or sent funds should change those credentials from a clean device and contact their bank or payment provider. Evidence:

• Homepage: only a challenge interstitial was served, so no site-supplied identity or licence claims exist to cross-check.
• Domain history: a registration date of 2026-07-13 and a single archive snapshot from 2026-07-29 leave no established record to rely on.
• External listing: the confirmed blacklist hit and malicious verdicts mean any referral link should be treated as hostile.

Summary Verdict

The overall posture is critical-risk and clearly cautionary. Active external threat detections, a very young domain with no meaningful history and no independently verified operator converge on a site unsuitable for any sensitive interaction. Technical hygiene and the absence of observed wallet or clipboard abuse do not change this conclusion.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF. All four observed addresses (two IPv4 and two IPv6) are Cloudflare edge servers in the US, and the origin server is not observable. This is a mitigating factor only. It limits direct exposure of the origin, but edge-only visibility prevents independent verification of the real hosting and can mask rapid content swaps. It cannot offset the reputational risk from the external threat detections.

Closing Assessment

The site should be treated as unsafe for any login, credential entry, payment or financial activity. At most it should be viewed passively, from an isolated, non-sensitive environment. No wallet connections, downloads or personal data submissions should be made. It is appropriate to report the domain to the relevant bank, platform or anti-phishing channel if it was received through an unsolicited contact.