Is foxshouse.pages.dev safe? TrustSniffer's low-trust assessment: 42/100

foxshouse.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.

42 OUT OF 100
Low Trust

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

The page as captured

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

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

Security Alert

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

This website is a small web property on the free, shared Cloudflare Pages hosting namespace. Automated visits received only a Cloudflare bot-challenge response, so no brand, product, service or business model could be observed, and its apparent purpose cannot be determined from the captured content.

Scam/Impersonation Risk

Contradictory signals are present and are the decisive factor in this assessment. Several independent threat-intelligence engines classify the site as malicious, and a tier-one security vendor is among them. The reputation picture is therefore blacklisted by confirmed external detections, not merely a soft reputational concern. The page returned to the analysis sensor was an interstitial titled as a suspected-phishing warning, which is consistent with those detections. Seven abuse reports exist against a Cloudflare edge IP address the site resolves to. These apply to shared provider infrastructure with a zero confidence rating, so they are discounted and are not held against the site. No conflicting legal identities and no brand impersonation were observed, and no wallet-connection, clipboard-manipulation or hidden-form behaviour was triggered in three sandbox runs. The site's network behaviour is nonetheless unusual. A large share of its traffic goes to external hosts and the browser logged repeated console errors. This pattern fits a thin page that relies on third-party resources, and it adds to the caution without establishing intent. The external detections stand regardless of whether the operator is a deliberate actor or a compromised party. Evidence:

  • The homepage capture was a Cloudflare challenge page (HTTP 403) titled "Suspected Phishing | Cloudflare", with very little text and no site-authored content.
  • Sandbox observation of the homepage recorded 12 external XHR/fetch calls and 6 external POST requests, all to whitelisted destinations. External requests made up about 87% of the peak network activity, and 12 console errors were logged.
  • Archive history covers 10 snapshots from 2024-09 to 2025-03 (about 2 years tracked). The domain is roughly 1.8 years old.

Regulatory Verification Notes

The site presented no legal, terms, privacy or about content in the captured material. Licensing status, a corporate registration or a named operator therefore cannot be assessed. No regulator or broker-rating dataset matched this site, so no third-party reputational signal exists on that front. The operator's real-world identity is unconfirmed, and the registration record shows ownership opacity. This is an administrative limitation and not a contradiction in itself, but it leaves the external threat detections without any accountable party to answer them. The valid transport encryption is only a baseline hygiene signal. Domain-validated certificates are issued automatically to any controlled hostname and do not attest to who operates the site. Evidence:

  • The site is served from AS13335 (Cloudflare, Inc., US). The site's own pages publish no disclosure of an operating entity.
  • The TLS certificate was issued by WE1 at DV level and is valid to 2027-01-14.
  • The domain sits under the shared pages.dev namespace, so it has no independently registered domain identity.

What to Verify Next

Before any engagement, obtain a direct statement from the claimed operator through an independent, offline route that names the legal entity behind this hostname. Confirm that entity in the relevant company or financial-services registry in its home jurisdiction. Check whether the hostname is referenced from any official channel of a known brand, because a free-hosting subdomain is easy to create and discard. A re-scan after the operator reports remediation would show whether the external detections have been cleared. Evidence:

  • The homepage disclosed no operator, registry number or official contact route.
  • The malicious classifications attach to this hostname itself, not to the shared hosting provider.

Summary Verdict

The overall posture is one of elevated risk. The weight of confirmed external threat detections outweighs the clean transport encryption and the stable, uninterrupted archive history, so the site is treated as unsafe for any sensitive interaction. The evidence shows a short-lived free-hosted property with an unconfirmed operator. It does not show a site that has earned trust.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF. All four observed addresses are Cloudflare edge servers, and the origin server was not observable, so independent verification of the real hosting location is not possible. The bot-protection layer is a mitigating factor for availability and abuse resistance only. It cannot offset the external reputation risk, and it also means the visible content can be altered at the edge without detection from outside.

Closing Assessment

Access should be limited to passive, read-only viewing at most, with no account creation, login, credential entry, payment or financial interaction, and no file downloads, until the external detections are cleared and an accountable operator is independently confirmed.

Written analysis generated 2026-10-27 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

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

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 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
  • The page sent data to other domains many times while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_POSTS_HEAVY

03 Registration and ownership

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

Signals weighed against the site

  • AbuseIPDB: 7 reports on hosting IP 2a06:98c1:3120::1 (Cloudflare, Inc., Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

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 foxshouse.pages.dev.

  • The request stayed on foxshouse.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2024-09-08. Clear
  • It is hosted on CLOUDFLARENET, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc., US
CountryUS
Server IP2a06:98c1:3120::1
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2027-01-14
Domain age1.80 years (continuous registration)
Domain expiryNot available
Archive first seen2024-09-08
Archive snapshots10
ReputationVirusTotal: 4 flagged | AbuseIPDB: 0% confidence, 7 reports | Google Safe Browsing: 0 matches

About this assessment

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

Is foxshouse.pages.dev a scam?

TrustSniffer found several risk patterns on foxshouse.pages.dev. It scored 42 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 foxshouse.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 foxshouse.pages.dev?

foxshouse.pages.dev scored 42 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