Is verify-rainmakerapp.pro 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.

Rainmaker is a single-page web property, titled "Rainmaker", on a very recently created domain whose name pairs a "verify" prefix with a product-style name. Its homepage carries a modest amount of text and gives the visitor no stated corporate operator. Automated access to the site is gated by a bot-challenge layer. The site's purpose is not established from the captured content. The naming pattern suggests an app-access or account-verification flow rather than a conventional information site.

Scam/Impersonation Risk

This site shows confirmed contradictory signals. Several major threat-intelligence engines currently flag the domain as malicious or suspicious, including at least one top-tier security vendor, and an external blacklist listing is active. This is a decisive negative. No page-level content was captured that would show which kind of abuse is behind the detections, so the listing is a reputational finding, not a documented attack technique. No conflicting legal identities and no impersonation of a specific named brand were observed. The domain name is a concern in itself. A "verify-" prefix attached to a product name is a construction often used for credential-collection and onboarding lures, and the domain is only weeks old. Behavioral testing found no wallet-connection prompts, clipboard manipulation, hidden forms, or password forms posting to outside parties. Those results do not offset the blacklist listing. The page makes heavy use of third-party requests and logged repeated script errors, which is consistent with an unfinished or deliberately thin deployment. Evidence:

• Homepage and domain: the "verify-" naming pattern and the "Rainmaker" page title are the only identity cues, and neither ties the site to a verifiable organization.
• Reputation: multiple independent threat-intelligence engines flag the domain, so the listing does not depend on a single vendor.
• Homepage behavior: automated sessions recorded 27 third-party XHR/fetch calls and 9 third-party POST requests, none to non-allow-listed destinations, with 9 console errors.
• Domain provenance: registered 2026-08-03 (~0.23 years old); the web archive holds 1 snapshot, dated 2026-08-04, in a single tracked year.

Regulatory Verification Notes

The homepage text names no operating company, jurisdiction, licence, or registration number. It also exposes no dedicated legal or terms pages. The site's real-world operator therefore cannot be tied to any accountable entity. This is a disclosure gap and should be weighed as one, but it is not the basis for the cautionary posture. That posture rests on the blacklist and threat-detection findings above. No regulator, broker-reputation, or third-party licensing record matches the domain. Ownership details are also obscured. That is an opacity limitation, not an identity contradiction. The domain's technical hygiene is ordinary: the transport certificate is valid. A domain-validated certificate only proves control of the domain name and says nothing about who operates it. Evidence:

• Homepage: no legal entity, licence, or registration identifiers appear in the captured text.
• Hosting: served from AS13335 (Cloudflare).
• Transport encryption: TLS certificate issued by WE1 (DV), valid to 2026-12-30.
• Registration: registered through NICENIC INTERNATIONAL GROUP CO., LIMITED, with a one-year term expiring 2027-08-03.

What to Verify Next

The operator should be treated as unidentified until it is confirmed independently of this site. Any claim that "Rainmaker" is a licensed service or a known application should be checked against the official channels of the brand or app it claims to represent. Those channels should be reached through an offline or previously trusted route, not through links on this domain. If a financial or regulated activity is implied, the relevant national registry should be searched for the operator's name. Any account, verification, or onboarding request that arrives pointing to this domain should be treated as unsolicited and confirmed with the supposed sender through a separate channel. Security teams should also check whether the domain appears in their own mail, proxy, or DNS logs, and should block it pending clearance. Evidence:

• Domain: the listing and detections are current, so the domain should be re-checked against threat feeds before any change in handling.
• Homepage: no verifiable operator identity is presented, so confirmation must come from outside the site.
• Domain naming: the "verify-" construction suggests a link that may have been delivered to users by email or message, which makes the delivery channel worth examining.

Summary Verdict

Available evidence supports a high-risk posture. Active adverse reputation findings, a very new domain with almost no history, and an unidentified operator converge on the same conclusion. The absence of observed credential-theft mechanics does not change it, because the reputational detections are decisive. The site should be treated as unsafe for any sensitive interaction.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and all four observed addresses are edge servers. The origin server was not observable, so hosting cannot be independently attributed to the operator. A bot-challenge layer is also present. The setup is mainstream and the certificate is valid. These are mitigating factors only. Shared protective infrastructure is available to anyone and does not offset the adverse reputation findings. The edge-only visibility also means the content behind the domain could change quickly without any change visible at the network level.

Closing Assessment

Do not log in, enter credentials, or make any payment or financial commitment on this domain. Viewing the page without interacting is the only low-risk use. Anyone who was directed here by a message or advertisement should report that message, avoid following any further instructions in it, and change credentials already submitted to this site. Interaction should be reconsidered only if the operator is independently identified and the threat listings are cleared.