Autonomous System
AS140096
Last fetched
AS140096 is operated by JINX-AS-AP - JINX CO., LIMITED, registered in HK, and announces 20 prefixes to 10 BGP neighbours. AS140096 has a reputation score of 12.6 (NEUTRAL); 0 of its 3,328 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 20
- BGP neighbours
- 10
- RPKI ROAs
- 37
- MOAS conflicts
- 0
- CAIDA AS-rank
- 3,861
- Customer-cone ASNs
- 6
- Facilities
- 24
- Internet exchanges
- 2
- Customer degree
- 3
- Peer degree
- 3
- Provider degree
- 4
- 103.55.5.0/24
- 103.169.217.0/24
- 124.108.20.0/24
- 161.129.42.0/24
- 161.129.46.0/24
- 182.255.32.0/24
- 182.255.33.0/24
- 182.255.32.0/22
- 182.255.35.0/24
- 199.15.76.0/24
- 199.15.76.0/23
- 199.15.77.0/24
- 199.15.78.0/24
- 199.15.78.0/23
- 199.15.79.0/24
- 2400:cca0:2101::/48
- 2401:d9c0:2000::/44
- 2401:d9c0:2010::/44
- 2401:d9c0:2000::/36
- 2604:d6c0::/32
Infrastructure presence
Internet exchanges (2 total)
Facilities (24 total)
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix SV8 - Silicon Valley, Palo Alto
- Equinix SG1 - Singapore
- Equinix SV3 - Silicon Valley, San Jose
- Equinix SV2 - Silicon Valley, Santa Clara
- Equinix SV4 - Silicon Valley, Sunnyvale
- Equinix TY2 - Tokyo
- Digital Edge TYO2 (ComSpace 1) - Tokyo
- AT TOKYO (CC1/CC2)
- Equinix HK2 - Hong Kong
- COLT in Asia Tokyo Data Center 1 (TDC1)
- Equinix TY4 - Tokyo
- MEGA Two (iAdvantage Hong Kong)
- Equinix TY6 - Tokyo
- Otemachi Place West Tower (BBTower Shin-Otemachi)
- NTT DOCOMO BUSINESS Tokyo (NW1)
- NTT DOCOMO BUSINESS TK1 - Tokyo (NTT Otemachi)
- Digital Realty Tokyo - NRT10
- SCSK netXDC (SI1/SI2/SI3)/NEC Inzai DC
- IIJ Shiroi DCC
- IIJ Ikebukuro DC
- MEGA Gateway (iAdvantage Hong Kong)
- AT TOKYO (CC3)
- NTT ME Ikebukuro DC
Route origin authorizations
A sample of 10 of this network’s 37 ROAs.
- 103.116.72.0/22 · max length /24
- 103.169.216.0/24 · max length /24
- 103.169.217.0/24 · max length /24
- 103.200.112.0/23 · max length /24
- 103.55.4.0/23 · max length /24
- 124.108.20.0/23 · max length /24
- 177.0.134.0/24 · max length /24
- 182.255.32.0/22 · max length /24
- 2400:cca0:2101::/48 · max length /48
- 161.129.42.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS140096.
Blast radius
- Announced IPv4 addresses
- 3,328
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 15
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: clean.
Peering ecosystem
A sample of 10 of this network’s 10 BGP neighbours.
- MISAKA - Misaka Network, Inc. · AS917
- CAELUS-AS - Caelus Technology LLC · AS1405
- HURRICANE - Hurricane Electric LLC · AS6939
- CTCSCITECHLIMITED-AS-AP - CTCSCI TECH LIMITED · AS9886
- MNI-AS-AP - Misaka Network, Inc. · AS23961
- LIBERALLY-INTERNATIONAL - Liberally Network, LLC · AS32595
- PANLIANTECHNOLOGYCOLIMITED-AS-HK - PAN-LIAN TECHNOLOGY CO., LIMITED · AS137897
- JINXCOLIMITED-AS-AP - JINX CO., LIMITED · AS150684
- YunZheng-Network - zhenyun sun · AS204921
- PRIME-SEC - Prime Security Corp. · AS400618
Reputation
12.6reputation score (NEUTRAL)
AS140096 (JINX-AS-AP - JINX CO., LIMITED, HK) has a reputation score of 64.9 (NEUTRAL).
- Threat density
- 51.7/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 85.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- JINX CO., LIMITED
- RIR
- APNIC
- Registered
- Mon, 09 Jan 2023 05:53:26 GMT
- Abuse contact
- abuse@jinx.cloud
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS140096 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.