Is claim-pepeheimer-portal.pages.dev a scam? TrustSniffer's critical-risk assessment: 0/100

claim-pepeheimer-portal.pages.dev

Is it safe to use? When the evidence was captured, Cloudflare showed its own warning page in place of this site, and external threat listings named it as malicious. Do not pay or share personal details with this site.

Download PDF Check another site How we score
Ask your AI about this report

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

Verdict

When the evidence was captured, Cloudflare showed its own warning page in place of this site, and external threat listings named it as malicious. Do not pay or share personal details with this site.

0 OUT OF 100
Critical Risk

claim-pepeheimer-portal.pages.dev shows critical-risk indicators.

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.

Evidence captured 2026-11-13, re-scored 2026-11-14 by automated analysis. Evidence confidence 55%.

What the captured page showedThe captured page is a Cloudflare 'Suspected Phishing' warning stating that the site has been reported for potential phishing. It contains no service description, forms, legal identity, contact details or policies for the underlying site.

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-13 and re-scored on 2026-11-14. The certificate, the registration age and the page content describe the site as it was on 2026-11-13.
  • External threat sources confirmed a listing for this site when the evidence was captured (cloudflare_warning, VirusTotal, a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-26)). It was not re-queried for this version. On its own it would limit the score to at most 10; the score is lower because of the other findings below.
  • When captured, this address served Cloudflare's own warning page instead of the site, so the site's own content was not captured; Cloudflare's warning is itself the evidence.
  • 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 (55%) 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 scoreThe findings belowThe confirmed external listing ceiling (at most 10) and the threat-listing ceiling (at most 5) also apply, but the findings brought the score lower.Watch
Malware engines9 marked it malicious, 1 suspiciousVirusTotal; Fortinet, Sophos among the engines that flagged itRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address0% confidenceAbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
Domain ageNot availableNo registration record was returnedNoted
Web archiveNever archivedNo public history of this siteWatch
CertificateEncrypted connectionIssued by YE1Noted

The page as captured

https://claim-pepeheimer-portal.pages.dev/
Screenshot of the claim-pepeheimer-portal.pages.dev homepage captured during the TrustSniffer assessment
What claim-pepeheimer-portal.pages.dev served when TrustSniffer captured it on 2026-11-13. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Security Alert

9 VirusTotal engines, including Fortinet, Sophos, marked this site as malicious; independent sources confirm a listing for this site.

Overview

The address claim-pepeheimer-portal.pages.dev is a subdomain on the pages.dev hosting platform, so it has no registration of its own. When captured on 13 November 2026, it served Cloudflare's "Suspected Phishing" warning page instead of any content from its operator. The page showed no products, forms, pricing or business description, so its commercial purpose could not be read from the page. The wording of the address presents it as a "claim" portal. The domain name contains the word "pepeheimer", but the site is not a known brand and nothing on the captured page ties it to one.

Scam/Impersonation Risk

This site is assessed as a critical risk. The page captured on 13 November 2026 was Cloudflare's own warning, which states that the website "has been reported for potential phishing". It also defines phishing as a site that tries "to steal sensitive information by falsely presenting as a safe source" (quoted from the page). An independent threat-intelligence listing classifies the site as a source of phishing, and it was last seen on 26 October 2026. An engine-aggregation service flagged it as malicious, including two leading security vendors. Three separate sources therefore agree: the Cloudflare warning, the aggregation service and the threat-intelligence listing. This meets the bar for a confirmed listing. The score is the sum of the scored findings: the Cloudflare phishing interstitial, the confirmed external listing, a high-risk reading across several analysis modules, and an incomplete registration record. No single alert is the sole driver. No brand impersonation or conflicting legal identities were observed. The capture was a warning page, so the page's requests and structure are not evidence of the operator's own behaviour. The page showed no login or payment form, so what it would ask of a visitor is unknown.

Evidence
  • Cloudflare warning page (the captured homepage): displayed "Suspected Phishing" and "This website has been reported for potential phishing", with no site content behind it.
  • VirusTotal results: 9 engines rated the address malicious and 1 suspicious, including Fortinet and Sophos.
  • Threat-intelligence listing: classified the site as a phishing source, with the listing last seen 2026-10-26.
  • Homepage capture: no forms were present (0 forms seen), and no sensitive data collection was observed.

Regulatory Verification Notes

