Is og-liquicore.web.app a scam? TrustSniffer's critical-risk assessment: 5/100

og-liquicore.web.app

Is it safe to use? An external threat listing 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

An external threat listing 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

og-liquicore.web.app 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 40) applies, but the score is below it; a threat-intelligence listing limits the score; as a site on web.app, 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-10, re-scored 2026-11-16 by automated analysis. Evidence confidence 55%.

How the site describes itselfLiquiCore is a pre-launch BNB Chain liquidity protocol running an OG Season 0 campaign in which users register a wallet and earn points through referrals and tasks for a possible top-300 OG role. Protocol features such as vaults, lending and launchpad are listed in navigation without details, audits are marked 'Soon', and no legal entity, address or contact channel is shown.

Evidence status and limitations

Evidence completeness: PartialThis says whether every check on the site was recorded as finished. At least one check failed or returned no result.

  • The evidence was captured on 2026-11-10 and re-scored on 2026-11-16. The certificate, the registration age and the page content describe the site as it was on 2026-11-10.
  • One external source flagged this site when the evidence was captured (a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-26)). No second source confirms it. The alert is from the evidence captured on 2026-11-10; it was not re-queried for this version and is treated as unconfirmed. On its own the alert would limit the score to at most 49; 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.
  • These checks returned no result: web archive lookup.

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 (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 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-26), and that listing caps the score. The business-model ceiling (at most 40) and the unconfirmed alert ceiling (at most 49) also apply, but the score is below them.Risk
Malware enginesNone malicious; 2 marked it suspiciousVirusTotalWatch
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address1% confidenceAbuseIPDB, 4 reports; shared hosting inflates 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
CertificateEncrypted connectionIssued by WR3Noted
Hosted byFASTLYNetwork registered in USNoted

The page as captured

https://og-liquicore.web.app/
Screenshot of the og-liquicore.web.app homepage captured during the TrustSniffer assessment
What og-liquicore.web.app served when TrustSniffer captured it on 2026-11-10. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • No security engine marked this domain as malicious and Google Safe Browsing does not list it; some engines marked it suspicious, which TrustSniffer does not count as a listing. Its hosting IP carries AbuseIPDB reports below the confidence level TrustSniffer treats as a flag.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Overview

LiquiCore presents itself as a pre-launch decentralized liquidity protocol on BNB Chain, served from a subdomain of a free hosting platform (web.app) rather than a domain of its own. Its single captured page is an "OG Season 0" campaign. Visitors are asked to connect a wallet, register, and earn points through referrals and social tasks to qualify for one of 300 "OG" places. The site's navigation lists vaults, lending, a launchpad, governance and an NFT section without describing them, and its LIQ token is shown as not yet live. The apparent business model is a points-and-referral growth campaign ahead of a token launch. The page does not say how the protocol would earn revenue or how the token would be distributed.

Scam/Impersonation Risk

This is a critical-risk site. A threat-intelligence feed recorded the site as a phishing source, with the site itself in the actor role rather than a victim. The listing was last seen on 26 October 2026, shortly before the evidence was captured on 10 November 2026. It is a single-source alert and not a multi-source confirmation. It holds the overall assessment down through the threat-listing ceiling. Two antivirus engines rated the address suspicious and none rated it malicious. No brand impersonation was detected, and the site's own pages do not name conflicting legal entities, so no identity contradiction was found. The page offers no login or payment form, but it does push visitors toward a wallet connection. It does so with urgency and exclusivity messaging: "Secure your spot now" and "15d 7h left to register" (the site's own wording). It also shows "1935 registered" against only 300 places, and says selection is by "Manual review by team". A wallet-connection flow tied to a phishing-class listing is the sensitive interaction in this assessment. The leaderboard shows many accounts with near-identical points and full referral counts. The page does not explain how those figures were produced or checked.

Evidence
  • Threat feed: the site was recorded as a phishing source in the actor role, last seen 26 October 2026, from a single source.
  • VirusTotal: 2 engines rated the address suspicious and 0 rated it malicious.
  • Homepage: the "OG Registration" panel pairs a countdown with "Connect Wallet to Claim", and its leaderboard shows 1935 registered participants competing for 300 places.
  • Homepage: no login, password or payment form was observed (0 forms), and no brand impersonation was detected.

Regulatory Verification Notes

On the pages read (only the homepage), the footer links to Terms of Service, Privacy Policy, Risk Disclosure, Disclaimer and Contact. On those pages no legal entity, registered address, team members, regulator or licence, or contract address is shown. For a token project these are the core disclosures. The site's own pages also say things that sit badly together. The timeline lists registration as Days 1–3, while the page shows "Day 1 of 18" and 15 days left to register. The site calls its contracts "non-custodial smart contracts governed by the community", yet Governance and Token are marked "Soon". Audits and Bug Bounty are also "Soon". The page counter "18 / 300 Total OG spots (final selection)" is not explained. No third-party broker or regulatory record was matched. Nothing independent connects the site to a real-world operator, so the "LiquiCore" name is only the site's own presentation of itself.

