3 ms·

Doesn't seem the case https://apps.db.ripe.net/db-web-ui/query?searchtext=2a03:2880:20ff:d::face:b00c https://apps.db.ripe.net/db-web-ui/query?searchtext=2a03:2

Doesn't seem the case https://apps.db.ripe.net/db-web-ui/query?searchtext=2a03:2880:20ff:d::face:b00c https://apps.db.ripe.net/db-web-ui/query?searchtext=2a03:288...

Wingy 6y ago
IP packets have a source field, which can be fake and not their actual IP. That's a Facebook IP, but the packet might not have actually come from it.
- detaro 6y ago
  If they made actual requests that went through, a connection got established. That won't happen with a faked source.
  - lgats 6y ago
    Could be the IP address OP is showing is actually from an X-Forwarded header or other proxy header (but not the actual source of the packet).
  - Wingy 6y ago
    Ah okay, thanks for helping me learn :)
- thephyber 6y ago
  UDP packets can fake their source IP. TCP packets realistically can't.
  - hinkley 6y ago
    More precisely, spoofing a TCP handshake is a problem that we know how to prevent. Odds are pretty good that your kernel has these protections enabled by default, but it's not guaranteed and you should check as a matter of due diligence.