Website trust intelligence

Is customer-sp-brantison1.pages.dev legit? Trust check & scam signals

Shoppers often look up “customer-sp-brantison1.pages.dev legit”, “customer-sp-brantison1.pages.dev scam”, or whether a site is phishing before handing over passwords or payments. Fraudly summarizes what public scam feeds, phishing heuristics, SSL behavior, registration context, and model-friendly trust indicators say about customer-sp-brantison1.pages.dev—presented calmly so you can triage risk quickly, then drill into receipts if you choose.

The answers below clarify how to read Fraudly’s signals. After that you’ll find the structured scan—risk scores, corroborating sources, expandable technical notes. Nothing here is legal advice, credit guidance, or a guarantee of safety—when in doubt pause the transaction and contact the brand via an official route you sourced separately.

Context, not certainty. Fraudly summarizes signals from public scam intelligence, phishing heuristics, and technical lookups. Fraudsters rotate infrastructure quickly—combine this page with official support channels before high-value decisions.

Trust-style score
59 / 100
Domain age (days)
SSL / HTTPS
HTTPS available — encrypts transit, does not prove legitimacy

Common questions before you trust customer-sp-brantison1.pages.dev

Fraudly aligns with informational searches—“is this site legit?”—without pretending to adjudicate legitimacy in a legal sense. Use each answer alongside the scan below.

Is customer-sp-brantison1.pages.dev legit?

Fraudly doesn’t certify sites as “legit.” This page combines automated checks and public scam intelligence around customer-sp-brantison1.pages.dev into a readable snapshot. Higher trust-style readings mean fewer negative signals surfaced in Fraudly’s model—not proof the business is trustworthy. Always verify payment pages, refunds, reviews on independent channels, and official branding before sharing money or passwords.

Is customer-sp-brantison1.pages.dev a scam?

A single automated scan cannot prove fraud. Fraudly flags patterns often seen with phishing sites, dubious shops, malware distribution, or impersonation when matching data exists. Treat strong risk indicators as reasons to pause, use official contact methods, and double-check URLs—not as a courtroom conclusion about customer-sp-brantison1.pages.dev.

Can I trust customer-sp-brantison1.pages.dev for online shopping or logins?

Use this report as guardrails alongside your judgment: look for mismatched branding, unrealistic prices, urgency tactics, unfamiliar payment rails, broken policies, or requests to bypass normal checkout. Fraudly summarizes technical and feed-based context for customer-sp-brantison1.pages.dev so you can decide whether to investigate further—not whether to blindly trust checkout forms.

How does Fraudly detect phishing-like behavior for customer-sp-brantison1.pages.dev?

Fraudly layers SSL inspection, hostname and registration context, phishing and malware intel where available, and textual risk scoring from reachable content. Signals are probabilistic—attackers imitate trusted brands. When customer-sp-brantison1.pages.dev aligns with curated threat lists or heuristic risk patterns, that context appears in the breakdown below so you understand “why Fraudly surfaced concern.”

What does Fraudly mean by a “trust-style score”?

The score summarizes model-friendly trust indicators versus risk cues for customer-sp-brantison1.pages.dev. It is not a banking risk rating or endorsement. Threat overrides (for example Tier‑1 malware lists) may change how the headline reads even when ancillary metrics look middling—always review the explanatory sections underneath the headline.

How often should I recheck customer-sp-brantison1.pages.dev?

Websites and scam infrastructure change rapidly. Fraudly refreshes caches periodically—run a fresh check from the homepage before high-stakes actions. If fraud reports spike for looks-like domains nearby customer-sp-brantison1.pages.dev, re-verify you are still on the exact hostname you scanned.

Structured scan & evidence

Expand sections for technical receipts, phishing-adjacent language cues, corroborating sources, reviews when reachable, and limitations of each data feed.

Limited public information available

No confirmed malicious indicators were detected. Public data availability was limited in this scan, which affects context completeness but is not a risk signal.

Some caution advised

The website responded, but some page details could not be fully inspected during this scan.

Website responded, but some page details could not be fully inspected during this scan.

This website has mixed trust signals. It may still be legitimate, but some indicators are worth a closer look before you pay or sign in.

Online risks can change over time. Always use your own judgment before purchasing or sharing personal information.

Some caution advised

Trust score

59 / 100

04979100