Evidence
  • Homepage footer: lists legal and contact links but names no operating entity, address or regulator.
  • Homepage security section: Audits and Bug Bounty are marked "Soon" while the protocol is described as infrastructure.
  • Homepage timeline: shows registration as Days 1–3, against the "Day 1 of 18" and "15d 7h left to register" counters.
  • Registration record: the address is a subdomain of the web.app hosting platform, so there is no registration of its own to examine.

What to Verify Next

One open question is whether the listing relates to content that was actually served from this address. The site's claims should also be tested against records the operator does not control. A contract address published on a blockchain explorer, a named team, and a completed third-party audit report would each be independent evidence, and none was visible on the page read. Any official support or contact channel should be confirmed through a route independent of this page. Wallet connection should not be attempted unless those checks succeed.

Evidence
  • Homepage: no contract address was shown for the LIQ token, which the page itself describes as not yet live.
  • Homepage: no named team was shown, and selection of OGs is described only as "Manual review by team".
  • Homepage security section: audit status is "Soon", so no audit report exists to check yet.

Summary Verdict

The assessment is critical risk. The site has a recorded phishing-class threat listing, no verifiable operator, and a campaign built around a wallet connection for an unlaunched token. Unverifiable claims and internally uneven page statements reinforce that picture. Technical hygiene such as a valid certificate does not alter it.

Infrastructure Integrity

Traffic is served through Fastly's edge network, and only edge addresses were observed. The origin server could not be observed, so hosting of the actual content cannot be verified independently. The CDN is neutral and neither mitigates nor aggravates the risk. Four abuse reports on the shared Google-operated edge address were attributed to that shared provider infrastructure and say little about this site. The page's behaviour under interaction was a scored concern. Its structure changed very heavily after interaction, with about 15,600 DOM changes recorded. The site's transport encryption was valid at capture.

Evidence
  • Hosting infrastructure: served from AS54113 (FASTLY, Fastly, Inc., US) via two edge IPs, with no origin candidate observed.
  • Transport encryption: the TLS certificate was issued by WR3 (DV) and valid to 2027-01-25.
  • Shared-address abuse record: 4 reports against the shared provider address, attributed to that provider's infrastructure.

Closing Assessment

The site should be treated as unsafe for any sensitive interaction. That means no wallet connection, no registration for the OG campaign, and no sharing of social accounts or referral links. Viewing the page without interacting is the only use consistent with the assessment.

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

What the analysis found

8 findings contributed to this verdict, raised by governance, page content, behaviour in a sandbox, and registration and ownership.

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 (this one reads as a crypto token project on its own pages); here that limit is at most 40, 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-26), and that listing caps the score.Governance rule:gov_active_threat_listing

02 Page content

  • The page content shows three or more warning signs that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_STRONG
  • 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 Behaviour in a sandbox

  • The page replaced a large part of its own content during the sandbox session.Behaviour in a sandbox rule:BEHAV_DOM_CHANGE_HIGH
  • 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 structure of the page changed sharply during the sandbox session.Behaviour in a sandbox rule:BEHAV_DOM_DENSITY_SPIKE

04 Registration and ownership

  • As a site on web.app, 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

How related findings were counted

Some findings above describe the same underlying fact, and some are weak on their own. TrustSniffer counts each such group under one shared limit, so one fact is not counted several times and weak signals stay bounded.

  • Page structure: 3 findings share one limit, because they describe one page structure. The limit applied, so together they counted for less than their sum.
  • Certificate and search-engine setup: 2 findings share one limit, because none of them is a sign of fraud on its own. Together they stayed under the limit.

Noted, not counted

Recorded during the assessment, but not counted against the site.

  • AbuseIPDB: 4 reports on hosting IP 2620:0:890::100 (FASTLY), 1% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

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.

  • org:LiquiCore
  • on_site_identity

What TrustSniffer observed

First-party facts recorded during the assessment of og-liquicore.web.app.

  • The request stayed on og-liquicore.web.app. It was not redirected to another domain. Clear
  • It is hosted on FASTLY, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingFASTLY - Fastly, Inc.
Network registered inUS
Server IP2620:0:890::100 (a CDN edge address; the server behind it was not observed)
Name serversNot available
CDN / edge networkDetected (fastly)
Resolved IP addresses2
Edge IP addresses2
Likely origin IP addresses0
SSL issuerWR3
SSL expiry2027-01-25
First seen (web archive)Not available (the web archive has no record of this address; a site on web.app has no registration of its own)
Domain expiryNot available
Archive first seenNot available
Archive snapshotsNot counted (archive lookup incomplete)
ReputationVirusTotal: 0 malicious, 2 suspicious | AbuseIPDB (CDN edge address, not the host): 1% confidence, 4 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about og-liquicore.web.app 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 og-liquicore.web.app

Is og-liquicore.web.app a scam?

TrustSniffer's assessment of og-liquicore.web.app found strong scam indicators. It scored 5 out of 100 on 2026-11-16, which is the critical-risk band. The specific signals are listed in the evidence above.

Is og-liquicore.web.app safe to use?

An external threat listing 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 og-liquicore.web.app?

og-liquicore.web.app scored 5 out of 100 on 2026-11-16, 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-16 · how we assess · report a mistake