lawaPangram 100% Human badge

lawa is my web crawler. It crawls the web and writes down the HTTP headers that come back from each site. Everything below is regenerated every few minutes from what it has seen so far.

Status

lawa iscrawling
pace1,301 requests in the last minute
servers visited7,153,992 finished, 825 in progress
servers waiting in line9,157,743
responses studied below83,249,542 from 6,202,513 servers
numbers as of2026-11-05 11:11 UTC

The shares below are measured by hostname. Additionally, lawa takes at most 25 pages from any one server, and each server is counted once, when lawa has finished with it.

Web servers seen

Server headerserversshare
cloudflare1,621,15926.1%
apache1,126,65118.2%
nginx1,073,23417.3%
(none)515,0818.3%
gse232,3973.7%
openresty221,1393.6%
squarespace220,2803.6%
litespeed159,4522.6%
github.com116,7151.9%
vercel97,6561.6%

13.7% of the servers that name themselves also announce their version number.

X-Powered-Byserversshare of those sending it
php 8259,71236.8%
php 788,30612.5%
asp.net87,59812.4%
next.js59,2008.4%
php 530,2334.3%
plesklin29,3324.2%
express26,9713.8%
wp engine22,7153.2%

Bad time

A Date only has one‐second resolution and the network adds delay, so I decided that β€œon time” means β€œwithin 2Β seconds, from my perspective”.

server clockserversshare
on time5,451,62898.6%
up to 10Β seconds off21,9460.4%
10Β seconds to a minute18,3000.3%
a minute to an hour35,2540.6%
an hour to a day3,3080.1%
more than a day1660.0%

Of the 78,974 wrong clocks, 53,827 run slow and 25,147 run fast. 1,368 are wrong by a whole number of hours, which is likely timezone problems rather than drift. 48,535 servers sent no Date at all, and 884 sent malformed Dates.

Responses served from a cache (indicated by an Age header) are left out. 620,689 servers only ever answered that way.

Security headers

headerserversshare
HSTS (share of HTTPS servers)1,943,45138.6%
X-Content-Type-Options2,713,09843.7%
X-Frame-Options1,731,36527.9%
Content-Security-Policy1,088,58317.6%
Referrer-Policy1,037,59216.7%
Permissions-Policy496,1468.0%
X-XSS-Protection (deprecated)1,072,42117.3%

TLS

81.2% of servers answered over HTTPS at least once. lawa connects even when the certificate is bad, so here’s what was wrong. 2.1% of HTTPS servers would have failed in a browser.

certificate problemserversshare of HTTPS
wrong hostname59,9521.2%
unknown or incomplete issuer25,6640.5%
expired25,4980.5%
self‐signed11,6330.2%
protocolserversshare of HTTPS
TLSv1.34,697,49793.3%
TLSv1.2336,7006.7%
certificate authorityserversshare of HTTPS
Let's Encrypt2,864,49556.9%
Google Trust Services1,238,03824.6%
Sectigo Limited208,7604.1%
Amazon172,2423.4%
DigiCert Inc164,0393.3%
GoDaddy.com78,5171.6%
GlobalSign nv-sa61,9821.2%
ZeroSSL GmbH22,4750.4%

Other quirks

lawa speaks my handrolled HTTP/1.1 implementation and logs each header block as the raw bytes, so we can see some stuff that HTTP libraries usually clean up.

quirkserversshare
same header sent more than once1,284,99420.7%
every header name in lowercase334,0885.4%
answered HTTP/1.1 with HTTP/1.037,7230.6%
bare LF line endings (no CR)7140.0%
folded (multi‐line) header values4030.0%

The average response carried 15.2 header lines in 818Β bytes. In total, lawa has read 68.09Β GB of headers.

Status codes

statusresponsesshare
20063,552,24984.8%
3016,130,1998.2%
4041,766,8842.4%
3021,746,4842.3%
403757,9211.0%
308286,1570.4%
307229,1870.3%
429116,1790.2%

2,111 responses were 418 I'm a teapot, and 516 were 451 Unavailable For Legal Reasons. lawa asked for 12,532,017 robots.txt files and, because of what they said, left 2,537,890 pages alone. it walked away from 101,895 servers entirely because of 429, 503, or repeated 403s, and 617,508 linked‐to servers turned out not to exist any more.

Where the W3 is from

networkserversshare
Cloudflare, Inc.1,366,24522.4%
Amazon.com, Inc.730,03911.9%
Google LLC402,3576.6%
Squarespace, Inc.220,2433.6%
Fastly, Inc.187,4783.1%
Hetzner Online GmbH171,4572.8%
OVH SAS144,2122.4%
Cloudflare London, LLC138,7552.3%
IONOS SE117,6321.9%
Microsoft Corporation78,7891.3%
countryserversshare
United States2,043,86345.3%
Germany573,75312.7%
Canada307,9946.8%
Japan186,6384.1%
France180,5174.0%
United Kingdom149,3153.3%
The Netherlands140,9893.1%
Switzerland88,9072.0%
Italy61,3581.4%
Russia60,6701.3%

Countries leaves out the 1,692,478 servers behind Cloudflare and Fastly, because an anycast address is in every country at once. IP geolocation by DB-IP.

top‐level domainserversshare
.com2,832,84845.7%
.org587,2749.5%
.de349,2155.6%
.net194,7053.1%
.uk171,1142.8%
.jp131,3952.1%
.io129,2182.1%
.ch98,8341.6%
.fr95,6881.5%
.nl78,8951.3%

Non‐standard headers

headerserversshare
cf-ray1,627,68326.2%
cf-cache-status1,151,75618.6%
x-cache521,9888.4%
x-served-by345,3985.6%
x-request-id253,3944.1%
cf-edge-cache227,1193.7%
x-proxy-cache223,1843.6%
x-contextid222,4453.6%
x-permitted-cross-domain-policies220,1243.5%
x-cache-hits210,3183.4%
x-redirect-by209,1623.4%
x-timer196,8203.2%

1,422 servers (0.02%) send an Onion-Location header, which invites Tor Browser users to a .onion mirror of the site.

And of course, X-Clacks-Overhead. 10,019 servers send it:

X-Clacks-Overheadserversshare
GNU Terry Pratchett8,72187.0%
GNU Natalie Nguyen5095.1%
GNU Terry Pratchett, Stephen Hawking, Pr460.5%
GNU Terry Pratchett Going Postal210.2%
GNU Terry Pratchett, Douglas Adams, Step170.2%

record holders

recordvalueserver
slowest clock56.8Β years behindwww.ara.am
fastest clock136.0Β years aheadedventurebuilder.com
oldest Last-Modified1991-10-16quimby.gnus.org
biggest header block66,688Β byteswww.mydreamstable.com
most header lines918www.mydreamstable.com
most cookies in one response910www.mydreamstable.com
farthest from this site42 links awayelliottlevin.com

35,021 pages claimed implausibly old Last-Modified (before the W3 existed, mostly 1970 (epoch fail!)) and 18,284 claimed one from the future; neither counts.

Details

lawa obeys robots.txt (its name there is β€œlawa”), waits at least ten seconds between requests to the same server, and takes at most 25 pages from any one. If it is bothering you, a robots.txt rule is honored within a day, and I read my email robin@dreamstation.systems regularly.

Figures cover 2026-09-20 05:43 UTC to 2026-11-05 09:31 UTC (515 data segments); the crawl is constantly running, and the newest ~45Β minutes are not in yet.