Is stfx-5wq.pages.dev safe? TrustSniffer's low-trust assessment: 41/100

stfx-5wq.pages.dev
Download PDF Check another site How we score

Verdict

Several risk patterns were present. Do not send money or personal details until you have verified this business another way.

41 OUT OF 100
Low Trust

stfx-5wq.pages.dev is low-trust and potentially risky.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-27 by automated analysis. Classification confidence 75%.

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 engines1 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 0 reports; shared hosting inflates reportsClear
Domain age2.5 years oldRegistered historyClear
Web archiveArchived since 202410 snapshotsClear
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

No screenshot is retained for this report.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • Domain age: 1 to 3 years (registration continuity).
  • Public web-archive history exists since 2024.
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.

Full analysis

Overview

TrustSniffer assessed stfx-5wq.pages.dev on 2026-10-27 and gave it a trust score of 41/100, a low-trust result: several signals typical of risky or unverified sites were present, so extra caution is warranted. The trust score runs from 0 to 100, where 100 is the most trusted; it is an automated, evidence-based assessment and not a legal finding.

What the analysis found

2 findings contributed to this verdict, raised by external reputation, registration and ownership.

01 External reputation

  • Several malware engines flagged this domain.External reputation rule:EXT_BLACKLIST_HIGH

02 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 stfx-5wq.pages.dev.

  • The request stayed on stfx-5wq.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2024-05-02. 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:2c8b
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiryNot available
Domain age2.49 years (continuous registration)
Domain expiryNot available
Archive first seen2024-05-02
Archive snapshots10
ReputationVirusTotal: 1 flagged | AbuseIPDB: 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about stfx-5wq.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 stfx-5wq.pages.dev

Is stfx-5wq.pages.dev a scam?

TrustSniffer found several risk patterns on stfx-5wq.pages.dev. It scored 41 out of 100 on 2026-10-27, a low-trust result. That is not proof of fraud: it means the evidence did not support treating the site as safe.

Is stfx-5wq.pages.dev safe to use?

Several risk patterns were present. Do not send money or personal details until you have verified this business another way.

What is the trust score of stfx-5wq.pages.dev?

stfx-5wq.pages.dev scored 41 out of 100 on 2026-10-27, which places it in the low-trust 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-27 · how we assess · report a mistake