---
title: "Is syncreconfig.pages.dev a Scam? Risk Report, Score 0/100"
source: TrustSniffer
type: Website trust & fraud report
subject: "syncreconfig.pages.dev"
verdict: "Critical Risk"
trust_score: 0
classification_confidence: 75
canonical_url: https://trustsniffer.com/report/syncreconfig.pages.dev
assessed: 2026-11-06
---

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

## Verdict


**Verdict: Critical Risk, trust score 0/100.** syncreconfig.pages.dev shows critical-risk indicators.

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

Labels: 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-06 by automated analysis. Evidence confidence 75%.

| Field | Value |
| --- | --- |
| How the site describes itself | This is a Cloudflare interstitial warning that the requested website has been reported for potential phishing, with a cookie-enablement notice and a Ray ID. No target-site content, forms, or claims are visible, so the site's purpose and legitimacy cannot be assessed. |

## Evidence status and limitations


Evidence completeness: Complete

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

| Check | Result | Status |
| --- | --- | --- |
| Malware engines | 12 marked it malicious (VirusTotal) | Risk |
| Google Safe Browsing | Not listed (Google) | Clear |
| Abuse reports on the CDN edge address | 0% confidence (AbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observed) | Noted |
| First seen | 9 months before capture (Web archive; a site on pages.dev has no registration of its own) | Watch |
| Web archive | Archived since 2026 (2 snapshots; the archive has almost no record of this site, which counted against it) | Watch |
| Certificate | Encrypted connection (Issued by WE1) | Noted |

## The page as captured


