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

yrrhh.pages.dev

Is it safe to use? External threat listings named this site as malicious when the evidence was captured. 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

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

0 OUT OF 100
Critical Risk

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

Assessed 2026-11-10 by automated analysis. Evidence confidence 75%.

How the site describes itselfBlockchain Guildhall is a wallet-connection hub that asks visitors to Connect Wallet and lists airdrop, claim, recovery, migration and transaction-troubleshooting roles. It names no operator, legal entity, contact channel or risk disclosure, and its 'verified' claim is unsupported, so the wallet-connection step is high-stakes with proof missing.

Evidence status and limitations

Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.

  • 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-25)). 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 (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.

What limits the scoreThe findings belowThe confirmed external listing ceiling (at most 24) and the threat-listing ceiling (at most 5) also apply, but the findings brought the score lower.Watch
Malware engines12 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
First seen5 months before captureWeb archive; a site on pages.dev has no registration of its ownRisk
Web archiveArchived since 20262 snapshots; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

https://yrrhh.pages.dev/
Screenshot of the yrrhh.pages.dev homepage captured during the TrustSniffer assessment
What yrrhh.pages.dev served when TrustSniffer captured it on 2026-11-10. 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

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

Overview

Blockchain Guildhall is a single-purpose web3 landing page published on a free pages.dev subdomain. It presents itself as a hub of "guilds" and asks visitors to Connect Wallet and "Sign in to get started". Its listings are themed around token claims, airdrops, wallet recovery, migration, transaction reversal and wallet-error troubleshooting. It names no product, operator or revenue model. Its apparent function is to move visitors toward connecting a crypto wallet.

Scam/Impersonation Risk

The site carries critical risk. Its address has a confirmed listing, confirmed by two independent sources: VirusTotal and a separate threat-intelligence listing. A large number of antivirus engines, including two leading security vendors, flagged it as malicious. The threat-intelligence listing classifies it as phishing and places the site in the role of the actor, last seen on 25 October 2026. Google Safe Browsing did not list it, but that does not offset the other two sources. The page content points the same way. Its categories ("Claim Token", "Airdrop", "Recovery", "Revoke TXN", "Hard Reset", "Wallet Error") are classic lures aimed at people who believe they have a stuck transaction, an unclaimed token or a locked wallet. Each such lure ends in the same step, connecting a wallet. The scale figures beside each category (for example "867K" beside Airdrop and "647K" beside Claim Token) are the site's own unsupported numbers. The "Explore verified guilds" banner gives no verifier or method, so the "verified" claim is unsupported. The domain is a tenant subdomain on the pages.dev hosting platform, and the site is not that platform. Observed behaviour adds to the concern. The page sent a large volume of requests to other hosts, many to destinations TrustSniffer does not recognise. It produced an extreme number of console errors, and its structure changed heavily after interaction. These behaviour findings count toward the score. No impersonation of a specific brand and no conflicting legal identities were found. Identity is only likely and is not verified: the homepage uses the name "Guildhall", and the connection page carries a different label.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
  • Web archive record: first seen 2026-06-03, 160 days before capture, with 2 snapshots between 2026-06-03 and 2026-06-16 (a 13-day span). The site has no registration of its own because it sits on a hosting platform.
  • VirusTotal: 12 engines malicious and 1 suspicious, including Fortinet and Sophos. A threat-intelligence listing separately classifies the site as phishing in the actor role, last seen 2026-10-25.
  • Homepage: lists categories such as Airdrop (96 roles), Claim Token (87 roles), Recovery (4 roles), Staking and Bridge Transfer, all behind a single "Connect Wallet" prompt. It asserts "verified guilds" without any verification method.
  • Behavioural capture: 55 requests sent data to other hosts, 34 of them to destinations TrustSniffer does not recognise, with 6,323 console errors recorded across 3 runs.

Regulatory Verification Notes

The site claims no licence, registration or regulatory standing, and no third-party regulatory record was matched. This is a verification gap, not a contradiction. A token or crypto project is expected to disclose a contract address, a team and terms or a privacy policy. On the pages read, none of these appeared. No operator or legal entity was named either, and no contact channel or risk disclosure appeared. The homepage and the connection page give a visitor no means to establish who receives wallet access or what is being approved, and the site's own pages state a "verified" status without showing any basis for it. The missing disclosures matter more here than they would for a content site. The page's only call to action is a wallet connection, a high-stakes step. The technical hygiene of the site does not compensate for the missing disclosures.

Evidence
  • Homepage and connection page (the only pages read): no contract address, no team information and no terms or privacy policy on the pages read.
  • Homepage: names "Blockchain Guildhall" as its identity but gives no operator, legal entity, address or contact channel.
  • Hosting: served from AS13335 (Cloudflare, Inc., US); the host's abuse record was checked and showed 0 reports.
  • Transport encryption: TLS certificate issued by WE1 (DV, domain-validated only), valid to 2027-01-04.

What to Verify Next

The unsupported "verified" claim and the wallet prompt are the points that need independent checking. Before any wallet interaction, the claim or recovery the page offers should be traced to the official website of the specific project it refers to, reached through a route that does not involve this site. The page names no token contract, so there is nothing on it to check against an on-chain record. Any named team or operator should be confirmed through channels independent of this site. If no independent confirmation can be found, the site should be treated as unconfirmed.

Evidence
  • Homepage: lists many claim and recovery categories without naming any project, token or contract they relate to.
  • Connection page: asks for wallet access without stating what is requested or approved.
  • Page content: names no team or operator whose identity could be confirmed with an outside registry.

Summary Verdict

The site sits at critical risk. The external threat findings, the content of the pages and the observed behaviour all point in the same direction, and no legitimacy signal offsets them. The evidence is consistent with a wallet-connection funnel built around claim and recovery lures, not with an established project.

Infrastructure Integrity

Traffic to the site is served through Cloudflare's edge network, and all four observed addresses belong to that network. The origin server was not observed. This is neutral and is not counted for or against the site. The certificate is valid and issued by a known authority, but it is domain-validated only and says nothing about who operates the site.

Closing Assessment

The site should not be used for any wallet interaction. A visitor should not connect a wallet, sign a message or approve a transaction here. If a wallet was already connected, token approvals should be reviewed and revoked, and assets should be moved to a fresh wallet if there is any doubt.

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

What the analysis found

19 findings contributed to this verdict, raised by external reputation, page content, several checks together, history in the web archive, hosting and network, behaviour in a sandbox, and registration and ownership.

01 External reputation

  • 12 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

02 Page content

  • The review of the page content rated it high risk.Page content rule:PAGE_RISK_HIGH
  • The page shows few of the signs expected from a trustworthy operator.Page content rule:PAGE_TRUST_QUALITY_LOW
  • The page content shows three or more warning signs that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_STRONG
  • The page runs on a free hosting-platform address instead of a domain of its own, a setup common to short-lived phishing and claim pages.Page content rule:PAGE_FREE_PLATFORM_ADDRESS
  • The browser raised a warning while loading the page.Page content rule:PAGE_BROWSER_FLAGS_SUSPICIOUS
  • The page has no description for search engines, which established sites usually provide.Page content rule:PAGE_SEO_MISSING_META
  • The page carries none of the structured previews for search and social sharing that established sites usually provide.Page content rule:PAGE_SEO_NO_STRUCTURED

03 Several checks together

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

04 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

05 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

06 Behaviour in a sandbox

  • The structure of the page changed sharply during the sandbox session.Behaviour in a sandbox rule:BEHAV_DOM_DENSITY_SPIKE
  • The page exchanged network traffic with destinations TrustSniffer does not recognise.Behaviour in a sandbox rule:BEHAV_NONWHITELISTED_TRAFFIC
  • The page sent data to a destination TrustSniffer does not recognise.Behaviour in a sandbox rule:BEHAV_NONWHITELISTED_POSTS
  • The page rewrote itself after it was interacted with, so what a visitor first sees is not what they end up on.Behaviour in a sandbox rule:BEHAV_DOM_DIFF_AFTER_INTERACTION
  • The page made background requests to destinations TrustSniffer does not recognise.Behaviour in a sandbox rule:BEHAV_NONWHITELISTED_XHR
  • The page produced an unusually high number of errors while it ran.Behaviour in a sandbox rule:BEHAV_CONSOLE_ERRORS_HIGH
  • An automated reading of the page's network activity judged some requests unusual for this kind of page.Behaviour in a sandbox

07 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

StatusLIKELY (NOT INDEPENDENTLY VERIFIED)

What the page shows points to a real-world brand or person, but nothing was independently checked.

  • org:Guildhall
  • on_site_identity

What TrustSniffer observed

First-party facts recorded during the assessment of yrrhh.pages.dev.

  • The request stayed on yrrhh.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2026-06-03. Watch
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Code shared with other sites rated Critical

TrustSniffer found that this site serves the same distinctive code files as 1 other site it has analysed. That site is rated Critical on its own evidence.

Shared code shows that these sites were built from the same toolkit. It does not by itself show who operates them.

Shared files (SHA-256)wallet-connect-v4.js 366cd69217836334d1b44d864c2f6804a9349bef6f286bd772969c5a1466f47f
7efb4be83d5c92e9.css ae2f3f1afac32b2af61eaf1bdae1dcf4817bb042353d883566670d9fef55a0a5
626349bc758151ba.css c3c2bde25e57f738be352b23b184d0f5457d29e6bba2bbd7fc05371de5251d0e

Two sites are linked only by two or more shared distinctive files or one shared identifier: an endpoint written into the page's code (a Cloudflare Worker or a Telegram bot), a wallet address shown on the page (checksum-validated), a contact or an analytics ID. Common libraries, platform files, images, well-known contracts, a brand's own accounts and anything also used by a site rated Moderate or High are excluded. Contact details (Telegram, WhatsApp, phone, email) are withheld. A shared file can be checked by its SHA-256 hash.

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:310c::ac42:2f12 (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-04
First seen (web archive)160 days before capture; a site on pages.dev has no registration of its own
Domain expiryNot available
Archive first seen2026-06-03 (160 days before capture)
Archive snapshots2
ReputationVirusTotal: 12 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 yrrhh.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 yrrhh.pages.dev

Is yrrhh.pages.dev a scam?

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

Is yrrhh.pages.dev safe to use?

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

What is the trust score of yrrhh.pages.dev?

yrrhh.pages.dev scored 0 out of 100 on 2026-11-10, 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-10 · how we assess · report a mistake