Is Certifiedhoodrat a scam? TrustSniffer's high-risk assessment of certifiedhoodrat.info: 0/100

Security Alert

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

This domain hosts a very recently registered website under the ".info" top-level domain, and the name does not point to any recognisable brand. When the site was visited, no ordinary storefront or service content loaded. The visitor was met by a security interstitial with the title "Suspected Phishing", served with an access-denied response and a bot challenge in front of a very short page. The apparent purpose and business model of the site could therefore not be read from its own content. The only presentation a visitor receives is a warning that the site is suspected of phishing.

Scam/Impersonation Risk

Contradictory signals are present, and they are decisive. The domain is blacklisted. A large cluster of independent security engines flag it as malicious, including several of the most widely relied-on endpoint-security vendors, and the aggregate detection level is high enough to trigger an automatic critical override. The same domain is also recorded in a known-phishing context, and the interstitial served on the homepage independently labels it as suspected phishing. Together these amount to a convergent, multi-source indication of phishing-type abuse, not a single noisy detection. Nothing in the evidence points to brand impersonation or conflicting legal identities. The risk comes from the reputation and phishing signals themselves. The domain's age compounds it: it is days-to-months old rather than established, which is the profile typical of disposable campaign infrastructure. Its trading history is a single archive capture with no earlier continuity, so there is no track record of legitimate operation to weigh against the detections. During automated interaction, the site made heavy volumes of outbound requests to third-party endpoints. Page scripts produced many console errors and large DOM mutations after interaction. No wallet-connection, clipboard-hijack or hidden-form behaviour was observed, and all contacted endpoints were whitelisted. Evidence:

• Homepage: the captured page was a challenge interstitial titled "Suspected Phishing", returned with an access-denied status.
• External reputation: multiple major security vendors currently classify the domain as malicious, and it is on a confirmed blacklist.
• Domain provenance: registered 2026-07-22 (~0.27 years old); the web archive holds 1 snapshot, dated 2026 (1 year tracked), so there is no prior history.
• Behavioural sandbox: heavy third-party request traffic and 29 console errors across 3 runs, with no wallet-drainer or clipboard-hijack activity.

Regulatory Verification Notes

No licensing, registration or regulator-facing disclosure can be associated with this domain, and no third-party regulatory source vouches for it. No broker-reputation entry was matched either. The domain's content could not be examined, so no legal-entity or terms pages were available to assess. The absence of verifiable regulatory standing therefore adds nothing to mitigate the confirmed reputation findings. Technical hygiene is basic and unremarkable: a valid but low-assurance domain-validated certificate and a mainstream hosting network. These show that the site is operational. They say nothing about who runs it or whether it is lawful. Evidence:

• Registrar: NICENIC INTERNATIONAL GROUP CO., LIMITED; registration runs to 2027-07-22.
• Transport encryption: TLS certificate issued by WE1 (DV), valid to 2026-12-18 (about 50 days remaining).
• Hosting: served from AS13335 (CLOUDFLARENET - Cloudflare, Inc., US).
• DeFi recognition: the domain is not listed in any DeFi protocol directory, so there is no TVL or market-capitalisation evidence of legitimacy.

What to Verify Next

Nothing should be verified by interacting with the site. The first step is to find out how the domain reached the user, such as a message, advertisement or link, and to treat that origin as potentially hostile. The second is to confirm independently through an offline, known-good route whether any organisation actually claims this domain, using an official channel for that organisation and not anything reachable from the site. Security teams should add the domain to blocking and monitoring controls and check mail and proxy logs for earlier contact. If the domain is believed to be a legitimate property that has been compromised, its owner should be notified so that it can be cleaned and delisted. Evidence:

• Homepage: the suspected-phishing interstitial is the only content observed, so no on-site channel can be treated as trustworthy.
• External reputation: the active blacklist status should be rechecked before any future reassessment.
• Domain provenance: the very recent registration means no historical use can be relied upon to indicate who operates it.

Summary Verdict

The overall posture is high-risk and clearly cautionary. Several independent security sources currently classify the domain as malicious, and the site's own access layer labels it a suspected phishing destination. Its young age and the lack of any history or verified identity give no legitimate-operation evidence to set against these findings. Positive trust signals are limited to a valid certificate and mainstream hosting. They do not offset the reputation findings, and they do not establish identity or legitimacy.

Infrastructure Integrity

The site is fronted by Cloudflare's CDN and WAF, and every observed address is a CDN edge address. The origin server is not visible. Bot protection was active during analysis, and it is what produced the challenge interstitial. This protection is a mitigating factor only. It is not evidence of legitimacy, and it cannot offset the threat detections. It also prevents independent verification of the real hosting and allows content to be changed behind the edge without notice. The site's certificate is valid and from a recognised issuer, but it provides encryption only and does not vouch for the operator.

Closing Assessment

The domain should not be used for any login, credential entry, payment or wallet interaction. It should not be visited from a production environment, and nothing should be downloaded from it. Anyone who has already entered credentials or financial details should change them immediately and report the incident to the relevant security team or provider.