Autonomous System
AS134238
Last fetched
AS134238 is operated by CT-Jiangxi-IDC - CHINANET Jiangx province IDC network, registered in CN, and announces 118 prefixes to 13 BGP neighbours. AS134238 has a reputation score of 12.2 (NEUTRAL); 24 of its 83,712 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 118
- BGP neighbours
- 13
- RPKI ROAs
- 116
- MOAS conflicts
- 0
- CAIDA AS-rank
- 13,719
- Customer-cone ASNs
- 1
- Facilities
- 0
- Internet exchanges
- 0
- Customer degree
- 0
- Peer degree
- 0
- Provider degree
- 1
- 59.53.48.0/23
- 59.53.49.0/24
- 59.53.51.0/24
- 59.53.52.0/22
- 59.53.56.0/21
- 59.53.60.0/24
- 59.53.64.0/24
- 59.53.67.0/24
- 59.53.69.0/24
- 59.53.70.0/23
- 59.53.64.0/20
- 59.53.72.0/24
- 59.53.73.0/24
- 59.53.84.0/24
- 59.53.85.0/24
- 59.53.90.0/23
- 59.53.92.0/22
- 59.53.95.0/24
- 59.63.156.0/22
- 59.63.159.0/24
- 59.63.160.0/23
- 59.63.164.0/24
- 59.63.167.0/24
- 59.63.160.0/19
- 59.63.177.0/24
Routing posture
- Hijack posture score
- 0.18
- Origin mismatches
- 1
Route origin authorizations
A sample of 10 of this network’s 116 ROAs.
- 106.225.128.0/19 · max length /19
- 106.225.128.0/22 · max length /22
- 106.225.128.0/24 · max length /24
- 106.225.129.0/24 · max length /24
- 106.225.132.0/22 · max length /22
- 106.225.134.0/24 · max length /24
- 106.225.136.0/21 · max length /21
- 106.225.144.0/24 · max length /24
- 106.225.145.0/24 · max length /24
- 106.225.146.0/23 · max length /23
Upstreams
The networks that most often share an observed BGP path with AS134238.
Blast radius
- Announced IPv4 addresses
- 83,712
- Threat-listed addresses
- 24
- Threat density
- 0.0287 %
- Routed prefixes
- 108
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 13 of this network’s 13 BGP neighbours.
- CHINANET-BACKBONE - No.31,Jin-rong Street · AS4134
- CHINATELECOM-JIANGXI-SHENGJI-5G-NETWORK - CHINATELECOM Jiangxi province Shengji 5G network · AS140852
- CHINATELECOM-JIANGXI-NANCHANG-5G-NETWORK - CHINATELECOM Jiangxi province Nanchang 5G network · AS140853
- CHINATELECOM-JIANGXI-JIUJIANG-5G-NETWORK - CHINATELECOM Jiangxi province Jiujiang 5G network · AS140854
- CHINATELECOM-JIANGXI-JINGDEZHEN-5G-NETWORK - CHINATELECOM Jiangxi province Jingdezhen 5G network · AS140855
- CHINATELECOM-JIANGXI-SHANGRAO-5G-NETWORK - CHINATELECOM Jiangxi province Shangrao 5G network · AS140856
- CHINATELECOM-JIANGXI-YINGTAN-5G-NETWORK - CHINATELECOM Jiangxi province yingtan 5G network · AS140857
- CHINATELECOM-JIANGXI-YICHUN-5G-NETWORK - CHINATELECOM Jiangxi province Yichun 5G network · AS140858
- CHINATELECOM-JIANGXI-PINGXIANG-5G-NETWORK - CHINATELECOM Jiangxi province Pingxiang 5G network · AS140859
- CHINATELECOM-JIANGXI-XINYU-5G-NETWORK - CHINATELECOM Jiangxi province Xinyu 5G network · AS140860
- CHINATELECOM-JIANGXI-GANZHOU-5G-NETWORK - CHINATELECOM Jiangxi province Ganzhou 5G network · AS140861
- CHINATELECOM-JIANGXI-JIAN-5G-NETWORK - CHINATELECOM Jiangxi province Jian 5G network · AS140862
- CHINATELECOM-JIANGXI-FUZHOU-5G-NETWORK - CHINATELECOM Jiangxi province Fuzhou 5G network · AS140863
Reputation
12.2reputation score (NEUTRAL)
AS134238 (CT-Jiangxi-IDC - CHINANET Jiangx province IDC network, CN) has a reputation score of 65.5 (NEUTRAL).
- Threat density
- 78.6/100
- Graph metrics
- 55.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
- CHINANET Jiangx province IDC network
- RIR
- APNIC
- Registered
- Thu, 11 Jun 2015 06:04:42 GMT
- Abuse contact
- fjnic@fjdcb.fz.fj.cn
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS134238 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.