Is whitelist-manager.vercel.app a scam? TrustSniffer's high-risk assessment: 16/100

Overview

This website is a single-page web application titled "whitelist manager". It is served from a subdomain of a shared application-hosting platform rather than from a standalone branded domain. The homepage shows only a few lines of text and no company description, product explanation, pricing, or visible navigation to supporting pages. The name suggests an allowlist or access-management utility, but the site gives no evidence of who operates it, whom it serves, or what it does with the data and accounts it might handle.

Scam/Impersonation Risk

The assessment is high risk because of confirmed external threat detections, not because the page shows overt fraud mechanics. The domain is blacklisted: multiple independent security engines flag it as malicious or suspicious, and these detections are the decisive factor in the cautionary posture. No distinct legal entities, conflicting identities, or impersonated brands were observed. No wallet-connection prompts, clipboard manipulation, hidden or externally posting credential forms, or content cloaking appeared during behavioral testing. These clean behavioral results do not offset the blacklist. The homepage is too thin to show what the site is for, so the blacklisting stands without any benign explanation on the page. Roughly ninety abuse reports exist against a hosting-platform address associated with this site. That address is shared by many unrelated tenants, and the reporting source assigns it no confidence of abuse. These reports are therefore discounted as shared-infrastructure noise and are not attributed to this site. Behavioral testing also logged repeated client-side console errors and frequent third-party requests, all to recognized destinations. This points to an unfinished or poorly maintained application rather than a hostile one. Evidence:

• Homepage, reputation screening: 2 engines returned malicious and 1 returned suspicious verdicts, which triggered the blacklist determination.
• Homepage, behavioral testing across 3 successful runs: 14 external requests, none to non-whitelisted destinations, no external form posts, no wallet-provider activity, and no cloaking after interaction.
• Hosting-platform address reputation: 90 abuse reports from 9 distinct reporters, most recently on 2026-10-25, attributed to shared infrastructure and discounted.
• Homepage rendering: 14 console errors recorded across the test runs.

Regulatory Verification Notes

The only page captured is the homepage, which carries a very short body of text. It has no terms, privacy policy, about page, legal entity name, registration number, or licensing statement, so no regulatory status can be derived from the site. Automated page analysis could not independently link the site to any real-world brand or person, so the operator's identity is unconfirmed. No third-party broker or regulator-style reputation record matched this site, and the absence of a match is neutral. This note concerns disclosure only. It is separate from, and not the cause of, the elevated-risk finding above. Evidence:

• Homepage: roughly 90 characters of body text and no legal, licensing, or entity disclosures.
• Hosting infrastructure: served from AS16509 (AMAZON-02, Amazon.com, Inc., US), with the abuse reports above tied to Vercel, Inc.'s shared network.
• Transport encryption: TLS certificate issued by WR1 at domain-validated (DV) level, valid to 2026-11-27 with about 32 days remaining. DV validates domain control only and says nothing about the operator.

What to Verify Next

Before any interaction beyond viewing, the operator's identity and purpose should be established independently. The first step is to obtain the site's address from a trusted source, such as the organization that told the user to use it, and confirm it matches exactly. The second step is to ask that party in writing, through a channel known to be genuine, what the tool is and who operates it. Official support and contact channels should be confirmed the same way. Third, the specific detections should be rechecked in a multi-engine reputation service, and the site should be treated as unsafe until they clear. If the site appears to be a legitimate project that has been compromised, its owner should be notified so the content can be cleaned. Evidence:

• Homepage: no named operator, purpose statement, or contact route, so identity can only be established off-site.
• Reputation screening: the malicious and suspicious detections are current and remain unresolved.
• Transport encryption: the certificate expires 2026-11-27, which is a routine renewal point and not a risk in itself.

Summary Verdict

The evidence supports an elevated-risk, clearly cautionary posture. Current external threat detections are decisive, and the site's own content gives no counterweight in the form of a verifiable operator, a stated purpose, or supporting disclosures. Sound transport security and unremarkable behavioral testing show a functioning site but do not outweigh the reputation findings.

Infrastructure Integrity

The site is delivered through Amazon-hosted infrastructure on a major platform's CDN. The observed addresses all belong to the provider's edge network, and the origin server was not observable. Edge-only visibility prevents independent verification of the hosting and can allow content to be swapped quickly. The protection is a mitigating factor only. It does not offset the reputation risk and does not make the site legitimate.

Closing Assessment

The site should be limited to passive viewing at most. Logins, credentials, wallet connections, personal data, and payments should be withheld until the operator is independently verified and the security detections are cleared.

Signals weighed against the site

• AbuseIPDB: 90 reports on hosting IP 64.29.17.67 (Vercel, Inc, Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.