I see this ip address actively accessing gmail account in spite of 2-Step Verification.
whois 243.25.203.20 produces following message: No whois server is known for this kind of object.
How can I find out what functionality uses this ip?
I see this ip address actively accessing gmail account in spite of 2-Step Verification.
whois 243.25.203.20 produces following message: No whois server is known for this kind of object.
How can I find out what functionality uses this ip?
As @tripleee said in his comment, looks like it is an IP from a reserved block, so it should not be public routable on the Internet (in an ideal world, that is :D).
You can check by specifying an explicit whois server, for example
$> whois -h whois.ripe.net 243.25.203.20
returns
inetnum: 243.0.0.0 - 243.255.255.255
netname: IETF-RESERVED-ADDRESS-BLOCK
descr: IPv4 address block reserved by the IETF
remarks: ------------------------------------------------------
remarks:
remarks: This address block is reserved by the IETF
remarks:
remarks: You can find more information on the IANA registry page:
remarks: http://www.iana.org/assignments/ipv4-address-space
remarks:
remarks: ------------------------------------------------------
Checking on public looking glasses returns empty results, too:
route-views>sho ip ro 243.25.203.20
% Network not in table
route-views>sho ip bgp 243.25.203.20
% Network not in table
It could be a spoofed IP Address but more likely someone is hijacking unused address space.
Read up on ipv6 address coercion.
- "Address coercion" protects IPv4-only code from IPv6
- Take IPv6 address
- Remove user-modifiable bits
- Hash into 224.0.0.0/3
- Sometimes not perfect
- "Your last login was from 238.1.2.3"
I'm pretty sure Google came up with hashing IPv6 into the 224.0.0.0/3 subnet for IPv6 unaware apps.
Guess OP must have found some edge case...
As kasperd said it'd be nice to understand what the edge case is though so they can fix it...
That's "class E" address space -- 240/4, aka. the space beyond multicast. It is not a valid internet address. (and never will be.) Almost no commercial network gear will even allow assigning such an address.
The only "internet" source I'm aware of that even remotely uses that range is Cloudflare. And it's only for IPv6-to-IPv4 proxied traffic (X-Forwarded-For header), with explicit admin opt-in.
Ultimately, you'd have to ask Google (good luck with that) how such an address can appear in their gmail headers.