Is zrc20.icu safe? TrustSniffer's low-trust assessment: 41/100

zrc20.icu
Download PDF Check another site How we score

Verdict

Several risk patterns were present. Do not send money or personal details until you have verified this business another way.

41 OUT OF 100
Low Trust

zrc20.icu is low-trust and potentially risky.

Safe for Read-Only

Assessed 2026-10-19 by automated analysis. Classification confidence 75%.

What this site appears to beA minimal promotional landing page for a ZRC20 token airdrop on the ZEC mainnet by the 'BitX team'. Content primarily advertises an airdrop/claim and provides minimal contextual or trust-building information.

Evidence status and limitations

Evidence completeness: Not recorded

  • The real-world operator identity was not independently verified.
  • Module-level completeness metadata is unavailable for this legacy report.

At a glance

The checks that decide most of this verdict.

Malware enginesNone flagged itVirusTotalClear
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 0 reports; shared hosting inflates reportsClear
Domain age22 days oldMost scam domains are under a year oldRisk
Web archiveArchived since 20262 snapshotsClear
CertificateEncrypted connectionIssued by YE2Noted

The page as captured

https://zrc20.icu/
Screenshot of the zrc20.icu homepage captured during the TrustSniffer assessment
What zrc20.icu served when TrustSniffer captured it on 2026-10-19. The page may look different now.

Key findings

  • Automated classification: Safe for Read-Only.
  • Domain age: less than 1 year (registration continuity).
  • Public web-archive history exists since 2026.
  • No flags from the reputation services TrustSniffer consulted at assessment time.

Full analysis

Overview

The website is a minimal promotional landing page for a ZRC20 token airdrop on the ZEC mainnet, presented as a project by the “BitX team” and intended to direct visitors toward an airdrop claim or address-checking process rather than a clearly defined commercial service.

Scam/Impersonation Risk

No confirmed blacklist, phishing, malware, brand-impersonation, or conflicting-identity signals were observed. The principal concern is the site’s own content: the homepage promotes “ZRC20,” describes it as the first ZRC20 token on ZEC mainnet, and refers to airdrop applications and a future claim process, but provides little evidence supporting the project, its value flow, or the identity of the operating team. The site’s FAQ and documentation links do not, in the supplied evidence, resolve that information gap. One external reputation check produced a suspicious result, but it was not corroborated as a malicious or blacklist determination. The appropriate posture is therefore cautious and limited to observation pending independent validation.

Evidence
  • Homepage: promotes “ZRC20,” a ZEC-mainnet airdrop, and a future token-claim process while providing only minimal project context.
  • Homepage: states that the token was built by the “BitX team” and links to a single social-media account, without independently establishing the team’s identity.
  • External reputation telemetry: 0 malicious detections, 1 suspicious detection, and no confirmed blacklist result.
  • Registration and archive telemetry: registered 2026 (~0.06 years old); 2 archive snapshots spanning 2026–2026 (1 year tracked).

Regulatory Verification Notes

The available material does not establish a regulated financial service or a verified licensed operator. The site presents a token-distribution campaign, but the supplied pages do not provide a clear legal entity, licensing authority, registration number, or formal regulatory disclosure. This is a verification gap rather than evidence of impersonation or fraud. The registration record names Gayane Karapetyan and uses PDR Ltd. d/b/a PublicDomainRegistry.com as registrar; those details identify a registration record but do not independently prove that the named person operates the project. Transport security and hosting records are technically consistent with a functioning website, but they do not validate the business or token claims.

Evidence
  • Registration record: created 2026-09-25 and expiring 2027-09-25; registrar PDR Ltd. d/b/a PublicDomainRegistry.com; registrant listed as Gayane Karapetyan.
  • Homepage, FAQ, and documentation pages: no license authority or license number is identified in the supplied content.
  • Hosting telemetry: served from AS13335, CLOUDFLARENET — Cloudflare, Inc., US.
  • Transport telemetry: TLS certificate issued by YE2 with DV validation, valid to 2026-12-27.

What to Verify Next

