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

dfhsdfhsdfhsh.pages.dev

Is it safe to use? An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Download PDF Check another site How we score
Ask your AI about this report

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

Verdict

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

0 OUT OF 100
Critical Risk

dfhsdfhsdfhsh.pages.dev shows critical-risk indicators.

Sensitive Interaction Risk Governance Risk
  • Sensitive Interaction Risk: This label is given when the overall risk is high. The captured page did not ask for a password, card number or other sensitive details; if it ever does, entering them here could be unsafe.
  • Governance Risk: A registration check came back incomplete: as a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site). That is a gap in what could be looked up, not a sign that ownership is hidden, and it does not say who runs the site.

Assessed 2026-11-05 by automated analysis. Evidence confidence 75%.

How the site describes itselfThis captured page is a Cloudflare warning interstitial stating that the requested site was reported for potential phishing. It contains no evidence of the underlying site's services, branding, forms, or business model. The page risk is elevated based on the third-party phishing report, but the underlying site itself could not be analysed.

Evidence status and limitations

Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.

  • The real-world operator identity was not independently verified.

How to read these numbers

A trust score of 0 means the risk evidence outweighed every trust signal by more than the 0 to 100 scale can show. It rates the evidence found, not the probability that the site is a scam.

Evidence confidence (75%) measures how much of TrustSniffer's evidence set this site produced: the page reading, the browser sandbox, the web archive, the registration record and the reputation services. It falls when a check returns nothing, as listed above, and it does not change the score.

At a glance

The checks that decide most of this verdict.

Malware engines2 marked it maliciousVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address0% confidenceAbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
First seen5 months before captureWeb archive; a site on pages.dev has no registration of its ownRisk
Web archiveArchived since 20262 snapshots; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

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

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • First seen: less than 1 year before capture (web archive; a site on pages.dev has no registration of its own).
  • Public web-archive history exists since 2026.
  • At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.

Full analysis

Security Alert

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

Overview

This is a site hosted on a free, shared static-hosting subdomain with a randomly generated, keyboard-mash style name. It carries no recognisable brand. The only content captured from it is a security interstitial that warns the destination was reported for potential phishing. The page shows no products, pricing, branding, forms, or business description, so the site's purpose and business model cannot be determined. The interstitial offers an "Ignore & Proceed" option, which would take a visitor on to the unreviewed destination.

Scam/Impersonation Risk

This is an elevated-risk finding. The site is blacklisted by external threat intelligence: more than one independent security engine, including a tier-one security vendor, currently flags the domain as malicious or suspicious. The hosting platform's own edge security layer has separately flagged the destination as suspected phishing and placed a warning interstitial in front of it. These are the decisive signals, and they converge. The domain name is also an anonymous, randomly generated label that closely resembles the shared hosting platform's own domain name. It does not look like a legitimately branded property. This points to a disposable, throwaway deployment and does not by itself establish impersonation of a named brand. The captured page contains no login form, no payment form, and no wallet-connection or clipboard-manipulation behaviour. The underlying site's real content was never observed, so any credential or payment capture it might perform remains unassessed rather than cleared. Taken together, the blacklist status, the phishing warning, and the throwaway naming pattern justify treating this destination as a credential-harvesting risk until shown otherwise.

Evidence
  • Homepage capture: a "Suspected Phishing" interstitial states the destination "has been reported for potential phishing", with no service, identity, or contact content behind it.
  • External reputation: two security engines rated the domain malicious and three rated it suspicious, including one tier-one vendor, and this triggered the confirmed-blacklist condition.
  • Provenance: the domain is about 155 days old (~0.4 years). The web archive holds only 2 snapshots, from 2026-06-02 to 2026-06-16 (1 year tracked), which indicates a very recent and thin footprint.
  • Behaviour testing: the final destination did not match the requested page, and the site's access challenge blocked capture of the underlying content.

Regulatory Verification Notes

No licence, registration number, legal entity, terms page, privacy page, or contact channel could be reviewed, because the only captured page is the interstitial. This leaves the real-world operator unverified. Nothing links the domain to a company or person, and no regulatory claim exists to test. No broker-reputation record matches this domain. The absence of a licence is therefore not an independent finding here. The decisive concern is the external threat reporting described above. The valid transport encryption on the site is a basic hygiene control available to any deployment, including throwaway ones. It does not establish operator identity or legitimacy.

