Is portal-moonshot-83r.netlify.app safe? TrustSniffer's low-trust assessment: 25/100

Security Alert

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

This website is a subdomain on a shared static-hosting platform that currently returns only the platform's standard "Site not found" error screen. The page shows a generic broken-link message, a platform support reference and a prompt to start building a site. It names no product, service, organization or monetization model, and its apparent purpose as a "portal" can only be inferred from the host name. No legitimate business function is visible.

Scam/Impersonation Risk

Confirmed adverse contradictions are present. Multiple independent security engines classify the address as malicious or suspicious, and it also appears on an external blacklist. This is the decisive finding. The visible page is only a hosting-platform error, so the flagged behavior cannot be traced to any content the visitor can see. The page also looks nothing like the behavior recorded behind it. Across all three sandbox sessions, hidden form structures and password-type inputs were detected on a page that visibly shows no forms. The page also underwent very heavy structural change after interaction, which points to scripted content being injected or swapped. This pattern matches credential-harvesting staging, where a benign-looking shell hides a form or kit that is activated selectively. It is not confirmed phishing. The host name is a lookalike of the hosting platform's own domain. The page analysis does not treat this as active brand impersonation, and no conflicting legal identities exist. The abuse reports on one of the addresses serving the site apply to a shared provider address. They are therefore weaker evidence than the blacklist and detection findings, and they are not discounted. Taken together, the evidence calls for a clearly cautionary posture toward any login or financial interaction. Evidence:

• Homepage: shows only the platform's "Site not found" message, with no products, claims or contact details.
• Sandbox behavior on the homepage: hidden forms and password-type inputs appeared in all three runs although no form is visible, and roughly 4,100 DOM mutations followed interaction.
• Threat intelligence: 7 engines rated the address malicious and 1 suspicious, and it is listed on an external blacklist.
• Hosting-level reports: 4 abuse reports were filed against a shared edge address serving the site.

Regulatory Verification Notes

The site has no legal, about, terms, privacy or contact pages, so there are no disclosed entity names, licensing details, registration numbers or governance information to assess. The real-world operator of the subdomain is unverified, and operator identity and governance are opaque. The site makes no regulated-activity claims, so no license can be confirmed or contradicted. No third-party broker or regulatory-reputation profile matched the site. That absence is neither a favorable nor an unfavorable signal. The valid transport-encryption certificate belongs to the hosting platform, not to the subdomain's operator. It shows only that the connection is encrypted and says nothing about who runs the content. Evidence:

• Homepage and site structure: no legal, contact or corporate-identity pages and no outbound links.
• Hosting: served from AS16509 (Amazon).
• Transport encryption: the TLS certificate is OV-validated, issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 to Netlify, Inc, and valid to 2027-03-19.
• Third-party broker reputation: no match found.

What to Verify Next

The first step is to establish through an independent route why this address was supplied, such as a message, advertisement or search result. The legitimate service's official portal address should be confirmed through the organization's known website or an offline channel, not through any link tied to this address. If the address claims to be a company's portal, that company should be asked directly whether it operates it. Hosting-platform abuse reporting is the appropriate channel for notifying the provider if the address reached the user through unsolicited contact. Until the address is cleared, the site should not be used for any authentication or payment. Evidence:

• Homepage: contains no contact route or owner reference that could be checked.
• Sandbox behavior: password-type inputs were detected repeatedly even though the visible page offers none.
• Threat intelligence: the address carries blacklist and multi-engine detections that would need to clear before any engagement.

Summary Verdict

The site carries an elevated-risk, low-trust posture. Convergent external detections and anomalous hidden form behavior, with no visible content or verifiable operator behind them, outweigh the benign appearance of a platform error page. The available evidence does not support treating the address as a legitimate or safe destination.

Infrastructure Integrity

The site is served from edge addresses within a major cloud and CDN provider's network. All four observed addresses are edge nodes, and no origin address is visible. Because the platform is shared, the address cannot be independently attributed to one operator, and content can be changed quickly behind the same edge. A valid certificate and mainstream infrastructure are mitigating factors only. They do not offset the external threat detections or the hidden-form behavior.

Closing Assessment

The address should be treated as unsafe for logins, credential entry and any financial interaction. At most it can be viewed passively, and nothing should be downloaded from it. Anyone who has already entered credentials on a page at this address should change them promptly and report the incident to the relevant organization.

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.