who dis is?

{'ip': '216.73.216.101',
 'location': {'city': 'Columbus',
              'country': 'US'},
 'device': {'family': 'Spider',
            'brand': 'Spider',
            'model': 'Desktop'},
 'os': {'family': 'Other'},
 'browser': {'family': 'ClaudeBot',
             'major': '1',
             'minor': '0'}}

1) What

simple demo illustrating information leakage during web requests

also available:

• https://whodis.fyi/data.json
• https://whodis.fyi/data.png
• https://whodis.fyi/data.jpeg
• https://whodis.fyi/data.full.png
• https://whodis.fyi/data.full.jpeg

embed it

the images above are ordinary image URLs — anywhere they load (forum posts, markdown docs, email, chat), the fetch itself makes the same information available to this server as loading the page does. loading an image is a request, and every request leaks.

you can label a request for your own reference, e.g. https://whodis.fyi/data.png?tag=whatever — the tag is simply echoed back to whoever loads it, like every other field. note that email providers (gmail, outlook) usually fetch images through a proxy, so the data shown there is the proxy's, not the recipient's.

(src)

stats

top requesters since server was last restart: