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

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

5 OUT OF 100
Critical Risk

hunego.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: The governance checks raised a concern: the business-model ceiling (at most 50) applies, but the score is below it; a threat-intelligence listing limits the score; as a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site). The findings below give the detail.

Evidence captured 2026-11-04, re-scored 2026-11-09 by automated analysis. Evidence confidence 75%.

How the site describes itselfA Cloudflare bot-verification interstitial that requires a CAPTCHA ('I am not a bot') before access. No underlying site content, product, claims, or forms are visible in the captured HTML.

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-04 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-04.
  • 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)). It was not re-queried for this version. On its own the alert would limit the score to at most 24; the threat-listing ceiling holds it at 5, because the listing names the site itself as the source.
  • The real-world operator identity was not independently verified.

How to read these numbers

The trust score runs from 0 to 100, higher is safer. 5/100 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 scoreThreat-listing ceilingA threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-25), and that listing caps the score. The business-model ceiling (at most 50) and the independent sources ceiling (at most 24) also apply, but the score is below them.Risk
Malware engines2 marked it malicious, 1 suspiciousVirusTotalRisk
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 20261 snapshot; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by YE2Noted

The page as captured

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

Overview

The address is a Cloudflare-styled "Verify that you are a human" bot-verification page, hosted as a tenant subdomain on a free web-publishing platform. A visitor is shown only a CAPTCHA prompt ("I am not a bot") and a message saying firewall rules require the challenge. No product, service, pricing, company information or navigation was visible at capture, so no business model can be determined from the page. The address itself was listed by threat-intelligence sources as a phishing actor.

Scam/Impersonation Risk

The address carries critical risk. A threat-intelligence listing classifies it as an active phishing actor, last seen on 25 October 2026, and an aggregated multi-engine scanning service independently flagged it. Two engines rated it malicious and one rated it suspicious. Together these form a confirmed listing from two independent sources. Google Safe Browsing did not list it, and no leading security vendor was among the engines that flagged it. The score is held down by the threat-listing ceiling. A page that imitates a security checkpoint while hosted on an unrelated tenant subdomain is consistent with a gate placed in front of other content, though the capture shows nothing behind it. No brand impersonation was detected, and no conflicting legal identities appeared, because the page carries no identity content at all. The page offered no login or payment form at capture. It generated a high volume of browser console errors, and it lacked a page title description and other basic metadata, which are scored weaknesses. Both are consistent with a thin, hastily assembled page.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
  • Threat-intelligence listing (observed 2026-10-25): the address was classed as a phishing actor.
  • VirusTotal: 2 engines malicious and 1 suspicious; no top-tier vendor among them.
  • Archive record: 1 snapshot, first and last seen 2026-06-16 (span 0 days), and first seen 141 days before capture. The site has no registration of its own because it is a platform tenant.
  • Homepage capture on 2026-11-04: 15 console errors in the sandbox, a CAPTCHA-only page, no forms, and no page metadata.

Regulatory Verification Notes

The page claims no licence, regulator, registration number or company name, and it contains no legal, terms, privacy or about content. Because the capture is only a verification gate, licensing status and operator identity could not be assessed from the site itself. Registration privacy and incomplete ownership data count as scored findings, and the operator's real-world identity remains unverified. No third-party broker or regulatory-database record matched this address, and none is offered as a verdict. The technical profile shows only that the address is technically functional: a valid, DV-validated certificate and an identified network. Neither establishes who runs it or that it is legitimate.

Evidence
  • Homepage: no licence, authority or company disclosure appeared on the captured page.
  • Hosting infrastructure: served from AS13335 (Cloudflare, Inc., US). The host address's abuse record was checked and showed 0 reports.
  • Transport encryption: TLS certificate issued by YE2 (DV), valid to 2027-01-18 at capture.A TLS certificate is what puts the padlock and https:// in your browser and encrypts the connection. "YE2" is the name of the authority that issued it. DV (domain validated) means the issuer only confirmed who controls the domain name, not which person or company runs the site. "Valid to" is the date it expires.
  • Broker database: no match found for this address.

What to Verify Next

The first step is to establish how the address was reached. If it came from an email, message, advertisement or search result, the sender should be contacted through an independent, previously known channel to ask whether the link is genuine. If the address was presented as a financial or otherwise regulated service, the named entity's licence should be checked directly in the relevant regulator's public register. Any official portal for the claimed organisation should be reached by typing its known address manually rather than through this link. A security team that has seen this address in its logs should treat the traffic as related to a phishing listing. It can report the address to the hosting platform's abuse channel.

Evidence
  • Threat-intelligence listing: the address's phishing classification supports tracing its origin.
  • Homepage: no operator, contact or licence details exist on the page to check.
  • Archive record: only one snapshot exists, so no earlier content can be compared.

Summary Verdict

The address sits at critical risk. Independent confirmed listings, a very short first-seen history and an unidentified operator converge, and the threat-listing ceiling holds the score down. The page shows nothing that would let a visitor assess the site on its merits.

Infrastructure Integrity

The address resolved to four Cloudflare edge addresses in the United States, and no origin server was observable. The sandbox found a CDN in front of the site and no origin candidates. The CDN is a neutral factor here. It neither mitigates the listing nor adds exposure, and it says nothing about who operates the content behind it.

Closing Assessment

This address should not be visited, interacted with or relied on, and the CAPTCHA should not be completed. Any message, advertisement or search result that led here should be treated as suspect. Where the page was reached through a trusted brand, only the organisation's independently known official address should be used.

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

What the analysis found

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

01 Governance

  • TrustSniffer limits the score of a site whose operator it could not verify, according to the kind of site it appears to be; here that limit is at most 50, and the score is below it, so it does not set the score.Governance rule:gov_business_model_cap
  • A threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-25), and that listing caps the score.Governance rule:gov_active_threat_listing

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 content shows at least one warning sign that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_SOME
  • 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

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 External reputation

  • 2 VirusTotal engines marked this domain as malicious when the evidence was captured.External reputation rule:EXT_BLACKLIST_MEDIUM

06 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

07 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

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

  • The request stayed on hunego.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

Code shared with other sites rated Critical

TrustSniffer found that this site serves the same distinctive code files, has code wired to the same Cloudflare Worker and uses the same analytics or tracking ID as 12 other sites it has analysed. All 12 are rated Critical on their own evidence.

Shared code and shared identifiers show that these sites were built from the same toolkit or are linked by the same identifier. It does not by itself show who operates them.

Shared identifiersHotjar ID: 3556817
Cloudflare Worker: df.lexine348.workers.dev
Cloudflare Worker: small-star-b48f.linkamlbot.workers.dev
Shared files (SHA-256)flower.js 04c10f9e3fa16c775133790941b2db949883acf5ad7d4c47fd81fc569f432455 (8 sites)
8phixoeci82.js 348b5111017a62ad16be1e54454e824979fbe96981c6b618caf5394fcf056094 (3 sites)
6eeadc20.js d0e4263c6f4eb664599977a4191642926c54f86ac88991a209af7a1988426046

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:2c98 (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 issuerYE2
SSL expiry2027-01-18
First seen (web archive)141 days before capture; a site on pages.dev has no registration of its own
Domain expiryNot available
Archive first seen2026-06-16 (141 days before capture)
Archive snapshots1
ReputationVirusTotal: 2 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 hunego.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 hunego.pages.dev

Is hunego.pages.dev a scam?

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

Is hunego.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 hunego.pages.dev?

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