Findings · 2026-09-25 · By VSNARY | Emmanuel Orta · 0 views
CrawlCheck is crawlcheck.io, not crawlcheck.dev or .com
One CrawlCheck has been scanning sites and sealing the results to the Bitcoin blockchain since 13 August 2026. A second one appeared on 18 September under the same name. Here is the public record, how to tell us apart, and what each one actually does.
CrawlCheck is crawlcheck.io. Its domain was registered on 12 August 2026 and its reports have been sealed to the Bitcoin blockchain every day since 13 August. It is not affiliated with crawlcheck.dev, a separate product registered on 18 September 2026 that bills through Paddle or Lemon Squeezy, or with crawlcheck.com, a 2011 registration with no working site. Our only website is crawlcheck.io, our email is @crawlcheck.io, and we take payment only through Stripe.
There is one CrawlCheck, and it is crawlcheck.io. We are not affiliated with crawlcheck.dev, crawlcheck.com, or any other website, app, extension or account that uses the CrawlCheck name and is not linked from this site. We did not build them, we do not run them, we do not take their payments, and we will not answer for them.
One of them, crawlcheck.dev, sells an AI-crawler audit under our exact name, with a two-tone wordmark — “Crawl” in white, “Check” in teal, on a dark page — that is easy to mistake for ours. It appeared 37 days after we did. This page sets out the record, which is not ours to edit, and exactly what each site does.
The short version #
crawlcheck.dev does a fraction of what CrawlCheck does. Its free tools read a robots.txt you paste in, and its scanner fetches one page as 8 crawlers, three times a day. Its paid report sweeps up to 50 pages of one site as the same 8 crawlers and returns a fix list. CrawlCheck audits the whole site: 114 named crawlers resolved from robots.txt, 15 crawler identities sent to your site live, 35 measured sections with 24 of them scored, an open dataset from thousands of scans, reports anyone can prove were never altered, a browser extension, a documented API, and a team that will implement every fix it finds. It uses our name, and it arrived five weeks after we did.
The record #
Anyone can say they were first. The dates below come from three public records that neither site controls, so anyone can check them without trusting us.
| Record | crawlcheck.io (us) | crawlcheck.dev | Who keeps it |
|---|---|---|---|
| Domain registered | 12 Aug 2026 | 18 Sep 2026 | The .io and .dev registries (RDAP) |
| First TLS certificate for the current site | 12 Aug 2026, 20:48 UTC | 18 Sep 2026, 12:04 UTC | Public Certificate Transparency logs |
| First day sealed to the Bitcoin blockchain | 13 Aug 2026, and every day since | None | The Bitcoin blockchain, via OpenTimestamps |
| Terms of service in effect | At launch | 21 Sep 2026 | Each site’s own terms page |
The third row is the one nobody can argue with. Every day since 13 August, a fingerprint of that day’s crawlcheck.io reports has been written into the Bitcoin blockchain. A timestamp there cannot be backdated by anyone — including us. The site was scanning real domains and sealing the results for 36 days before crawlcheck.dev’s domain was registered. The receipts are on our proof page, and any of them can be checked with free, open tools.
The name is older than both of us, and that is fine #
We checked further back, because a page like this should survive anyone checking it. The word has been used before, and none of those uses has anything to do with either site:
- crawlcheck.com was registered in 2011 by someone else. It had no working website when we checked.
- crawlcheck was an open-source Python web crawler for checking sites before deployment, published on GitHub by Alexandr Mansurov between 2015 and 2019.
- crawlcheck.io itself was held by a different owner between 2018 and 2020, according to Certificate Transparency logs. It lapsed, and we registered it on 12 August 2026.
None of those were AI-crawler audits, and none of them are a problem. What changed on 18 September is different in kind: a second product in the same market, selling the same kind of audit, under the identical name, with a wordmark in the same two colours, five weeks after ours went live. That is the one we are writing about.
Every CrawlCheck domain we checked #
| Domain | What is there (25 Sep 2026) | Ours? |
|---|---|---|
| crawlcheck.io | This site: the AI-visibility audit, reports, research, API and browser extension | Yes |
| crawlcheck.dev | A separate product under the same name: registered 18 Sep 2026, paid report billed through Paddle or Lemon Squeezy, contact hi@crawlcheck.dev | No |
| crawlcheck.com | Registered in 2011 by someone else; no working website answered when we checked | No |
| .net, .org, .ai, .app, .co, .tech, .xyz, .pro, .tools, .me, .so, .cloud, .page, .store, .shop, .site, .online, .us, .info, .biz | Not registered, or no website, when we checked | No |
| Any other CrawlCheck app, extension, social account or site | Not ours unless crawlcheck.io links to it | No |
How to tell it is us #
- The address. Our only website is crawlcheck.io. Reports live at crawlcheck.io/r/… and every page is served from that domain.
- Email. We write from @crawlcheck.io addresses only, for example hello@crawlcheck.io.
- Payments. We take payment only through Stripe checkout links on crawlcheck.io. A “CrawlCheck” charge from Paddle or Lemon Squeezy is not ours; crawlcheck.dev’s own terms name those two as its merchants of record.
- The browser extension. Ours is the one linked from crawlcheck.io/extension.
- Who runs it. CrawlCheck is built and operated in Colorado by Emmanuel Orta (VSNARY), under his own name. crawlcheck.dev’s about page names no one.
What each one does #
crawlcheck.dev’s column is taken from its own pages — home, scanner, about, terms and refund policy — read on 25 September 2026, and it includes the paid report its terms describe. Ours is measured on this site the same day.
| crawlcheck.io (us) | crawlcheck.dev (not us) | |
|---|---|---|
| What you give it | A domain. We fetch the live site ourselves. | A robots.txt you paste in, or one page URL for its free scanner (3 scans a day) |
| Crawlers covered | 114 named crawler agents resolved from robots.txt; 15 crawler identities sent to your site live | “60+” AI crawlers in its list, built from the open ai.robots.txt community project; its scanner and paid report fetch as 8 |
| What is measured | 35 measured sections, 24 of them scored: robots.txt and its hidden rule conflicts, machine files, structured data and the entity graph, local listings, speed and more | robots.txt verdicts, a live fetch per crawler, a bot-versus-browser text check, JSON-LD, llms.txt, noindex and readable text, rolled into one score |
| Paid report | The fix list implemented on your site for $749 with 30 days of monitoring, or Watch monitoring (/pricing) | “Pro Deep Report”: up to 50 pages of one site, 8 crawlers, a prioritized fix list at a private URL, 30-day money-back guarantee; price shown only at checkout |
| Proof of results | Every report fingerprinted with SHA-256; each day anchored to Bitcoin (how it works) | Not offered on its site |
| Open data | Published dataset from 2,394 scans across 6,992 measured sites (/data) | Not offered on its site |
| Research | 65 published findings, 26 guides and a 579-term glossary | Guides and a crawler directory |
| Free tools | Per-crawler robots.txt reader, llms.txt drafter, access-log crawler verifier, sitemap, HSTS and EntityMap starters | robots.txt auditor and generator; FAQ, HowTo and Article schema generator |
| Browser extension | Yes: measures what crawlers are served from your own browser (/extension) | Not offered on its site |
| API | 21 documented endpoints, 14 open, plus an MCP server (/docs/api) | Not documented on its site; its scanner runs on api.crawlcheck.dev |
| Who implements the fixes | We do, on your site, and prove each one with a re-scan | Not offered on its site; the report is a list for you to work through |
| Payments | Stripe | Paddle or Lemon Squeezy |
| Contact | hello@crawlcheck.io | hi@crawlcheck.dev |
The gap is not a matter of taste. A robots.txt verdict tells you what a file says. A live fetch as 8 crawlers tells you what 8 crawlers were served on the pages you asked about. CrawlCheck does both, for 15 crawler identities and every section of the site that answer engines read, then publishes the evidence, seals it, and fixes what it finds. That is what the name stood for five weeks before anyone else used it.
We are watching, and we keep receipts #
Our monitoring checks every hour for new domains close to our name — whether each one resolves, holds a TLS certificate, or serves a page — and keeps watching crawlcheck.dev and crawlcheck.com for changes. Each hit is checked by hand before anything is said about it, because a similar name is often a coincidence. When something matters, it is recorded with its date and the evidence behind it, the same way we record everything else. If anything changes — a new lookalike, a changed wordmark, a site that stops using the name — this page will say so, with the date.
To whoever runs crawlcheck.dev #
You launched an AI-crawler audit under a name that a live AI-crawler audit had already been using for five weeks, with a wordmark in the same two colours. The dates are in public logs that neither of us can change. We have no interest in your customers and will not contact them. Pick a name of your own, and we will note it on this page the day you do. Until then, this page stays up and stays accurate.
If something claiming to be CrawlCheck contacted you #
If an email, invoice, extension or account says it is CrawlCheck and it is not on crawlcheck.io or from an @crawlcheck.io address, it is not us. Forward it to hello@crawlcheck.io and we will look at it. If you bought a report through Paddle or Lemon Squeezy, that purchase was with crawlcheck.dev; its terms offer a 30-day money-back guarantee through hi@crawlcheck.dev.
Method #
Registration dates come from each registry’s RDAP record: crawlcheck.io (Identity Digital, registrar Namecheap), crawlcheck.dev (registrar Cloudflare) and crawlcheck.com (registrar GoDaddy). Certificate dates are the earliest entries for each current site in public Certificate Transparency logs, read through crt.sh. Seal dates are listed on our proof page with their OpenTimestamps files. The GitHub project’s dates are its first and last commits. The other domains were checked by DNS lookup and an HTTPS request on 25 September 2026. crawlcheck.dev’s features, processors, guarantee and contact address are quoted from its own pages the same day. This page describes the sites as we found them; it makes no claim about who runs crawlcheck.dev.
Every figure above came out of this scanner.
Point it at your own domain and see the same measurements, free.
The main product
Found this on your own site? We fix it for $749.
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
Questions this post answers
Is crawlcheck.dev the same company as crawlcheck.io?
No. crawlcheck.dev is a separate product with its own terms, payment processors and contact address. We have no connection to it.
Which CrawlCheck came first?
crawlcheck.io. Its domain and first certificate date from 12 August 2026 and its reports have been sealed to Bitcoin daily since 13 August. crawlcheck.dev's domain and first certificate date from 18 September 2026.
Did crawlcheck.io copy crawlcheck.dev?
No. crawlcheck.io was live, scanning and publishing for 37 days before crawlcheck.dev's domain was registered, and public registry, certificate and blockchain records show it.
Is crawlcheck.com yours?
No. It was registered in 2011 by someone else and had no working website when we checked on 25 September 2026.
How do I know I am on the real CrawlCheck?
The address is crawlcheck.io, email comes from @crawlcheck.io, and payment is only through Stripe links on crawlcheck.io.
I was charged by Paddle or Lemon Squeezy for a CrawlCheck report. Is that you?
No. We only use Stripe. crawlcheck.dev's terms name Paddle and Lemon Squeezy as its merchants of record and offer refunds through hi@crawlcheck.dev.
Related findings
Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed.
Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.