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

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

halrecovery.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 70%.

What the captured page showedThe page is a Cloudflare warning interstitial stating the requested site was reported for potential phishing. No site content is visible, so the site's purpose cannot be assessed.

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 (Google Safe Browsing, cloudflare_warning, VirusTotal, a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-25)). 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 (70%) 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 engines11 marked it malicious, 1 suspiciousVirusTotal; Fortinet, Google, Sophos among the engines that flagged itRisk
Google Safe BrowsingListed as unsafeGoogleRisk
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
First seen5 months before captureWeb archive; a site on pages.dev has no registration of its ownRisk
Web archiveArchived since 20265 snapshotsClear
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

https://halrecovery.pages.dev/
Screenshot of the halrecovery.pages.dev homepage captured during the TrustSniffer assessment
What halrecovery.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.
  • 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

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

Overview

halrecovery.pages.dev is a tenant address on Cloudflare's pages.dev hosting platform, not a standalone registered domain. When TrustSniffer captured it on 13 November 2026, it returned only Cloudflare's "Suspected Phishing" warning interstitial, not any content of its own. The page shows no products, services, forms or business information. The site's purpose and monetization model therefore could not be determined from the capture. What is observable is that the address was flagged as a phishing risk and presented no operator identity.

Scam/Impersonation Risk

Confirmed contradictory signals are present. The sources that confirm the listing are Google Safe Browsing, Cloudflare's own warning page, VirusTotal and a threat-intelligence listing. As of the 13 November 2026 capture, Google Safe Browsing listed the address for social engineering, and Cloudflare's interstitial stated the site "has been reported for potential phishing". VirusTotal reported 11 engines as malicious and 1 as suspicious, with Fortinet, Google and Sophos among those that rated it malicious. A threat-intelligence listing classes the site as a phishing actor, last seen on 25 October 2026. The listing carries the actor role, so it identifies the site as the source of phishing rather than a victim. The convergence of these sources makes this a confirmed listing. No conflicting legal-entity names were observed, so no identity contradiction exists. The risk rests on the confirmed phishing listings. The captured page was Cloudflare's warning, so the requests and console messages recorded during capture belong to that warning page and are not evidence of the site's own behaviour. No login or data-entry form was seen on the captured page.

Evidence
  • Search-reputation alert: Google Safe Browsing listed the address for social engineering as of the 13 November 2026 capture.
  • Multi-engine scan: 11 engines malicious and 1 suspicious, with Fortinet, Google and Sophos among the vendors rating it malicious.
  • Homepage capture: Cloudflare's interstitial stated the site "has been reported for potential phishing" and defined phishing as a site that "attempts to steal sensitive information by falsely presenting as a safe source".
  • Web archive: 5 snapshots from 3 June 2026 to 16 June 2026 (a 13-day span); the address was first seen in the web archive 163 days before capture.

Regulatory Verification Notes

On the only page read, the homepage, which was the warning interstitial, no contact channels and no terms or privacy disclosures were present. These are the disclosures an informational site would normally make, and they are absent on the pages read. The captured page also gave no legal entity, licence claim or registration number. Because the address is a tenant of a hosting platform, it has no domain registration of its own, and the operator's real-world identity is unverified. No third-party broker or regulator record was matched for the name. This is a verification finding, separate from the phishing listings above.

Evidence
  • Homepage (warning interstitial): no contact channels, terms or privacy content on the pages read.
  • Hosting record: the address is served from AS13335 (Cloudflare, Inc., US) as a pages.dev tenant.
  • Transport encryption: a DV certificate issued by WE1, valid to 2027-01-05. This confirms only encryption, not who operates the site.
  • Broker reputation dataset: no match found for the site.

What to Verify Next

The listings were last seen on 25 October 2026, and the address was captured on 13 November 2026. Any later change in its status should be checked directly with the original listing providers before any reassessment. Anyone who reached the address through a message, advertisement or recovery-service offer should confirm the sender's identity by an independent route, using a contact channel obtained from a source other than that message. Confirming whether the sender or business holds the licence or registration it claims should be done only with the relevant public registry, using details not supplied by the sender.

Evidence
  • Homepage capture: the page displayed Cloudflare's warning and no business details, so there is nothing on the site to verify against.
  • Reputation listings: the aligned alerts date from the 13 November 2026 capture, and the last threat listing was seen on 25 October 2026.
  • Registration lookup: the address has no registration of its own, so there is no registrant record to confirm.

Summary Verdict

This address is assessed at critical risk. Aligned external alerts classify it as a phishing source, and the site offered no content or accountable operator identity that could counter them. Its encryption certificate is valid, but that does not establish who operates the site or that it is legitimate.

Infrastructure Integrity

The address resolves to four Cloudflare edge IP addresses, and no origin server address was observable. A check of the host address's abuse record found no reports. Edge hosting is neutral here: it neither mitigates nor aggravates the findings, and it provides no evidence of legitimacy.

Closing Assessment

Treat this address as a critical risk. Do not engage with it, and do not act on any message, advertisement or recovery-service offer that directed a visitor to it.

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

What the analysis found

5 findings contributed to this verdict, raised by page content, external reputation, several checks together, hosting and network, 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

  • Google Safe Browsing and 11 VirusTotal engines 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 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

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

  • The request stayed on halrecovery.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2026-06-03. 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:2fcc (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 issuerWE1
SSL expiry2027-01-05
First seen (web archive)163 days before capture; a site on pages.dev has no registration of its own
Domain expiryNot available
Archive first seen2026-06-03 (163 days before capture)
Archive snapshots5
ReputationVirusTotal: 11 malicious, 1 suspicious | AbuseIPDB (CDN edge address, not the host): 0% confidence, 0 reports | Google Safe Browsing: 1 match

About this assessment

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

Is halrecovery.pages.dev a scam?

TrustSniffer's assessment of halrecovery.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 halrecovery.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 halrecovery.pages.dev?

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