The trust score combines technical checks, reputation signals where available, website history cues, scam intelligence, and AI-assisted analysis.

Higher scores usually mean fewer red flags appeared in this snapshot—not proof a site is safe or unsafe.

Reputation & public trust

Public review and reputation signals can help provide context, but they are not a guarantee that a website is safe.

Positive review signals can support trust, but reviews can be incomplete or manipulated.

Trustpilot

No public review profile found in this scan.

Google Reviews

No review snapshot available in this scan.

Why we say this

Positive signals

  • No Police page string match
  • RDAP lookup failed
  • Google Safe Browsing not configured

Extra context

  • Some public reputation data was limited. This affects extra context, not direct risk.

Website checked

customer-sp-brantison1.pages.dev

Detailed scan findingsTechnical notes, redirects, list matches, reputation snapshots, and model details — open when you want the full picture.

Signals behind your score

Be careful / Caution

Availability: limited_inspection · Website responded, but some page details could not be fully inspected during this scan. (HTTP 403)

Inspection: blocked · dns=true · tls=true · botProtection=true · parserFailure=false · contentLength=5072

Matches from scam intelligence

Structured hits from curated phishing, malware, or police-aligned feeds in this crawl.

No Safe Browsing, OpenPhish, URLhaus, or police-aligned list matches were returned in this crawl.

Detected risk patterns

Extra risk-style signals scored in this snapshot. They are not definitive proof—a quick second opinion still helps.

No additional prioritized risk rows were raised beyond curated list matches.

Helpful signals & observations

Facts and neutral checks that balance the picture. Missing a row usually means “not seen”, not proof either way.

  • No Police page string match

    No direct domain string overlap was detected in lightly cached excerpts of the referenced politie.nl pages. Missing a hit is not proof a shop is trustworthy.

    Source: Dutch Police (public pages)Source reliability: low
  • RDAP lookup failed

    HTTP 400

    Source: RDAP (rdap.org)Source reliability: low
  • Google Safe Browsing not configured

    No API key is set, so threat matches cannot be requested.

    Source: Google Safe BrowsingSource reliability: high
  • No OpenPhish match found in this snapshot

    No overlapping entry was found in the fetched OpenPhish feed for this check window. This does not prove the site is safe.

    Source: OpenPhishSource reliability: medium
  • URLhaus unavailable

    HTTP 401

    Source: URLhausSource reliability: low
  • HTTPS is available

    HTTPS is available. This protects the connection, but does not verify that the site is legitimate. Issuer: Google Trust Services. Expiry: 2026-08-06T07:04:20.000Z.

    Source: TLS certificate checkSource reliability: high

Domain & registration

  • Checked URL/hostname: customer-sp-brantison1.pages.dev
  • Registered domain: customer-sp-brantison1.pages.dev
  • Registration date: unknown
  • Domain age (days): unknown
  • Registrar: unknown
  • Country: unknown
  • Expiration date: unknown
  • Privacy / redacted ownership hints: no / unknown

Source: RDAP (rdap.org)

Redirect analysis

  • Original URL: https://customer-sp-brantison1.pages.dev/
  • Final URL: https://customer-sp-brantison1.pages.dev/
  • Final domain: customer-sp-brantison1.pages.dev
  • Redirect count: 0
  • Crossed registrable domain: no

Security checks (HTTPS / certificates)

  • HTTPS/TLS reachable: yes
  • Certificate trusted in probe: yes
  • Possibly self-signed / untrusted: no / unknown
  • Issuer: Google Trust Services
  • Expiry: 2026-08-06T07:04:20.000Z

Source: TLS certificate check

Scam intelligence sources

Normalized provider output. “Matched” means that source reported something relevant in this run.

  • No Police page string matchgovernmentno match

    No direct domain string overlap was detected in lightly cached excerpts of the referenced politie.nl pages. Missing a hit is not proof a shop is trustworthy.

    Source: Dutch Police (public pages) · severity: info · reliability: low

  • RDAP lookup faileddomainno match

    HTTP 400

    Source: RDAP (rdap.org) · severity: info · reliability: low

  • Google Safe Browsing not configuredmalwareno match

    No API key is set, so threat matches cannot be requested.

    Source: Google Safe Browsing · severity: info · reliability: high

  • No OpenPhish match found in this snapshotphishingno match

    No overlapping entry was found in the fetched OpenPhish feed for this check window. This does not prove the site is safe.

    Source: OpenPhish · severity: info · reliability: medium

  • URLhaus unavailablemalwareno match

    HTTP 401

    Source: URLhaus · severity: info · reliability: low

  • HTTPS is availablesslno match

    HTTPS is available. This protects the connection, but does not verify that the site is legitimate. Issuer: Google Trust Services. Expiry: 2026-08-06T07:04:20.000Z.

    Source: TLS certificate check · severity: info · reliability: high