Before any account, wallet, payment, or token-related interaction, an independent review should confirm the legal identity behind the “BitX team,” the project’s token contract and distribution mechanics through authoritative ZEC ecosystem sources, and whether any relevant financial or virtual-asset registration applies. The published social account and contact routes should also be validated through an independent, offline-established channel rather than relying solely on links presented by the landing page. Any claim or transaction should be tested only after the project’s documentation, ownership, and recovery arrangements are independently substantiated.

Evidence
  • Homepage: confirms the stated project name, token claim purpose, and ZEC-mainnet association that require independent validation.
  • FAQ and documentation pages: provide the designated locations for checking distribution rules, technical details, and operator disclosures.
  • Social-link path: provides only one externally linked social presence, making independent channel confirmation material to identity validation.

Summary Verdict

The website has a low-trust posture and should be treated as an unverified, newly established token project with limited operational transparency. No direct contradiction or confirmed impersonation finding was identified, but the available evidence is insufficient to support confidence in the project’s claims or operator identity beyond a likely association with the stated team.

Infrastructure Integrity

The site is protected by Cloudflare’s CDN/WAF infrastructure, which provides a mitigating layer against direct exposure of the hosting environment; all observed addresses were CDN edge addresses, and no origin address was identified in the supplied infrastructure analysis. This protection supports transport and availability integrity but is not evidence that the project itself is legitimate.

Evidence
  • Infrastructure: Cloudflare CDN/WAF detected; four observed addresses were identified as edge infrastructure.
  • Origin analysis: no likely origin IP candidate was identified.

Closing Assessment

The proportionate course is read-only review until the operator, token mechanics, and applicable regulatory position have been independently confirmed; credentials, wallet authorization, payments, and other financially consequential actions should not be undertaken on the basis of the landing page alone.

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

What the analysis found

3 findings contributed to this verdict, raised by page content, hosting and network, history in the web archive.

01 Page content

  • 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 review of the page content rated it moderate risk.Page content rule:PAGE_RISK_MED
  • The page content shows at least one warning sign that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_SOME

02 Hosting and network

  • The domain was registered less than three months ago.Hosting and network rule:DNS_NEW_DOMAIN_90D

03 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

Identity verification

StatusLIKELY
Identity score73/100
Identity verification confidence74%
  • Trusted social count=1

Identity verification measures whether the site can be independently connected to a real-world brand or person. It is separate from the classification confidence.

What TrustSniffer observed

First-party facts recorded during the assessment of zrc20.icu.

  • The request stayed on zrc20.icu. It was not redirected to another domain. Clear
  • Registration is published under PDR Ltd. d/b/a PublicDomainRegistry.com. Clear
  • DNS for this domain is served by cloudflare.com, across 2 name servers. Noted
  • The registration is paid up to 2027-09-25. Noted
  • The earliest public archive of this site is from 2026-09-26. Clear
  • It is hosted on CLOUDFLARENET, from a server in US. Noted

Domain intelligence

RegistrarPDR Ltd. d/b/a PublicDomainRegistry.com
HostingCLOUDFLARENET - Cloudflare, Inc., US
CountryUS
Server IP2606:4700:3033::ac43:884d
Name serversGUY.NS.CLOUDFLARE.COM, JULE.NS.CLOUDFLARE.COM
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerYE2
SSL expiry2026-12-27
Domain age0.06 years (continuous registration)
Domain expiry2027-09-25
Archive first seen2026-09-26
Archive snapshots2
ReputationVirusTotal: 0 flagged | AbuseIPDB: 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about zrc20.icu at assessment time. It is a starting point for your own judgement, not a guarantee: a high score means the signals were consistent with a legitimately operated site, a low or critical score means several risk patterns were present.

TrustSniffer assesses a website from the evidence it can collect at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A score is a summary of that evidence, 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 zrc20.icu

Is zrc20.icu a scam?

TrustSniffer found several risk patterns on zrc20.icu. It scored 41 out of 100 on 2026-10-19, a low-trust result. That is not proof of fraud: it means the evidence did not support treating the site as safe.

Is zrc20.icu safe to use?

Several risk patterns were present. Do not send money or personal details until you have verified this business another way.

What is the trust score of zrc20.icu?

zrc20.icu scored 41 out of 100 on 2026-10-19, which places it in the low-trust 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.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-19 · how we assess · report a mistake