Google has publicly stated that around 30% of their code is now generated by AI. That number sounds impressive - until you start to think about what it really means for efficiency and quality.

Here is a simple experiment you can try yourself - open a new Incognito window in Chrome and visit google.com. Then, open Developer Tools → Network and take a look at what’s being downloaded. You’ll find that the browser fetches roughly 848 kB of mixed resources. Remarkably, about 95.7% of that payload consists of minified JavaScript code.

Now, for comparison, open another new Incognito window and navigate to karaqu.com/guest/inbox. This loads a fully functional email client, running under a guest account. The total size of all downloaded resources? Just 427 kB.
(Karaqu platform: 332 kB, Inbox App 95 kB).

A static Google search page - pretty much a logo and a text field, requires double bandwidth than a complete web-based email client. So when we hear that nearly a third of Google’s codebase is AI-generated, it raises a fair question:
What’s the real quality of that code?

This isn’t a jab at Google’s developers. They’re some of the brightest minds in the industry. But perhaps the problem isn’t with the people writing the code, it's with who is being allowed to shape it.

While developing, configuring and hardening the security of the Karaqu mailserver, I came across internet.nl/mail/ — an excellent online tool for testing a mail domain’s security posture and compliance with modern Internet standards. It provides a detailed analysis of various aspects such as DNSSEC, TLS, DANE, and DMARC implementation.

Below is a list of domains that provide email services, along with their respective test results and observations, ranked by their score.