Is gitlawb a scam? TrustSniffer's critical-risk assessment of git-lawb.net: 5/100

git-lawb.net

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

git-lawb.net shows critical-risk indicators.

Sensitive Interaction 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.

Evidence captured 2026-11-03, re-scored 2026-11-05 by automated analysis. Evidence confidence 55%.

How the site describes itselfGitlawb is a v0.1.0-alpha decentralized git network aimed at developers and AI agents. It offers DID-based identity, IPFS-pinned storage, libp2p gossip replication, and an MCP server with 25 tools. The page lists three live nodes and promotes an open-source OpenClaude runtime, a Playground, and a one-line CLI install. It makes no financial or return claims and collects no sensitive data.

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-03 and re-scored on 2026-11-05. The certificate, the registration age and the page content describe the site as it was on 2026-11-03.
  • 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 (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 scoreBusiness-model ceiling; Threat-listing ceilingTrustSniffer 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 what sets the score. A threat-intelligence feed TrustSniffer monitors listed a file on this site as malicious when the evidence was captured, and that listing caps the score.Risk
Malware engines2 marked it maliciousVirusTotalRisk
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
Domain age5 months oldRegistered 2026-05-21Risk
Web archiveNever archivedNo public history of this siteWatch
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

https://git-lawb.net/
Screenshot of the git-lawb.net homepage captured during the TrustSniffer assessment
What git-lawb.net served when TrustSniffer captured it on 2026-11-03. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • Domain age: less than 1 year at capture (registered 2026-05-21).
  • At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Overview

This website presents itself as gitlawb, a v0.1.0-alpha decentralized git network for developers and AI agents. Its homepage promotes DID-based cryptographic identity, IPFS-pinned storage, libp2p replication, an MCP agent server with 25 tools, an open-source "OpenClaude" runtime, a hosted Playground and a one-line command-line install. It also carries a "$gitlawb" token menu and a "Check Eligibility" button. No pricing, deposits or return promises are shown, so the apparent purpose is an early-stage open-source developer-tooling project with an associated crypto token.

Scam/Impersonation Risk

Contradictory signals are present, and they outweigh the benign appearance of the page. A threat-intelligence feed currently lists this domain as an active distributor of phishing, with the site itself cast as the actor rather than a compromised victim. This listing is decisive. It is reinforced by a confirmed external blacklist hit, with two security engines rating the domain malicious and a third rating it suspicious. The page content is a counterweight but does not offset these findings. The homepage collects no credentials and has no login or payment forms. Nothing in the captured page suggests wallet-drainer behavior, clipboard tampering or hidden forms. A phishing listing can still attach to a domain whose landing page looks clean, because lures are often served on other paths or to selected visitors. Two features of the page fit that pattern. The "Check Eligibility" call to action next to a "$gitlawb" token is a common lure for token-claim or airdrop credential theft. The one-line install command asks visitors to run remotely supplied code on their own machines. The domain is also a hyphenated variant of the brand shown on the page ("gitlawb"), and it closely resembles a major code-hosting platform's name, a lookalike pattern often seen in typosquatting. No brand impersonation was confirmed, and the evidence shows no conflicting legal identities.

Evidence
  • Homepage: shows a "Check Eligibility" button and a "$gitlawb" token menu alongside the developer-tool claims, with no explanation of the eligibility criteria.
  • Homepage: advertises a one-line CLI install and an MCP server with 25 tools, which would run code on user systems.
  • Domain registered 2026-05-21 (~0.45 years old). The project name on the page is "gitlawb", while the domain is the hyphenated "git-lawb".
  • Behavioral testing recorded no forms and no wallet-connection attempts. It did record 15 console errors and 27 external data requests, none to non-whitelisted destinations.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.

Regulatory Verification Notes

The site does not claim to be a licensed or regulated financial service, and none of its advertised products (git hosting, agent tooling, a free runtime) would normally need a financial license. The gaps are in basic disclosure. The page names no legal entity and gives no contact address, terms or privacy page, and no pricing. It describes the network as a "live multi-node network" and lists three nodes, but nothing on the page lets a visitor confirm this. The security audit is shown on the roadmap as not yet shipped. The "$gitlawb" token has no visible issuer, terms or eligibility rules, which matters because token programs can create financial exposure. No third-party broker or regulatory-registry record was matched to the domain. The risk assessment therefore rests on the threat-listing and blacklist findings, not on any licensing question.

Evidence
  • Homepage: no legal entity, contact address, pricing or licensing statement appears; the audit and several features are marked as not yet shipped.
  • Domain registered 2026-05-21 (~0.45 years old) through PDR Ltd. d/b/a PublicDomainRegistry.com, expiring 2027-05-21.
  • Served from AS13335 (Cloudflare, Inc., US).
  • TLS certificate issued by WE1 (DV level), valid to 2026-12-16. DV validates domain control only and says nothing about the operator's identity.

What to Verify Next

Before any interaction, confirm that this domain is the one the project's maintainers actually publish. Check it against the project's official source-code repository and its official social channels, not against links on this site. The hyphenated domain should be compared with the unhyphenated project name to establish which, if either, is the real one. The "Check Eligibility" flow and the "$gitlawb" token should be treated as unverified until an independent source confirms that a legitimate claim program exists. The command-line install should not be run from this site. If the software is wanted, it should be obtained from the maintainers' repository and its signatures or checksums reviewed first. Organizations should check whether the phishing listing is later cleared, and they should confirm official support and contact channels through an independent route.

Evidence
  • Homepage: the GitHub and X links are the channels to cross-check, and the page offers no other contact route.
  • Homepage: the one-line install and the Playground are the actions that execute or process user input.
  • The threat listing was last observed on 2026-10-24, so it is current.

Summary Verdict

The overall posture is high-risk. An active phishing listing and a confirmed blacklist outweigh the developer-focused presentation of the page. The project may be a genuine early-stage venture, but the available evidence does not support treating this domain as safe for sensitive use. Its operator identity remains unverified.

Infrastructure Integrity

The site sits entirely behind Cloudflare's CDN and WAF. All four observed addresses are Cloudflare edge servers, and no origin server was observable. The TLS certificate is valid but is only domain-validated. Cloudflare's bot protection was also detected during behavioral testing. These are mitigating factors only. Edge-only visibility prevents independent verification of where the content is served from, and it can mask rapid content changes. The protections cannot offset the reputational findings.

Closing Assessment

Treat the domain as unsafe for any interaction beyond passive viewing. Do not log in, connect a wallet, claim anything through the eligibility flow, enter credentials, make payments, or run or download anything from it until the maintainers' official domain is independently confirmed and the threat listing is cleared.

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

What the analysis found

6 findings contributed to this verdict, raised by governance, external reputation, hosting and network, behaviour in a sandbox and page content.

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 what sets the score.Governance rule:gov_business_model_cap
  • A threat-intelligence feed TrustSniffer monitors listed a file on this site as malicious when the evidence was captured, and that listing caps the score.Governance rule:gov_active_threat_listing

02 External reputation

  • Three or more VirusTotal engines, or two including a leading vendor, marked this domain as malicious.External reputation rule:EXT_BLACKLIST_HIGH

03 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

04 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

05 Page content

  • The page has no description for search engines, which established sites usually provide.Page content rule:PAGE_SEO_MISSING_META

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 git-lawb.net.

  • The request stayed on git-lawb.net. It was not redirected to another domain. Clear
  • Registered through PDR Ltd. d/b/a PublicDomainRegistry.com. Noted
  • DNS for this domain is served by ns.cloudflare.com, across 2 name servers. Noted
  • The domain is registered until 2027-05-21. Noted
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Domain intelligence

RegistrarPDR Ltd. d/b/a PublicDomainRegistry.com
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:3037::ac43:862b (a CDN edge address; the server behind it was not observed)
Name serverskyrie.ns.cloudflare.com, lauryn.ns.cloudflare.com
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2026-12-16
Domain age166 days (registered 2026-05-21)
Domain expiry2027-05-21
Archive first seenNot available
Archive snapshots0
ReputationVirusTotal: 2 malicious | 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 git-lawb.net 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 git-lawb.net

Is git-lawb.net a scam?

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

Is git-lawb.net 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 git-lawb.net?

git-lawb.net scored 5 out of 100 on 2026-11-05, 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-05 · how we assess · report a mistake