Is project-shiesty.firebaseapp.com safe? TrustSniffer's low-trust assessment: 48/100

Overview

This is a hosting-provider "Site Not Found" placeholder served from a project-named subdomain on a shared Google Firebase app-hosting domain. A visitor sees only a generic message that no app has been deployed, that an empty directory was published, or that a custom domain has not finished setup. There are no products, forms, login prompts, links, or branding. No business model can be inferred, and the page appears to be an unconfigured or abandoned deployment rather than an operating service.

Scam/Impersonation Risk

The decisive adverse signal is external. Third-party reputation sources currently list this host as malicious or suspicious. This is the one confirmed blacklist-type contradiction, and it keeps the assessment cautionary even though the homepage itself shows nothing harmful. The page has no credential forms, hidden forms, wallet prompts, or clipboard manipulation, and no brand impersonation was detected. No conflicting legal identities appear, because no identity content is published at all. Abuse reports exist against one of the edge addresses serving the site. They relate to a shared provider address used by many tenants, so they say little about this specific deployment, but they were not discounted and remain a visible background signal. Browser-side behavior is also atypical for a static error page. Interaction produced a very large burst of page changes, and the page made a heavy volume of outbound requests and posts to external destinations. These requests went to allow-listed destinations, but a "not found" page that does this is unusual. The tooling notes that content on an unfinished deployment could change quickly, so the placeholder state cannot be treated as a stable or benign endpoint. Evidence:

• Homepage: the only content is "Site Not Found" placeholder text of roughly 300 characters, with no forms, links, or offers; the capture returned an HTTP 404 status.
• External reputation: the host is on a current external blacklist, with one engine flagging it malicious and one flagging it suspicious.
• Shared edge address 2620:0:890::100 has 4 abuse reports from 2 distinct reporters, attributed to shared infrastructure.
• Sandbox behavior: 255 external fetch/XHR requests, 28 external posts, 2,204 DOM mutations after interaction, and 3 console errors across 3 successful runs.

Regulatory Verification Notes

The page contains no legal, terms, privacy, about, or contact content, so no operator name, company registration, licence, or regulator reference can be assessed. This is a content gap on a placeholder page, not evidence of wrongdoing. Ownership and governance are opaque, but that is an administrative limitation and not an identity contradiction. The subdomain sits on a platform where any account holder can register a project name, so the address does not itself connect the site to a verified real-world entity. No broker-rating dataset recorded a match, so there is no third-party reputational context beyond the reputation signals above. Evidence:

• Homepage: no company name, licence, jurisdiction, or registration number is published.
• Hosting: served from AS54113 (Fastly, Inc., US) under an ARIN-registered network allocation.
• Transport encryption: the TLS certificate is issued by WR4 with domain-validation (DV) only, valid to 2026-12-22. DV confirms control of the domain, not the identity of the operator.

What to Verify Next

Before any interaction, the deployment owner should be established through an independent channel. That means asking the party that supplied this address, through a known and separately obtained route, whether it is a genuine project and who administers it. If the address arrived in an unsolicited message, advert, or social post, the sender's authenticity should be checked first. The address should be revisited only after the owner has resolved the external listing and published a real application with disclosed operator details. Any later claim of licensing or registration should be confirmed directly with the relevant registry, and official support channels should be confirmed independently. Evidence:

• Homepage: the placeholder offers no contact route, so no on-site channel can be used for confirmation.
• The external blacklist listing is current and should be re-checked before any change in posture.
• The placeholder text states that the custom domain setup is unfinished, so content may change without notice.

Summary Verdict

The site carries an elevated risk posture. A current external blacklist listing, combined with unusual outbound activity from an otherwise empty page and no verifiable operator, outweighs the technically sound transport security. The site presents no legitimate service to evaluate, and legitimacy cannot be inferred from the domain.

Infrastructure Integrity

The site is delivered through the Fastly CDN, and every observed address is a CDN edge node. The origin server is not observable, which prevents independent verification of the actual hosting and can mask rapid content swaps behind the same address. The CDN, a valid certificate, and a US-registered network allocation are mitigating factors only. They show the delivery layer is well run, but they do not offset the reputation risk, and they do not vouch for whoever controls the content behind them.

Closing Assessment

Treat this address as unsuitable for logging in, entering credentials, or making any payment or financial commitment. Limit any contact to passive viewing, and only if the address came from a source already trusted through another route. Escalate to a security team if it was received through an unsolicited message.

Signals weighed against the site

• AbuseIPDB: 4 reports on hosting IP 2620:0:890::100 (Google LLC, Content Delivery Network), 3% confidence. The reports are attributed to shared infrastructure, not specifically to this website.