· ~5 min read

What hit my static site in its first week online

Fifteen thousand requests in five days, more than half of them looking for files that do not exist: .env files, git configs, WordPress installers and cloud credentials. A breakdown of who came, what they tried, and why none of it worked.

Why look

This site moved to its own domain, viotnet.com, on 7 November. A day later a "new website" directory emailed me to say it had found it. That made me curious about who else had. Cloudflare sits in front of the site, so I pulled the last week of edge analytics with a read-only API token and sorted through it.

The window is 7 to 12 November 2026, a little over five days. The numbers come from Cloudflare's analytics for the zone; on the free plan, detailed per-request data is sampled and kept only for a short time, so treat them as close estimates, not exact counts. I am not publishing any IP addresses: they are personal data, and the countries and tools tell the story well enough.

The headline numbers

RequestsShare
Total15,470100%
404 Not Found8,16353%
301 redirects (www and the old pages.dev address)4,03826%
200 OK2,79318%
Blocked or refused (403, 405)3702%
Timeouts on ports the site does not serve (5xx)about 4703%

More than half of everything that reached the site asked for a page that has never existed. The real readers are in the 200s: the home page about 1,900 times, each post between 35 and 45 times, and the Greek pages a few dozen times each.

Who came

Sorted by the User-Agent each client sent, which a client can fake, so this is what they claimed to be:

KindRequestsExamples
Looks like a browser8,385many are scanners using a browser string
Declared security scanners5,004"TLM-Audit-Scanner" (4,483), LeakIX (369), Censys, internet-measurement.com
Scripts and libraries831curl (594), Go, python-requests, aiohttp, okhttp
AI crawlers146GPTBot (66), ClaudeBot (63)
Search engines138Googlebot
SEO crawlers and link previews41serpstatbot, Facebook

One client did not even bother with a believable User-Agent: it sent the URL of a WordPress installer as its name, 490 times.

By country, the Netherlands led with about 6,400 requests, then the United States, Singapore, Germany and Japan. That does not mean Dutch people love this blog: those countries host a lot of cheap cloud servers, which is where scanners run from. The failed requests (4xx) came mostly from the Netherlands, Singapore, Russia and the US.

What they were looking for

Grouping the 4,700 failed requests by what the path was after:

TargetRequestsTypical paths
Secrets and config files2,252/.env, /.env.production, /.env.local, /.git/config, /.aws/credentials, /config.json
WordPress987/wp-admin/install.php, /wp-login.php, /xmlrpc.php, wlwmanifest.xml under 15 different folders
PHP files and shells275/info.php, /phpinfo.php
Admin panels137login and management pages
Application internals79/actuator/env (Spring Boot)

A few patterns stand out:

What Cloudflare stopped

Cloudflare's free managed rules blocked about 260 requests outright before they reached the site. Most were looking for backups of a WordPress config file: wp-config.php.bak, .old, .save, .swp, ~, .orig. These are the copies an editor or a hurried admin leaves behind, and they contain the database password in plain text.

Why none of it worked

This site is static: plain HTML and CSS files, no server-side code, no database, no admin panel, no JavaScript and no forms. There is no .env to leak because nothing on the server reads environment variables. There is no WordPress to hijack. A POST request has nothing to talk to and gets a 405. Every probe above ended in a 404, a redirect to a 404, or a block. I checked the most-requested paths by hand afterwards to make sure.

That is the real lesson. The most effective defence here was not a firewall rule, it was having almost nothing to attack. The attack surface of a static site is the hosting platform and the account that controls it, which is why the Cloudflare account sits behind a hardened Google login with two-factor authentication.

What I am changing

If you run anything on the public internet, look at your own logs for .env and .git requests. The bots already have.

Want the configs or code from this lab, or have a question? Email me at papas@viotnet.com

← all posts