Verdict
External threat listings named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.
brazil-2sl.pages.dev shows critical-risk indicators.
- 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.
| How the site describes itself | The captured page displays only the message 'Application error: a client-side exception has occurred' with no navigation, content, forms, or links, so its purpose cannot be determined. |
|---|
Evidence status and limitations
Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.
- The evidence was captured on 2026-11-02 and re-scored on 2026-11-09. The certificate, the registration age and the page content describe the site as it was on 2026-11-02.
- External threat sources confirmed a listing for this site when the evidence was captured (VirusTotal, a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-24)). It was not re-queried for this version. On its own it would limit the score to at most 24; the score is lower because of the other findings below.
- 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 (64%) 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.
| What limits the score | The findings belowThe independent sources ceiling (at most 24) and the threat-listing ceiling (at most 5) also apply, but the findings brought the score lower. | Watch |
|---|---|---|
| Malware engines | 3 marked it malicious, 1 suspiciousVirusTotal | Risk |
| Google Safe Browsing | Not listedGoogle | Clear |
| Abuse reports on the CDN edge address | 0% confidenceAbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observed | Noted |
| First seen | 5 months before captureWeb archive; a site on pages.dev has no registration of its own | Risk |
| Web archive | Archived since 20262 snapshots; the archive has almost no record of this site, which counted against it | Watch |
| Certificate | Encrypted connectionIssued by WE1 | Noted |
The page as captured
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
Overview
This is a minimal web page published on a free subdomain of the Cloudflare Pages hosting platform. When captured, it showed a visitor only a generic message that a client-side application exception had occurred. It had no navigation, forms, links, title or descriptive content. No product, service or business model could be inferred from it, so its apparent purpose is undetermined.
Scam/Impersonation Risk
TrustSniffer assesses this address as critical risk, and the cause is a set of external threat indicators, not anything the page itself displayed. VirusTotal recorded 3 engines as malicious and 1 as suspicious. A separate open-source threat-intelligence listing classed the address as a phishing source, with the site in the role of actor, and last saw it on 2026-10-24. Two independent sources agree, which meets the bar for a confirmed listing. Google Safe Browsing did not list the address. No brand impersonation and no conflicting legal identities were observed, because the page named no brand or entity. The captured page had no forms, so no credential or payment collection was seen. The listing therefore reflects what the address was reported to have served, not what the capture showed. Because the page offers nothing to substantiate legitimacy, no on-page evidence offsets the external record.
- VirusTotal: 3 engines malicious and 1 suspicious at capture on 2026-11-02; Google Safe Browsing did not list the address.
- Threat-intelligence listing: classed as phishing, with the site as actor, last seen 2026-10-24.
- Homepage: the only content was the application-error message, with no forms, links or brand references.
- Web archive: first seen 2026-06-16, 139 days before capture. Two snapshots were recorded, the last on 2026-07-03, a 17-day span.
Regulatory Verification Notes
No legal, terms, privacy, about or licensing page was captured, and the homepage named no operator, company, registration number or regulator. The address sits under a shared platform subdomain and has no registration record of its own, so no operator can be tied to it. Real-world identity therefore remains unverified, and no apparent legitimacy can be asserted. No regulatory register was matched, and a broker-reputation dataset returned no record for the address. That absence is neutral context, not a finding. Because the page discloses nothing, there is nothing to cross-check against a licensing authority.
- Hosting: served from AS13335 (Cloudflare, Inc.).
- Transport encryption: the TLS certificate was issued by WE1 (domain-validated). It was valid until 2027-01-09 when seen at capture. This confirms an encrypted connection only, not who operates the site.
- Homepage: no company name, licence or registration number was displayed.
- Broker dataset: no match for the address.
What to Verify Next
Verification should start from how the address was reached. If it arrived through a message, advertisement or referral, the claimed sender should be contacted through a channel known independently of that message, such as an official phone number or a known website typed in manually. They can then confirm whether they use this address. No operator can be established from the address itself. If a business later claims to run it, any licence it cites should be checked directly with the relevant regulator's public register, not through anything the site publishes.
- Homepage: no outbound links or contact channels were captured, so no route to an operator could be derived from the page.
- Page behaviour: three sandbox runs recorded 35 browser console errors, consistent with the application failure. The page exposed no working feature to assess.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.
- Identity: no operator, brand or person was named, so any identity claim must come from outside the site.
Summary Verdict
TrustSniffer assesses this address as critical risk. External threat intelligence converges with a page that offers no verifiable content and an operator who cannot be identified. The address's technical hygiene does not change this assessment.
Infrastructure Integrity
All four addresses observed for the site were Cloudflare edge addresses, and the host address's abuse record showed no reports. The CDN is neutral. It neither raises nor lowers the risk, and it does not indicate where or by whom the content is actually run.
Closing Assessment
The address should not be used, and links pointing to it should not be followed. Anyone who was directed to it by a message or advertisement should treat that source as suspect and report it to the platform or channel where it appeared.
Written analysis generated 2026-11-09 by the TrustSniffer Analysis Engine from the evidence in this report.
What the analysis found
8 findings contributed to this verdict, raised by external reputation, history in the web archive, page content, hosting and network, registration and ownership and behaviour in a sandbox.
01 External reputation
- 3 VirusTotal engines marked this domain as malicious when the evidence was captured.External reputation
rule:EXT_BLACKLIST_HIGH
02 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
03 Page content
- The page has very little readable content.Page content
rule:PAGE_CONTENT_THIN - The page has no title, which almost every website sets.Page content
rule:PAGE_TITLE_MISSING - The browser raised a warning while loading the page.Page content
rule:PAGE_BROWSER_FLAGS_SUSPICIOUS
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
05 Registration and ownership
- As a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site).Registration and ownership
rule:KF_WHOIS_INCOMPLETE
06 Behaviour in a sandbox
- The page produced an unusually high number of errors while it ran.Behaviour in a sandbox
rule:BEHAV_CONSOLE_ERRORS_HIGH
Identity verification
| 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 brazil-2sl.pages.dev.
- The request stayed on brazil-2sl.pages.dev. It was not redirected to another domain. Clear
- The earliest public archive of this site is from 2026-06-16. Watch
- It is hosted on CLOUDFLARENET, a network registered in US. Noted
Domain intelligence
| Registrar | Not available |
|---|---|
| Hosting | CLOUDFLARENET - Cloudflare, Inc. |
| Network registered in | US |
| Server IP | 2606:4700:310c::ac42:2c4e (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-09 |
| First seen (web archive) | 139 days before capture; a site on pages.dev has no registration of its own |
| Domain expiry | Not available |
| Archive first seen | 2026-06-16 (139 days before capture) |
| Archive snapshots | 2 |
| Reputation | VirusTotal: 3 malicious, 1 suspicious | 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 brazil-2sl.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.