[ whoami ]

what your connection and browser tell every website. nothing here is stored.

connection
ip (seen)
216.73.216.86
ipv4
checking…
ipv6
checking…
location
Columbus, Ohio, US · NA
timezone (ip)
America/New_York
network
AS16509 Amazon.com, Inc.
cloudflare edge
…
http / tls
…
warp
…
dnt / gpc
off / off
browser & device
browser
ClaudeBot 1.0
os
?
device
bot
leak tests
webrtc
press run — checks whether WebRTC exposes local or VPN-bypassing IPs
timezone
…
dns
press run — shows which DNS resolvers your lookups really go through (uses the bash.ws test service)
speed test
edge
–
ms to cloudflare
ping
–
ms to s1d
down
–
Mbit/s
up
–
Mbit/s

edge = round trip to the nearest Cloudflare data centre; the rest is measured against this server (Germany), through Cloudflare.

fingerprint

signals a site can read without asking. more bits = easier to single you out. estimates come from published browser-fingerprinting studies, not from tracking you.

signalvalue~bits
request headers your browser sent
hosts1d.me
user-agentMozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
accept*/*
accept-encodinggzip, br
cdn-loopcloudflare; loops=1
cf-connecting-ip216.73.216.86
cf-ipcityColumbus
cf-ipcontinentNA
cf-ipcountryUS
cf-iplatitude39.96118
cf-iplongitude-82.99879
cf-metro-code535
cf-postal-code43215
cf-raya4c2992948fdbdc9-CMH
cf-regionOhio
cf-region-codeOH
cf-timezoneAmerica/New_York
cf-visitor{"scheme":"https"}
cf-warp-tag-idd1820576-f289-4f58-a670-c76270257bd1
connectionkeep-alive
x-forwarded-for216.73.216.86
x-forwarded-protohttps
for terminals
curl s1d.me/ip          # your ip
curl s1d.me/ip.json     # {"ip": "…"}
curl s1d.me/me.json     # everything above, as json
curl s1d.me/ua          # your user agent
curl s1d.me/headers     # headers as received