On the only page read, the homepage, which was the Cloudflare warning, no contact channels and no terms or privacy policy were present. Both are disclosures a site of this type is expected to make. This reflects what was captured, not a finding about pages that were not read. No licence or regulatory registration was claimed, and no regulated status was found. No third-party broker profile matched. The operator's real-world identity is unverified, and the registration record shows incomplete owner details, which is a scored finding. The site lies on the pages.dev platform, so no domain registration of its own was found, and its first appearance cannot be dated from registration data. Nothing on the pages read supports a legitimacy claim.

Evidence
  • Homepage: no contact channels and no terms or privacy policy appeared on the page read.
  • Registration record: owner details were incomplete, and the address sits under the pages.dev hosting platform.
  • Transport encryption: the TLS certificate seen at capture was issued by YE1 (DV, domain-validated only) and valid to 2027-01-11. A DV certificate proves control of the domain, not the operator's identity.
  • Hosting: served from AS13335 (Cloudflare, Inc., US).

What to Verify Next

The address should not be treated as the official portal of any project or token until that project confirms it through its own channels. Anyone who arrived by a message, post or advertisement promising a "claim" should trace the link back to its sender and confirm it with the sender by another route. Any project that is named should be asked directly, through channels not published on this address, whether the portal exists. If the address was opened and anything was entered or approved there, the affected accounts and any approvals made should be reviewed.

Evidence
  • Homepage capture: no ownership, contact or policy information was present on the page read to check against.
  • Threat-intelligence listing: the phishing classification was last seen 2026-10-26, so the address was already flagged before the capture.
  • Cloudflare warning page: the notice appeared in place of site content, so nothing the operator published could be assessed.

Summary Verdict

The site sits at the bottom of the trust scale and is a critical risk. The evidence supports a clear conclusion of phishing risk, with confirmed warnings from several independent sources. No legitimate operator identity, business purpose or accountability could be established to offset them.

Infrastructure Integrity

The site was served from the Cloudflare edge network across four edge addresses, and no separate origin server was observed. The host address's abuse record was checked and showed no reports. Hosting through Cloudflare is neutral here, since it says nothing about who operates the site and does not offset the phishing warnings or the confirmed listing.

Closing Assessment

The address should not be visited or interacted with. Anyone directed to it should disregard the message that sent them and go only to the project's verified channels.

Written analysis generated 2026-11-14 by the TrustSniffer Analysis Engine from the evidence in this report.

What the analysis found

4 findings contributed to this verdict, raised by page content, external reputation, several checks together, and registration and ownership.

When captured, this address served Cloudflare's own warning page instead of the site, so the site's own content was not captured; Cloudflare's warning is itself the evidence.

01 Page content

  • When the evidence was captured, Cloudflare showed its own warning page in place of this site, telling visitors the site had been reported as harmful.Page content rule:PAGE_CF_PHISHING_INTERSTITIAL

02 External reputation

  • 9 VirusTotal engines, including a leading vendor (Fortinet, Sophos), marked this domain as malicious when the evidence was captured, which TrustSniffer counts as a confirmed external listing.External reputation rule:EXT_BLACKLIST_CRITICAL

03 Several checks together

  • Several independent checks pointed to risk at the same time.Several checks together rule:HYB_MULTIPLE_MODULES_HIGH_RISK

04 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

Identity verification

StatusUNVERIFIED

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.

What TrustSniffer observed

First-party facts recorded during the assessment of claim-pepeheimer-portal.pages.dev.

  • The request stayed on claim-pepeheimer-portal.pages.dev. It was not redirected to another domain. Clear
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:310c::ac42:2fa3 (a CDN edge address; the server behind it was not observed)
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerYE1
SSL expiry2027-01-11
First seen (web archive)Not available (the web archive has no record of this address; a site on pages.dev has no registration of its own)
Domain expiryNot available
Archive first seenNot available
Archive snapshots0
ReputationVirusTotal: 9 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 claim-pepeheimer-portal.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.

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 claim-pepeheimer-portal.pages.dev

Is claim-pepeheimer-portal.pages.dev a scam?

TrustSniffer's assessment of claim-pepeheimer-portal.pages.dev found strong scam indicators. It scored 0 out of 100 on 2026-11-14, which is the critical-risk band. The specific signals are listed in the evidence above.

Is claim-pepeheimer-portal.pages.dev safe to use?

When the evidence was captured, Cloudflare showed its own warning page in place of this site, and external threat listings named it as malicious. Do not pay or share personal details with this site.

What is the trust score of claim-pepeheimer-portal.pages.dev?

claim-pepeheimer-portal.pages.dev scored 0 out of 100 on 2026-11-14, which places it in the critical-risk 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.
Questions about this report? Ask your AI

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-11-14 · how we assess · report a mistake