Evidence
  • Homepage capture: no company name, licence, address, or legal-page link appears anywhere in the captured content.
  • TLS certificate: issued by WE1 at domain-validated level only (no organisational validation), valid to 2026-12-24.
  • Hosting: served from AS13335 (Cloudflare, Inc., US).
  • Third-party reputation: no broker-reputation record was matched for the domain.

What to Verify Next

Verification here means establishing who operates the destination and why it was reported, before any interaction. The first step is to confirm, through an independent route, that the destination was actually provided by a known organisation, and to obtain the correct official address directly from that organisation. Anyone who reached the site through a message, advertisement, or social post should treat that source as suspect and report it. If the site is associated with a business the user expects to deal with, the official support channel should confirm independently whether the site belongs to that business. The platform's report mechanism or the site owner's abuse channel can clarify the reason for the phishing flag. Browsing past the warning should be avoided unless done in an isolated, disposable environment.

Evidence
  • Homepage capture: the "Ignore & Proceed" option is the only route to the underlying content, and its destination was not analysed.
  • Domain naming: the randomly generated hostname carries no organisational identifier that could be matched to a registry or brand.
  • External reputation: the active threat detections are the trigger for these steps.

Summary Verdict

The evidence supports a clearly high-risk, cautionary posture. Independent threat-intelligence detections and a platform-level phishing warning converge on the same conclusion. No identifying content or legitimacy evidence offsets them, and the operator's identity is unverified. The site should be regarded as potentially hostile, with its true nature unconfirmed.

Infrastructure Integrity

The domain resolves entirely to a major, reputable CDN and WAF provider's edge network, and only edge addresses were observable. The origin server could not be seen. Protective infrastructure of this kind is only a mitigating factor. It is available to any customer, including operators of abusive sites, and it does not offset the active threat reporting or confirm who runs the destination. The access challenge in front of the site also limited what could be captured. The valid, mainstream-issued certificate is a minimal hygiene control and does not change this assessment.

Closing Assessment

The site should not be used for login, credential entry, or any financial or personal-data interaction. Passwords, payment details, and wallet access must not be supplied to it. Anyone who has already entered such information should change the affected credentials immediately and monitor the associated accounts.

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

What the analysis found

6 findings contributed to this verdict, raised by external reputation, page content, history in the web archive, and hosting and network.

01 External reputation

  • A confirmed external listing marks this domain as malicious: at least five security engines including a leading vendor, ten engines, or Google Safe Browsing.External reputation rule:EXT_BLACKLIST_CRITICAL

02 Page content

  • The page shows few of the signs expected from a trustworthy operator.Page content rule:PAGE_TRUST_QUALITY_LOW
  • The review of the page content rated it moderate risk.Page content rule:PAGE_RISK_MED
  • The page runs on a free pages.dev address instead of a domain of its own, a setup common to short-lived phishing and claim pages.Page content rule:PAGE_BRAND_SUSPECTED

03 History in the web archive

  • The web archive has almost no record of this domain, which fits a site that is new.History in the web archive rule:ARCH_PEN_YOUNG_AND_SPARSE

04 Hosting and network

  • The domain was registered, or a site on a hosting platform was first seen, three to six months before capture.Hosting and network rule:DNS_YOUNG_6M

Identity verification

StatusUNVERIFIED

The operator behind the site could not be connected to a real-world brand or person. What the page shows, if anything, is listed below; none of it was independently checked.

  • No contact detail, company registration number or linked social profile was extracted from the page for checking. Any operator the page names in its own words (see how the site describes itself, above) is not verified here.

What TrustSniffer observed

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

  • The request stayed on dfhsdfhsdfhsh.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2026-06-02. Watch
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:310c::ac42:2ca1 (a CDN edge address; the server behind it was not observed)
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2026-12-24
First seen (web archive)156 days before capture; a site on pages.dev has no registration of its own
Domain expiryNot available
Archive first seen2026-06-02 (156 days before capture)
Archive snapshots2
ReputationVirusTotal: 2 malicious | AbuseIPDB (CDN edge address, not the host): 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about dfhsdfhsdfhsh.pages.dev at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A high score means the signals were consistent with a legitimately operated site; a low or critical score means several risk patterns were present. It is a starting point for your own judgement, 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 dfhsdfhsdfhsh.pages.dev

Is dfhsdfhsdfhsh.pages.dev a scam?

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

Is dfhsdfhsdfhsh.pages.dev safe to use?

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

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

dfhsdfhsdfhsh.pages.dev scored 0 out of 100 on 2026-11-05, 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.
Questions about this report? Ask your AI

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-11-05 · how we assess · report a mistake