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

rftgjfgjhfgdj.pages.dev
Download PDF Check another site How we score

Verdict

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

0 OUT OF 100
Critical Risk

rftgjfgjhfgdj.pages.dev shows high-risk / scam indicators.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-29 by automated analysis. Classification confidence 55%.

Evidence status and limitations

Evidence completeness: Not recorded

  • The real-world operator identity was not independently verified.
  • Module-level completeness metadata is unavailable for this legacy report.

At a glance

The checks that decide most of this verdict.

Malware engines11 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 0 reports; shared hosting inflates reportsClear
Domain ageNot availableNo registration record was returnedNoted
CertificateEncrypted connectionIssued by WE1Noted
Hosted byCLOUDFLARENETServer in USNoted

The page as captured

https://rftgjfgjhfgdj.pages.dev/
Screenshot of the rftgjfgjhfgdj.pages.dev homepage captured during the TrustSniffer assessment
What rftgjfgjhfgdj.pages.dev served when TrustSniffer captured it on 2026-10-29. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.

Full analysis

Security Alert

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

This website is a randomly named subdomain on a free Cloudflare Pages hosting platform, and it presents no business content to visitors. The only material captured was a protective interstitial titled "Suspected Phishing", served instead of the intended page. Its apparent purpose could not be established from the content. The page appears to be a disposable deployment, the kind commonly used to stage phishing or other abusive pages.

Scam/Impersonation Risk

Multiple independent security vendors currently flag the site as malicious, including two tier-one engines. The detections are strong enough to place the site on a confirmed blacklist. No single detection category is specified, but the volume and the involvement of tier-one vendors make the reputational signal decisive. The homepage was also withheld behind a bot-challenge response, and the interstitial that replaced it carries a suspected-phishing label. The site's behaviour in a controlled session was consistent with an unstable or evasive page. It produced a large number of requests to external destinations, with nearly all activity directed off-origin. It also made repeated external data submissions, showed heavy page restructuring after interaction, and logged many console errors. No wallet-connection prompts, clipboard manipulation, hidden forms or external password forms were observed. No brand impersonation or conflicting legal identities were identified. The risk therefore rests on the threat-intelligence detections and the phishing labelling, not on identity inconsistencies. The random, meaningless hostname adds to the concern, because it gives a visitor no way to link the page to a recognizable organization. Evidence:

  • Homepage: the captured page was a challenge interstitial titled "Suspected Phishing", returned with an access-denied status instead of normal site content.
  • Reputation checks: several security vendors report the domain as malicious or suspicious, and the aggregate result triggered an automatic critical-risk override.
  • Behavioural session of the homepage: 66 external XHR/fetch calls and 9 external POST requests, with 34 console errors and 1,518 DOM mutations after interaction.
  • Behavioural session: no wallet-drainer, clipboard-hijack or hidden-form behaviour was detected.

Regulatory Verification Notes

The page that could be captured contains no legal, licensing, company or contact disclosures, and there is no about, terms or privacy page. The real-world operator has not been independently identified, so no claim of legitimacy can be made. The only affirmative technical indicators are a valid transport-encryption certificate and mainstream hosting. A domain-validated certificate shows only that the certificate holder controlled the hostname, not who operates the site, and it cannot offset the threat detections. No third-party broker or regulatory-database entry matched this site, so there is no external reputational context beyond the security detections. Evidence:

  • The site's transport encryption: TLS certificate issued by WE1 (domain-validated, DV), valid to 2027-01-11.
  • The site's hosting infrastructure: served from AS13335 (Cloudflare, Inc., US).
  • Homepage: no company name, licence, registration number or contact channel is present in the captured content.

What to Verify Next

Do not seek to confirm the site's legitimacy through its own pages. If a party has directed a user to this address, the claim should be checked through an independent, offline route with that organization. Official domains should be taken from a trusted source, such as printed materials, a regulator's public register or a known official channel, not from links in messages or ads. Any legal entity or licence the sender claims should be looked up directly in the relevant public registry. If the address arrived in an unsolicited message, the sender should be treated as suspect and the message reported. Evidence:

  • Homepage: the only content observed is a phishing-warning interstitial, so there are no on-site claims to cross-check.
  • Hostname: the random, non-descriptive subdomain on a shared hosting platform gives no link to any named organization.
  • Security feeds: current malicious listings mean any referral to this address warrants independent confirmation of origin.

Summary Verdict

