Is ionetp.pages.dev 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 is a project hosted as a subdomain on a free, shared web-publishing platform. Its address is a project-style name, with no standalone registered brand domain. The only page content captured was a short interstitial warning titled "Suspected Phishing", and it was served by the platform's security layer, not by the site's own pages. No storefront, product, service description, or business model could be identified from what the site presented, and its apparent purpose is unclear.

Scam/Impersonation Risk

Contradictory signals are present and are the decisive element of this assessment. The site is blacklisted by external threat-intelligence sources. Several independent detection engines classify it as malicious, and one further engine marks it suspicious. At least one of these is a major, established security vendor, so this is not an isolated low-confidence hit. The page the visitor receives is itself a phishing-suspicion warning, which is consistent with those external classifications. No conflicting legal entities or brand-impersonation claims were found, because there were no identity pages to compare. The listing alone is sufficient to treat the site as an elevated threat to credentials and funds. In the automated browsing sessions, no wallet-drainer behavior, clipboard manipulation, hidden forms, or credential posts to third-party hosts were observed. That is a limited mitigating observation, because the capture was stopped at a bot-challenge screen and did not reach any underlying application. The same sessions showed a very high share of traffic going to external hosts, heavy external background requests, and a high volume of script errors on the page. This is a noisy, unstable page whose real behavior cannot be confirmed. Evidence:

• Homepage: the captured page was titled as a suspected-phishing warning and was returned with an access-denied status behind a bot challenge.
• Multiple external detection engines flag the domain as malicious and one as suspicious, including a major security vendor, which produces the confirmed blacklist condition.
• Homepage behavioral sessions: about 95% of external traffic went to outside hosts, with 22 external background requests and 20 console errors across three successful runs.
• Behavioral sessions: no wallet connection, clipboard writes, hidden forms, or external password forms were detected.

Regulatory Verification Notes

No legal, terms, privacy, about, or contact pages could be assessed, because the only retrievable content was the warning interstitial. The evidence therefore contains no company name, licence, or registration number, and nothing ties the site to a regulated or identifiable operator. The domain sits under a shared hosting platform's subdomain space, so the address itself says nothing about who runs the site. No third-party broker or regulator-style record matches this site, which neither supports nor counts against it. The standard technical hygiene present is valid, but that does not establish who operates the site or that it is legitimate. Evidence:

• Homepage: a short warning page only, with no corporate, legal, or licensing disclosures observed.
• The site's transport encryption is a TLS certificate issued by WE1 (domain-validated, DV only), valid to 2027-01-02.
• The site is served from AS13335 (Cloudflare, Inc., US).

What to Verify Next

The practical priority is to establish how the link to this site was received. If it arrived through an unsolicited message, advertisement, or social post, the sender should be contacted through an independent, previously known channel to confirm it was sent deliberately. Any organization claiming to operate the site should be asked, through channels found independently of this site, to confirm that it controls this address and to supply its legal name and registration details, which can then be checked against the relevant public company or licensing registry. The official website of any brand this page might be imitating should be located through a search engine or a saved bookmark, and its address compared character by character with this one. Support and contact channels should be confirmed only through those independently located official sources. Evidence:

• Homepage: no operator name, registry number, or contact details are present to check.
• The address is a free-platform subdomain, so no brand-owned domain can be compared with it.
• The external warnings concern this exact address, so any claimed official channel must be located without using links from it.

Summary Verdict

The site presents an elevated risk posture. Confirmed external threat detections are the decisive factor, and technical hygiene or protective measures cannot offset them. No independent evidence of a legitimate, identifiable operator offsets those detections, so the site should be treated as a likely credential-theft or malware vector until proven otherwise.

Infrastructure Integrity

The site is delivered through a mainstream CDN and web application firewall, and all observed addresses are edge servers, with the origin server not visible. This is a mitigating factor only. It shows that the site is hosted on reputable commodity infrastructure and that the connection is encrypted, but it does not indicate who operates the content. It also means the hosting layer cannot be independently inspected and content could be changed quickly. It cannot offset the external threat detections.

Closing Assessment

Interaction with this site should be avoided. No credentials, personal data, payment details, or wallet connections should be entered, and nothing should be downloaded from it. If the link arrived unsolicited, it should be ignored and reported to the sender's platform or to the hosting provider's abuse channel. Anyone who has already entered credentials or payment details should change those passwords immediately and notify the relevant financial institution.