Site traffic
Every request to any site on this Pi (wiki, Qwordy, Wiring, Tilt) passes through Caddy, which writes one line per request. This page reads those lines. No tracking script is needed for any of it: it's what a browser sends on its own. Pi Info covers the hardware.
Logging started Oct 22, 2026 12:00 AM (LA time). A visitor is one IP address + browser on one day; a page view is a page a person (not a bot) loaded.
Page views by hour LA time
Who visits
"Came from" is the Referer header on a visitor's first page. Country is Cloudflare's lookup of the IP; the edge is the Cloudflare data center nearest the visitor.
Sites page views
- qwordy.wiki-doc.com 250%
- wiki-doc.com 250%
Top pages page views
- wiki / 250%
- qwordy / 125%
- qwordy /trivia 125%
Came from visitors
- Direct / bookmark 3100%
Countries visitors
- US 267%
- NL 133%
Cloudflare edge visitors
- Ashburn 133%
- San Jose 133%
- Amsterdam 133%
Browsers visitors
- Safari 267%
- Chrome 133%
Operating systems visitors
- iOS 267%
- Windows 133%
Devices visitors
- Phone 267%
- Desktop 133%
Languages visitors
- zh 267%
- en 133%
Recent visitors
The trail of pages each one viewed, newest first. Everything here came from request headers.
| Last seen | From | Using | Came from | Pages |
|---|---|---|---|---|
| Oct 22 12:46 AM | NL
speaks en |
Chrome · Windows Desktop |
direct | //
2 pages |
| Oct 22 12:15 AM | US
speaks zh |
Safari · iOS Phone |
direct | /trivia
1 page |
| Oct 22 12:12 AM | US
speaks zh |
Safari · iOS Phone |
direct | /
1 page |
Bots and scanners
Search engines, AI crawlers, link previews and uptime checkers name themselves in the User-Agent.
Scanners try paths like /wp-login.php or /.env on every server on the internet,
hoping for a misconfigured WordPress or a leaked password file. There is none here, so they get a 404.
Bots and crawlers requests
- MJ12bot 20175%
- SemrushBot 5922%
- ClaudeBot 62%
- (no user agent) 21%
- python-requests 10%
Probed for weaknesses requests
- /wp-includes/wlwmanifest.xml 16%
- /xmlrpc.php 16%
- /blog/wp-includes/wlwmanifest.xml 16%
- /web/wp-includes/wlwmanifest.xml 16%
- /wordpress/wp-includes/wlwmanifest.xml 16%
- /website/wp-includes/wlwmanifest.xml 16%
- /wp/wp-includes/wlwmanifest.xml 16%
- /news/wp-includes/wlwmanifest.xml 16%
- /2018/wp-includes/wlwmanifest.xml 16%
- /2019/wp-includes/wlwmanifest.xml 16%
- Other 844%
Responses requests
- 404 28297%
- 200 72%
- 201 21%
Your request
Exactly what your browser sent to load this page, after Cloudflare and Caddy added their notes. Every visitor sends the same set. This table is shown only to you and isn't saved anywhere beyond the access log.
| Header | Your value | What it tells the server |
|---|---|---|
| Your IP address Cf-Connecting-Ip |
216.73.217.114 | Where on the internet you are. Maps to your internet provider and a rough location (often the city). The closest thing to an identity a server gets for free. |
| Country Cf-Ipcountry |
US | Cloudflare looks your IP up and adds the country. |
| Cloudflare data center Cf-Ray |
a4e70ef5bdc72f31-CMH | A request ID. The last three letters are the airport code of the Cloudflare data center you reached, usually the one nearest you. |
| Browser and device User-Agent |
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected]) | Browser and version, operating system, and phone vs computer. Bots usually name themselves here. |
| Formats Accept |
*/* | The file types the browser can handle. |
| Compression Accept-Encoding |
gzip, br | gzip, br (Brotli), zstd: which compressions the browser understands. |
| Scheme Cf-Visitor |
{"scheme":"https"} | Whether you used https (between you and Cloudflare). |
| Scheme, last hop X-Forwarded-Proto |
http | http: the tunnel hands requests to Caddy over plain HTTP inside the Pi. |
| IP, last hop X-Forwarded-For |
127.0.0.1 | The standard header for the visitor's IP. Caddy only sees the tunnel on this Pi (127.0.0.1), which is why Cloudflare sends Cf-Connecting-Ip. |
| Hostname X-Forwarded-Host |
wiki-doc.com | Which site you asked for, added by Caddy. |
| Hostname Host |
wiki-doc.com | Which site you asked for. One Pi serves several. |
| Tunnel Cf-Warp-Tag-Id |
bf527c85-0bbc-4736-aa6e-e6aaecbf9747 | Which Cloudflare tunnel connection carried it to the Pi. |
| Plumbing Cdn-Loop |
cloudflare; loops=1 | Cloudflare marks requests it has passed along, to catch loops. |
What a script on the page can add
Headers are only the start. JavaScript running in your browser can read much more, and analytics scripts (this wiki runs Google Analytics) send it home. Read just now by this page; none of it was sent anywhere.
| What | Yours | Why it matters |
|---|
What the server can't see
- Who you are. No name or email unless you type it in. An IP points at a household or a phone carrier, not a person.
- The exact address. IP location is usually right about the country and often about the city, rarely closer. Cloudflare can add a city header; it's off here.
- Time on a page. The server only sees requests. Time between two page loads hints at it; the last page of a visit is a blank.
- Scrolling, clicks, mouse movement. Only a script can report those.
- The same person on two devices, or across days once the IP changes. That's why analytics companies want you to log in.
- Visits served from cache. Cloudflare and your browser keep copies of images and scripts, so those requests never reach the Pi.