3 ms·
That website doesn't work from my ISP. Can't even ping it or nc -z 104.37.63.7 443. Edit update: Your security infrastructure is broken because I don't know wh
by 1letterunixname 3y ago
That website doesn't work from my ISP. Can't even ping it or nc -z 104.37.63.7 443.
Edit update: Your security infrastructure is broken because I don't know what that is and don't use Twitter. If you check the AS, it's Google Fiber. And I'd appreciate it if you wouldn't dox me.
- kazinator 3y agoNot sure why. Out of the 26 IP addresses that accessed the egawk repository in the last day or so, only one was banned. The client identified as Twitterbot, coming from 136.49.X.X.
- wizzwizz4 3y agoThat isn't your dox: if you can't even ping it, you wouldn't have been able to request a specific repository, and won't appear in that access log.
- kazinator 3y agoI made it clear it's something reporting itself as "Twitterbot". Unlikely to be your web browser, unless you went out of your way to impersonate Twitterbot. Still, I only quoted two octets out of the IPv4 Class B address, even though I feel that it would be fine to reveal the full address of a bot.