The site carries an elevated, critical risk posture. Current threat detections, the phishing labelling on the captured page, and unstable external-heavy behaviour converge on the same conclusion. No identity or provenance evidence offsets them.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and every observed address is a Cloudflare edge address. This also means the origin server is not independently observable. The edge posture and the valid certificate are mitigating technical factors only. They show competent delivery infrastructure but do not indicate trustworthiness, and they do not offset the reputation findings.

Closing Assessment

This address should not be visited for any purpose beyond passive review in an isolated environment. No credentials, personal data, payment details or wallet connections should be provided, and nothing should be downloaded from it. Anyone who arrived through a link or message should report that message and confirm the intended destination through an official channel.

Written analysis generated 2026-10-29 by the TrustSniffer Analysis Engine from the evidence in this report.

What the analysis found

3 findings contributed to this verdict, raised by external reputation, behaviour in a sandbox, registration and ownership.

01 External reputation

  • An external threat feed lists this domain: either Google Safe Browsing marked it malicious, or a significant number of malware engines flagged it.External reputation rule:EXT_BLACKLIST_CRITICAL

02 Behaviour in a sandbox

  • Most of what the page loaded came from other domains rather than from this one.Behaviour in a sandbox rule:BEHAV_EXTERNAL_RATIO_HIGH
  • The structure of the page changed sharply while it was loading.Behaviour in a sandbox rule:BEHAV_DOM_DENSITY_SPIKE
  • The page produced an unusually high number of errors while it ran.Behaviour in a sandbox rule:BEHAV_CONSOLE_ERRORS_HIGH
  • The page made many background requests to other domains while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_XHR_HEAVY

03 Registration and ownership

  • The public registration record for this domain is incomplete.Registration and ownership rule:KF_WHOIS_INCOMPLETE

Identity verification

StatusUNKNOWN
Identity score50/100
Identity verification confidence30%
  • AI page analysis unavailable (page captured; identity not AI-verified)

Identity verification measures whether the site can be independently connected to a real-world brand or person. It is separate from the classification confidence.

What TrustSniffer observed

First-party facts recorded during the assessment of rftgjfgjhfgdj.pages.dev.

  • The request stayed on rftgjfgjhfgdj.pages.dev. It was not redirected to another domain. Clear
  • It is hosted on CLOUDFLARENET, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc., US
CountryUS
Server IP2606:4700:310c::ac42:2d2c
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2027-01-11
Domain ageNot available (no registration date was returned)
Domain expiryNot available
Archive first seenNot available
Archive snapshotsNot counted (archive lookup incomplete)
ReputationVirusTotal: 11 flagged | AbuseIPDB: 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about rftgjfgjhfgdj.pages.dev at assessment time. It is a starting point for your own judgement, not a guarantee: a high score means the signals were consistent with a legitimately operated site, a low or critical score means several risk patterns were present.

TrustSniffer assesses a website from the evidence it can collect at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A score is a summary of that evidence, not a guarantee and not a legal finding. There is no human rating and no user review in it. A site can change after it is assessed.

Already paid or signed in? Do this now

Act fast. The sooner your bank knows, the better the chance of stopping the payment.

  1. Call your bank or card company now. Use the number on the back of your card. Ask them to stop or reverse the payment.
  2. Paid with crypto? Contact the exchange or wallet app you sent it from today. Give them the address you paid.
  3. Signed in or shared a password? Change it now, on every site where you use it, and turn on two-step sign-in.
  4. Report it to the police. In the US you can also report at reportfraud.ftc.gov and ic3.gov. In other countries, use your national police or fraud reporting service.
  5. Keep the evidence. Save screenshots, receipts, emails and chat messages. Your bank and the police will ask for them.
  6. Ignore anyone who offers to get your money back for a fee. These "recovery" offers are often a second scam.

Looking for the real site? Type the company name into a search engine yourself, or use the web address printed on your card, bill or letter. Do not use links from messages or ads.

Common questions about rftgjfgjhfgdj.pages.dev

Is rftgjfgjhfgdj.pages.dev a scam?

TrustSniffer's assessment of rftgjfgjhfgdj.pages.dev found strong scam indicators. It scored 0 out of 100 on 2026-10-29, which is the critical-risk band. The specific signals are listed in the evidence above.

Is rftgjfgjhfgdj.pages.dev safe to use?

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

What is the trust score of rftgjfgjhfgdj.pages.dev?

rftgjfgjhfgdj.pages.dev scored 0 out of 100 on 2026-10-29, which places it in the critical-risk band. The score is built from the domain's age and registration history, its hosting and certificate, the content of the site itself, and third-party reputation data. There is no human rating and no user review in it.

Download this report as PDF Free, no account needed. Create one to keep a history of the sites you check.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-29 · how we assess · report a mistake