What does an LLM actually understand about your website?
What does it know about it? And what does it believe about it?
Not whether your meta tags are filled in. Not whether your images have alt text. Something harder: when a model looks at your site with nobody telling it what to care about, what does it come away believing?
I built 3Drake to find out, and I made every answer public.
Here is the entire prompt. All of it:
"What do you understand about this website? What information do you have about it? And what do you believe about it?"
Then: give it a number.
No criteria. No checklist. No scale. No examples. Nothing else is sent.
How it works:
→ You paste a domain or a URL. That's the whole input. Nothing else to fill in.
→ Each model goes and fetches your website itself, live, with its own tools. It's judging what your site is right now, not what it memorised months ago.
→ From there the reasoning is entirely the model's. It decides what matters about this particular website, judges it against that, and picks a number.
→ The score has no limit. It can be 0. It can be 1. It can be 1,000,000. That is the model's call and neither you nor I get to intervene.
Three frontier models run on every submission, deep reasoning on, at the same moment:
claude-opus-5
gpt-5.6-terra
gemini-3.7-flash
Not the cheap tier. The entire idea collapses if the model is pattern matching instead of actually thinking.
The three scores are added up, and that total is your place on a public leaderboard. Every review, from every model, is readable by anyone.
Free. No account. No sign up. No ownership verification. Scores lock for 24 hours, then you can be re-scored.
One thing said up front rather than left for you to discover: this is a subjective AI opinion. A genuinely great website can be handed a 0. AI can make mistakes. The reasoning is the real content — the score is just the headline.
https://t.co/CYuxQ5TUEm
@Hostinger How would you feel if you started your workday only to find your website malfunctioning—after having previously tried to fix the issue without receiving a response or a definitive solution from your hosting provider?
@Hostinger — I've been dealing with recurring 522 errors on my VPS for over a week now, and after multiple support contacts I still don't have a single technical answer. Posting publicly because private channels went nowhere.
I'm a backend engineer. I run production workloads on this server and I configured it myself.
What's happening:
• ~1 week ago: first wave of 522s. I contacted Cloudflare — they confirmed the problem is not on their edge. I contacted Hostinger and got no response at all. The errors eventually stopped on their own, with zero changes from my side.
• Sep 5: 522s came back. I contacted support again, went through the chat agent, then switched to human support. The answer I got was a generic "check your firewall settings" guide.
• Sep 6 (today): down again.
The frequency is increasing, not decreasing.
Why "check your firewall" isn't an answer here:
A 522 is generated by Cloudflare's edge when it can't open a connection to the origin. My home network, my router and my browser are not in that path — the failure is between a Cloudflare datacenter and the VPS. Nothing I do on my laptop can cause or fix it. I also haven't changed my network, my router, or any firewall rule on the server.
And if it were a firewall rule, it would fail consistently. This doesn't. It fails at random, recovers on its own, then fails again. That pattern points at something on the host side — node health, networking on the node, or something intermittently dropping traffic to my origin IP.
What I'm asking for:
Someone who can actually look at the infrastructure — host node status, network/routing for my VPS, and whether anything is throttling or dropping connections to my origin IP. I can provide exact timestamps, Cloudflare Ray IDs and origin-side logs immediately.
One more thing: I was never given a ticket ID. I went from the automated agent to human support and the conversation just ended, with no reference number and no follow-up. That alone is a problem — I have no way to reference any of my previous reports.
I'm a paying customer running production workloads. I'm not asking for a troubleshooting checklist. I'm asking for a root cause.
@Hostinger I sent them evidence of the error, but the response I got was just an automated bot reply. A disappointing experience with Hostinger's service.
You are:
Builders
Indie hackers
Founders
Vibe coders
AI enthusiasts
Digital nomads
Freedom lovers
You all have one thing in common: a website nobody asked an AI about.
Drop your URL 👇
Claude, GPT and Gemini will read it and tell you what they actually think.
https://t.co/CYuxQ5TUEm