IPv4 address
202.254.239.14
Last fetched
202.254.239.14 is announced in 202.254.236.0/22 by XSERVER - Xserver Inc. and geolocates to JP. 202.254.239.14 is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- no-data
Nutrition Label
Attribution
- Announced prefix
- 202.254.236.0/22
- Announcing network
- XSERVER - Xserver Inc.
- RIR-registered prefix
- 202.240.0.0/12
- RPKI
- valid
Anycast detection
This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.
Reverse DNS
- akatunagi.com
- mta-sts.akatunagi.com
- www.akatunagi.com
- edamichi.com
- mta-sts.edamichi.com
- www.edamichi.com
- harulc.com
- mta-sts.harulc.com
- www.harulc.com
- hive0812.com
- mta-sts.hive0812.com
- www.hive0812.com
- imekana.com
- www.imekana.com
- izumi-golfclub.com
- mta-sts.izumi-golfclub.com
- www.izumi-golfclub.com
- kochisogopg.com
- mta-sts.kochisogopg.com
- www.kochisogopg.com
- kyonan-marketing.com
- hostmaster.kyonan-marketing.com
- www.kyonan-marketing.com
- magchannelblog.com
- mta-sts.magchannelblog.com
- www.magchannelblog.com
- monokanso.com
- www.monokanso.com
- nokogiri-blog.com
- mta-sts.nokogiri-blog.com
- www.nokogiri-blog.com
- relatrfuu.com
- mta-sts.relatrfuu.com
- www.relatrfuu.com
- saienkiroku.com
- www.saienkiroku.com
- mta-sts.shine-eyelash.com
- www.shine-eyelash.com
- societycache.com
- mta-sts.societycache.com
- www.societycache.com
- sonoue.com
- www.sonoue.com
- watch-encount.com
- www.watch-encount.com
- xn--showroom-2e5qt48cnw1c.com
- mta-sts.xn--showroom-2e5qt48cnw1c.com
- www.xn--showroom-2e5qt48cnw1c.com
- jitenon.co.jp
- corp.jitenon.co.jp
Geographic detail
- Country
- JP
- Dominant city of the prefix
- Chiyoda, JP
Threat-feed evidence
History
Related pages
Pivot from 202.254.239.14 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "202.254.239.14"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.