Is blockdagtoken.pages.dev a scam? TrustSniffer's high-risk assessment: 5/100

Security Alert

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

This is a web page published on a shared Cloudflare Pages subdomain, and its hostname presents it as a "BlockDAG token" property. That naming suggests a cryptocurrency token promotion or presale. The content captured from the page was only a short security interstitial, not a full storefront, so the site's own products, yields and claims could not be read. Its apparent purpose, judging by the name alone, is to draw visitors toward a crypto-asset offering.

Scam/Impersonation Risk

Contradictory signals are present and decisive. Several major security vendors independently classify the site as malicious, and an external blacklist record exists for it. The hosting platform's own security layer replaced the homepage with a warning page titled "suspected phishing", and the capture returned an access-denied response. These signals converge on one conclusion: the site is a confirmed blacklisted destination with a phishing association. Its crypto-token naming fits a pattern that fraud operators commonly use to lure visitors toward wallet-connection or payment flows. No conflicting legal identities were found, and the site was not found to impersonate a specific named brand. The risk here comes from the threat listings, not from identity conflicts. Behavioral testing found no wallet-connection attempts, wallet-drainer routines, clipboard manipulation or hidden credential forms. That absence does not offset the external detections, because the page content was gated and not fully observable. The same testing showed that nearly all page activity went to external resources, with repeated script errors across sessions. This is consistent with a page that loads most of its behavior from elsewhere. Evidence:

• Homepage: the capture was replaced by a platform interstitial titled "Suspected Phishing", returned with an access-denied status, and exposed only a very short block of text.
• Reputation checks: multiple tier-one security vendors flag the domain as malicious, and one further engine marks it suspicious. An external blacklist record exists.
• Archive record: 20 snapshots spanning 2024–2025 (2 years tracked), with the first capture in May 2024. The domain is about 2.4 years old and the archive reaches back only to that point.
• Behavioral sandbox: 18 external XHR calls and 4 external POST requests across 3 runs, 16 console errors, and no wallet or form-hijack activity.

Regulatory Verification Notes

The captured page exposed no legal, terms, privacy or about content, so no licensing status, corporate registration or named operating entity can be assessed from the site. Operator ownership is opaque. This is an administrative limitation and is not treated as an identity contradiction. Nothing on the site supports a claim of regulated status, and no third-party broker or regulatory-database match exists for the name. Any crypto-asset activity tied to this hostname should therefore be treated as unregulated and unverified. The reputational risk stems from the threat detections described above, not from the absence of disclosures. Evidence:

• Legal and identity pages: none were retrievable, and the only content captured was the security interstitial.
• Broker intelligence: no match for the site name in the reputational dataset, which is a contextual signal and not a licensing verdict.
• Hosting: served from AS13335 (Cloudflare, Inc., US).
• Transport encryption: TLS certificate issued by WE1 (DV, domain-validated only), valid to 2026-12-03. This confirms an encrypted connection and says nothing about operator identity.

What to Verify Next

Anyone who encounters this link should not follow its calls to action. They should confirm whether the "BlockDAG" project has an official web presence by consulting independent, long-standing sources such as established exchange listings or the project's published documentation, and compare that hostname with this one. Because this address sits on a free-form shared hosting subdomain, it should be checked against the project's official channels before any trust is extended. If any token sale, presale or investment offer is associated with the site, the offering entity's authorization should be confirmed with the relevant financial regulator's public register through an independent route. Official support and contact channels should be confirmed from sources other than this site. Evidence:

• Hostname: the site runs on a shared platform subdomain, and the project name appears only within the subdomain label.
• Homepage: no operator name, licence reference or official-channel disclosure was visible in the captured content.
• Reputation checks: the existing malicious classifications mean a clean result cannot be assumed until independently cleared.

Summary Verdict

The site sits in a critical-risk posture. Active threat-intelligence detections and a phishing association outweigh every neutral or positive technical attribute observed. The available evidence indicates a destination that is dangerous for any sensitive interaction, and there is no basis for treating it as an established or legitimate entity.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and WAF, and every observed address belongs to the provider's edge network. The origin server was not observable. The Cloudflare bot-protection layer is active. This is a mitigating factor only, because it indicates a mainstream hosting platform. It does not validate the site, and it cannot offset the external threat detections. Edge-only visibility also prevents independent verification of the true hosting origin.

Closing Assessment

The site should not be used for login, credential entry, wallet connection or any financial transaction, and nothing should be downloaded from it. If it must be viewed at all, the visit should be read-only, from an isolated or protected environment. Anyone who has already interacted with it should rotate affected credentials and review any wallet approvals.