Reputation enrichment

Optional broader reputation pass when available—beyond the quick baseline probes.

No enriched reputation profile surfaced. That limits context; it does not prove the site is unsafe.

Quick review probes (baseline scan)

Lightweight directory checks powering part of the model—hiccups here describe our snapshot, not the shop’s honesty.

Public review data unavailable for this check.

  • No public review profile was found. This limits confidence but does not prove the site is unsafe.

No public reviews available; the site has been flagged for phishing.

  • Public review data unavailable for this check.
Source availability (neutral)
  • Third-party Trustpilot snapshot: snapshot unavailable in this crawl (limits confidence only).
  • Indexed review snippets probe: snapshot unavailable in this crawl (limits confidence only).

Raw review snapshots

Trustpilot raw snapshot: not available in current payload.

Google reviews raw snapshot: not available in current payload.

Fulfillment signals

Dropshipping: unlikely · China-linked fulfillment: unlikely · Local stock/production: unlikely · Confidence: low · Score nudge: 0

  • No strong supply-chain signals detected in snippet.
Scoring detail (advanced)

Composite model uses raw impacts × confidence weights on the server. Positive numbers push the risk score up; negative numbers pull it down. Neutral rows are explanatory only — they must not be read as endorsement.

Applied trust-score cap after identity guardrails: 74/100 displayed trust.

Combined scoring signals (reviews, reputation, feeds, fulfillment…)

Trust-positive signals

  • Valid HTTPS baseline (-3 raw · low confidence) — HTTPS and certificate checks looked healthy in this run. This is supportive context, not proof of legitimacy.

Website & technical observations

  • No matched Google listing (+0 raw · high confidence) — No Google Places listing matched this domain; review impact is neutral (not a penalty).

Detected risk patterns

  • Unusually long domain (+10 raw · medium confidence) — The hostname is unusually long, which is common in phishing or throwaway shops.
  • No clear business address in snippet (+15 raw · medium confidence) — Enough text was captured but no obvious physical business or return address was found.

Incomplete or unavailable data

  • Domain registration data unavailable (+1 raw · low confidence) — RDAP could not be read in this run (timeout, error, or rate limit). That limits how well we can date the domain—it is logged as limited evidence, not as proof the site is unsafe.
  • Domain ownership could not be verified from public registration data (+1 raw · low confidence) — WHOIS/RDAP did not expose corroboratable registrant signals in this crawl. That is common and mainly reduces how confidently we can score—not evidence of impersonation by itself.

Scam intelligence weighting (model)

No weighted intel contributions in this run.

Review collector notes (neutral)

Buckets distinguish provider errors, source outages, review-derived signals, and (rare) website crawler transparency—never merged with fraud intel.

  • trustpilot_public · source_unavailable: Third-party Trustpilot snapshot: snapshot unavailable in this crawl (limits confidence only).
  • google_indexed_snippets · source_unavailable: Indexed review snippets probe: snapshot unavailable in this crawl (limits confidence only).

Key factors explained

Blended notes from patterns we detected, scam intelligence scoring, and optional AI assistance—not legal or financial advice.

  • AI risk signal: high
  • The website has been flagged by Cloudflare as a suspected phishing site, indicating potential malicious intent.
  • No public review profiles were found, which limits confidence in the site's legitimacy.

AI model used in this run: yes

Fraudly summarizes public scam intelligence, reputation snapshots, and technical signals for awareness. It is not legal, financial, or flawless security advice—verify important decisions yourself.

Compact snapshot URL

Prefer sharing a shorter branded path? Fraudly exposes the identical cached analysis via fraudly.app/check/customer-sp-brantison1.pages.dev. Both URLs read the same data layer with separate editorial framing tuned for clarity vs. evergreen sharing.

Run a fresh homepage checkLatest public checksHow Fraudly worksThreat alerts feed