Is airdrop-stonkfun.com 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.

The domain airdrop-stonkfun.com presents itself as a cryptocurrency "airdrop" landing site, with a name that pairs a token-giveaway keyword with a meme-token-style brand. Its apparent purpose is to attract visitors with a free-token or claim offer. When the homepage was loaded, a Cloudflare challenge page titled "Suspected Phishing" was served in place of ordinary content, so no operator-authored text, product description or claim flow could be read. The domain was registered only weeks before the assessment.

Scam/Impersonation Risk

Confirmed contradictory signals are present, and the assessment is clearly cautionary. Several external reputation sources currently flag the domain. Multiple security engines report it as malicious, a further group classify it as suspicious, and a major network-security vendor lists it as a threat. Together these amount to a confirmed blacklisting. The only page observed at the homepage was a challenge interstitial labelled as suspected phishing. The naming pattern, an "airdrop" keyword attached to a token-style brand, matches the common structure of crypto giveaway lures that ask visitors to connect a wallet or approve a transaction. No wallet-connection prompt, clipboard manipulation or external credential form was triggered during the three automated browsing runs. That is a limited observation, because the real content was gated. Runtime behaviour was nonetheless unusual. Nearly all network activity went to third-party hosts: about ninety-one external background requests and nine external data submissions in a short session. The page also threw seventeen console errors and rebuilt over fifteen hundred page elements after interaction. This points to a heavily script-driven front end whose true behaviour is hidden from automated inspection. No conflicting legal identities and no confirmed impersonation of a specific named brand were established. Evidence:

• Homepage: served a bot-challenge page with a 403 status, titled as suspected phishing, instead of site content.
• Domain registration: created 2026-09-11 (~0.11 years old) through NICENIC INTERNATIONAL GROUP CO., LIMITED, expiring 2027-09-11.
• Web archive: 3 snapshots spanning 2026-09-11 to 2026-09-12 (1 year tracked), consistent with a newly created site.
• Homepage runtime: 91 external background requests, 9 external POSTs, 17 console errors and a peak of 1,523 DOM mutations across three runs.

Regulatory Verification Notes

No licensing, registration or legal-entity information could be observed. The only page retrieved was a security interstitial, so no terms, about or contact page was available to assess. Disclosure therefore cannot be called adequate or inadequate. Registrant details are incomplete, which constitutes ownership opacity. That is an administrative limitation and not an identity contradiction. No third-party broker or regulator-style reputation entry matched this domain. The reputational concern rests on the threat detections described above, and nothing in the evidence suggests the operator holds any financial or token-distribution authorization. The valid TLS certificate adds nothing on legitimacy, because domain-validated certificates are issued to any domain controller. Evidence:

• Homepage: no company name, licence number, jurisdiction or terms of service was visible.
• Transport security: certificate issued by WE1 (DV, domain-validated only), valid to 2026-12-10.
• Hosting: served from AS13335 (Cloudflare, Inc., US).
• Reputation databases: no broker or regulatory-register match for the domain.

What to Verify Next

Any project whose name the domain evokes should be checked through its own independently known website and verified social channels. The checks should confirm whether an airdrop or token claim exists at all, and whether this domain is referenced there. The route by which the link was received (a message, advertisement or social post) should be treated as untrusted and examined for how it reached the recipient. Security teams should review organisational logs for any prior visits or wallet interactions with the domain. Wallets that have already interacted with it should have outstanding token approvals reviewed and revoked. A single check of the claimed operator's licensing status with the relevant registry is warranted only if a legal entity is later identified. Evidence:

• Homepage: the challenge interstitial prevented any review of the claimed offer or its claim flow.
• Domain history: the domain's creation weeks ago means there is no prior track record to rely on.
• Runtime behaviour: heavy third-party data transfer means any interaction could expose data to undisclosed parties.

Summary Verdict

The site is assessed as high-risk and not trustworthy. Active threat detections from several independent sources, a very recent registration and an unexplained script-heavy front end converge on a posture consistent with a credential-harvesting or wallet-draining lure. The technical hygiene visible on the site is common to all web properties and does not offset this conclusion.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF. All four observed addresses are Cloudflare edge servers and no origin host could be identified, so the real hosting location cannot be independently confirmed. Bot protection is active, and it prevented normal content retrieval. This reduces exposure of the underlying server but is only a mitigating factor. It does not offset the external threat detections. Content behind the edge can also be changed rapidly without visible hosting changes. The valid, long-dated certificate and the identified network are routine properties of the platform.

Closing Assessment

The domain should not be used for login, wallet connection, token approvals, payment or the entry of any personal or credential data. If the site was visited, any connected wallets should be disconnected and their approvals revoked. The link and domain should be reported to the relevant security teams and blocked at the network or email layer where possible. Any airdrop claim should be pursued only through channels reached independently of this domain.