Question 1

What is vibe coding?

Accepted Answer

Vibe coding is building software by describing what you want in plain language and letting an AI agent write the code. You prompt, it ships a working app; you iterate by prompting again instead of editing files. Tools like v0, Bolt.new, Lovable, and Replit Agent popularised the workflow, and it now produces a large share of new landing pages, dashboards, and side projects on the web. The output is real code — usually React, Tailwind, and a hosted database — so a vibe-coded site is not automatically worse than a hand-written one. What it does mean is that the site inherits the defaults of whatever tool made it: the same component library, the same class naming, the same build output. Those defaults are exactly what a vibe code detector reads.

Question 2

What is a vibe code detector?

Accepted Answer

A vibe code detector is a tool that inspects a website's public output and estimates whether it came out of an AI builder. It works the same way stack-detection extensions do: fetch the HTML, look at what shipped, and match it against known fingerprints. Generator meta tags, script bundle paths, hosting headers, utility-class patterns from a specific component library, and hosted backend endpoints all leave traces that differ between tools. A detector scores how many of those signals fired and how specific each one is. Isvibe.io is a vibe code detector for founders and dev teams: paste a URL, get a 0–100 Vibe Score, and read the exact list of signals behind it. Nothing is inferred from writing style or screenshots — only from the code the site actually serves.

Question 3

How does Isvibe.io detect if a website was built with AI?

Accepted Answer

We request the page like a normal browser would and analyse what comes back. First the document head: generator tags, framework hints, and metadata that builders write automatically. Then the script and asset paths, which often reveal the bundler, the deploy platform, and sometimes the builder itself. Then the markup, where component-library signatures and utility-class conventions show which UI kit was scaffolded. Finally the network layer of the page: hosted database and auth endpoints such as Supabase or Firebase that AI builders wire up by default. Each match carries a weight, and the weighted total becomes your Vibe Score. Every fired signal appears in the evidence list under your result, so if you want to know how to tell if a website is AI generated, you can verify each line in view-source yourself.

Question 4

Can Isvibe.io detect v0, Bolt.new, and Lovable specifically?

Accepted Answer

Yes, when those tools leave identifiable traces in the shipped output — which they usually do. If you want to check if a site was built with lovable.dev, or ask whether a website was built with bolt.new, the detector looks for the specific patterns each platform produces: v0's Vercel-hosted build output and shadcn-style component structure, Bolt.new's StackBlitz-linked assets and Vite bundle signatures, Lovable's project metadata and hosted-backend wiring, and Replit Agent's deploy and asset paths. When a match is specific enough, the tool name appears as a chip on your result. When signals point to the general vibe-coding stack without identifying one vendor, we say that instead of guessing a brand. Naming a tool reflects a matched pattern, not an official statement from that company.

Question 5

Is Isvibe.io free?

Accepted Answer

Yes. Isvibe.io is a free vibe code checker with no signup. There is no account wall, no email capture before your first result, and no credit card. Paste a URL, get the score and the full evidence breakdown. Scanning is rate limited only to keep the service responsive and to avoid hammering the sites we fetch — normal use will not hit those limits. If we ever add a paid tier it will be for things individual scanning does not cover, such as bulk lists, API access, or monitoring a domain over time. The basic check that this page is built around stays free. That is deliberate: a detector nobody can try is a detector nobody trusts.

Question 6

Can vibe code detection be fooled or give false positives?

Accepted Answer

Yes, in both directions, and any tool claiming otherwise is overselling. False positives happen because the vibe-coding stack is also a popular hand-coded stack. A developer who writes React with Tailwind and shadcn components by hand will match several of the same fingerprints an AI builder produces. False negatives happen when generated code is refactored, rebuilt through a custom pipeline, self-hosted, or served behind a proxy or CDN that strips identifying headers. A site can also be a hybrid: AI-generated first draft, heavily rewritten afterwards. That is why the score comes with score bands rather than a yes/no, and why every signal is listed. Read the evidence, weigh it yourself, and treat the number as one input rather than proof.

Question 7

Does Isvibe.io store the URLs I scan?

Accepted Answer

Submitted URLs and their results may be cached temporarily — typically for 24 hours — so repeat scans return instantly and we send fewer requests to the sites being checked. Cached entries expire on their own. Beyond that we keep only aggregate, non-identifying counts: how many scans ran and which fingerprints fired, which is what tells us when a detection rule needs updating. No account is required, no personal data is requested, and nothing is sold or shared with advertisers. Only publicly reachable pages are fetched; we never touch anything behind a login. If you want a cached entry for a domain you control removed, email privacy@isvibe.io and we will clear it. Full details live in the Privacy Policy.

Vibe code detection, answered