![Screenshot of the syncreconfig.pages.dev homepage captured during the TrustSniffer assessment](https://trustsniffer.com/outputs/syncreconfig.pages.dev/screenshots/first.png)

_What syncreconfig.pages.dev served when TrustSniffer captured it on 2026-11-06. 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, Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.


### Overview

This website is a subdomain hosted on a free developer-publishing platform, and an automated visit could not reach any of its own content. Instead, the visit was met by a security interstitial headed "Suspected Phishing", which states that the site has been reported for potential phishing. The captured page has no products, forms, links, branding or business claims, so the site's purpose and monetisation model cannot be established. The only substantive evidence about it is the warning itself, together with the external threat detections recorded against it.


### Scam/Impersonation Risk

The principal finding is a **confirmed blacklist-level reputation failure**. A large cluster of independent security engines classify the site as malicious, including two tier-one vendors. This is reinforced by the platform-level phishing warning shown in place of the content, and the site's own archive history carries a known-phishing marker. No weaker explanation fits this pattern. The detections are numerous, independent and consistent with the phishing warning, so the site is treated as an active phishing or malware-distribution risk. Two secondary indicators point the same way. The hostname closely resembles the name of the hosting platform's own domain, which is a typical lookalike tactic, but this is not confirmed as impersonation of a specific brand. The sandbox also recorded unusually heavy page-structure churn after interaction and repeated console errors, which is more consistent with scripted or cloaked content than with a stable, ordinary website. No conflicting legal identities appear, because no identity content was reachable. The absence of a visible login form on the captured page is not reassuring, since that page is only the warning screen and not the underlying site.
_A console error is a technical error message that the page's own code reported inside the browser while it ran. It describes how the page is built, and on its own it is not proof that the site is harmful._

Evidence:
- Homepage capture: the page title and body text are a platform "Suspected Phishing" warning stating that the site has been reported for potential phishing, with no target-site content behind it.
- External reputation: twelve security engines flag the site as malicious and two as suspicious, including two tier-one vendors, which triggered the maximum-severity reputation cap.
- Domain provenance: the domain is about 0.7 years old (roughly 259 days), and the web archive holds only 2 snapshots (first seen February 2026, last seen June 2026, 1 year tracked), so there is no established history to offset the detections.
- Browser behaviour: across three sandbox runs, 1,508 DOM mutations after interaction, 12 console errors and 83 external fetch requests were observed.

### Regulatory Verification Notes

The captured page discloses no operator, company name, registration number, licence or jurisdiction, so no regulatory standing can be inferred. The real-world operator identity remains unverified, and a free platform subdomain gives no independent link to any accountable legal entity. This is a verification gap, not evidence of wrongdoing on its own. It matters here because it removes any mitigating context for the reputation findings. No broker-database match exists for the site, so there is no third-party regulatory reputation signal to weigh either way. The sound technical hygiene that is present (a valid, long-dated certificate and ordinary hosting) shows only that the site is technically reachable, not that it is legitimate.

Evidence:
- Homepage capture: no legal entity, address, licence authority or registration number appears anywhere on the retrieved page.
- Transport security: a domain-validated TLS certificate issued by WE1, valid to 2027-01-02, which confirms encryption but not the operator's identity.
- Hosting: served from AS13335 (Cloudflare, Inc., US).
- Broker reputation lookup: no match, so no regulatory or complaint context exists.

### What to Verify Next

Because the reputation findings are decisive, the practical task is to establish whether the site has been cleaned or was the intended threat, not to establish its credentials. Anyone who received this address through a message, advertisement or QR code should trace it back to the sender and confirm through an independent, offline channel that the sender actually issued it. Organisations expecting to deal with a named company should obtain that company's official domain from a source they already trust, such as a prior contract, a registry entry or a known phone number, and compare it character by character with this hostname. Security teams should block the hostname at the gateway and check logs for earlier visits or credential entries from staff.

Evidence:
- Homepage capture: the platform warning is the only content returned, so no on-site contact channel or identity can be confirmed.
- External reputation: the detections are current and numerous, so any claim that the site is safe should be treated as unsupported until independent engines stop flagging it.
- Hostname review: the name does not correspond to any recognisable brand and shares the hosting platform's domain suffix.

### Summary Verdict

The overall posture is **high risk**. Strong, converging reputation detections and the platform phishing warning outweigh every neutral technical signal, and nothing on the site's own pages demonstrates legitimacy or a verified operator. The site is assessed as a probable phishing or malicious-content vector.


### Infrastructure Integrity

The site is fronted by Cloudflare's CDN and WAF, and every observed address is a Cloudflare edge server, so the true origin host was not observable. The certificate is valid and the shared infrastructure carries no abuse reports of its own. These are mitigating facts only. Protective infrastructure cannot offset the external threat detections, and a free platform tenant on shared edge servers can change its content quickly without any change to this infrastructure picture.


### Closing Assessment

The site should not be used for login, credential entry, payments or any financial interaction, and nothing should be downloaded from it. If it has already been opened, any credentials entered should be changed immediately and the incident reported to the organisation's security team.


_Written analysis generated 2026-11-06 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 and history in the web archive.

### 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`)
- The browser raised a warning while loading the page. (Page content `rule:PAGE_BROWSER_FLAGS_SUSPICIOUS`)

### 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`)

## Identity verification


| Field | Value |
| --- | --- |
| Status | UNVERIFIED |

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

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

## Domain intelligence


| Field | Value |
| --- | --- |
| Registrar | Not available |
| Hosting | CLOUDFLARENET - Cloudflare, Inc. |
| Network registered in | US |
| Server IP | 2606:4700:310c::ac42:2c83 (a CDN edge address; the server behind it was not observed) |
| Name servers | Not available |
| CDN / edge network | Detected (cloudflare) |
| Resolved IP addresses | 4 |
| Edge IP addresses | 4 |
| Likely origin IP addresses | 0 |
| SSL issuer | WE1 |
| SSL expiry | 2027-01-02 |
| First seen (web archive) | 260 days before capture; a site on pages.dev has no registration of its own |
| Domain expiry | Not available |
| Archive first seen | 2026-02-19 (260 days before capture) |
| Archive snapshots | 2 |
| Reputation | VirusTotal: 12 malicious \| AbuseIPDB (CDN edge address, not the host): 0% confidence, 0 reports \| Google Safe Browsing: 0 matches |

## About this assessment


**Was this report useful?** Tell other people what you think of TrustSniffer, good or bad. An honest review helps others decide whether to rely on these checks. [Review TrustSniffer on Trustpilot](https://www.trustpilot.com/review/trustsniffer.com)

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

## Related on TrustSniffer
- [Every website and wallet TrustSniffer has assessed](https://trustsniffer.com/directory), the full risk directory
- [Check another website](https://trustsniffer.com/web-intelligence), run a new assessment
- [Check a crypto wallet address](https://trustsniffer.com/on-chain-risk), on-chain screening
- [The TrustSniffer Risk Index](https://trustsniffer.com/stats), how this verdict compares

## Guides
- [How to Report a Scam Website: Who to Tell and Why](https://trustsniffer.com/blog/how-to-report-a-scam-website)
- [Scam Website Statistics: Inside Our Data](https://trustsniffer.com/blog/scam-website-statistics-trustsniffer-data)
- [What Are Website Trust Signals?](https://trustsniffer.com/blog/website-trust-signals-explained)

---
*Source: [TrustSniffer](https://trustsniffer.com/report/syncreconfig.pages.dev), independent automated trust & fraud analysis. Cite as https://trustsniffer.com/report/syncreconfig.pages.dev · assessed 2026-11-06.*
