Autonomous System
AS7524
Last fetched
AS7524 is operated by HANSHIN - ITEC HANKYU HANSHIN CO.,LTD., registered in JP, and announces 122 prefixes to 8 BGP neighbours. AS7524 has a reputation score of 13.2 (NEUTRAL); 3 of its 366,336 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 122
- BGP neighbours
- 8
- RPKI ROAs
- 0
- MOAS conflicts
- 0
- CAIDA AS-rank
- 6,054
- Customer-cone ASNs
- 3
- Facilities
- 38
- Internet exchanges
- 6
- Customer degree
- 2
- Peer degree
- 20
- Provider degree
- 8
- 27.127.128.0/19
- 27.127.160.0/20
- 27.127.160.0/19
- 27.127.176.0/20
- 61.115.208.0/20
- 61.121.192.0/22
- 61.121.196.0/23
- 61.121.199.0/24
- 61.121.201.0/24
- 61.121.202.0/23
- 61.121.204.0/22
- 101.50.4.0/22
- 103.2.52.0/22
- 103.67.28.0/22
- 111.67.128.0/19
- 111.67.160.0/20
- 111.67.160.0/19
- 111.67.176.0/20
- 119.63.160.0/20
- 119.63.160.0/19
- 119.63.176.0/20
- 119.148.104.0/21
- 125.3.200.0/21
- 133.117.172.0/22
- 133.155.0.0/19
Infrastructure presence
Internet exchanges (6 total)
Facilities (38 total)
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- Equinix TY2 - Tokyo
- Digital Edge TYO2 (ComSpace 1) - Tokyo
- NTT DATA Otemachi Bldg
- AT TOKYO (CC1/CC2)
- NTT DOCOMO BUSINESS OS2 - Osaka (Telepark Dojima Building 2)
- NTT DATA Dojima (building #4)
- COLT in Asia Tokyo Data Center 1 (TDC1)
- Equinix OS1 - Osaka
- Equinix TY4 - Tokyo
- NTT DOCOMO BUSINESS OS3 - Osaka (Telepark Dojima Building 3)
- NTT DOCOMO BUSINESS OS1 - Osaka (Telepark Dojima Building 1)
- Telehouse – OSAKA 1&2
- FRT iDC Okinawa
- Colt DC Tokyo II
- NTT DATA Mitaka DataCenter EAST
- Otemachi Place West Tower (BBTower Shin-Otemachi)
- NTT DOCOMO BUSINESS Tokyo (NW1)
- NTT DOCOMO BUSINESS TK1 - Tokyo (NTT Otemachi)
- AT TOKYO (DC12 NTT DATA Dojima(building #4))
- Equinix TY11 - Tokyo
- Digital Realty Osaka - KIX11
- Digital Realty Tokyo - NRT10
- SCSK netXDC (SI1/SI2/SI3)/NEC Inzai DC
- QTnet Fukuoka Data Center 3(QD3)
Upstreams
The networks that most often share an observed BGP path with AS7524.
Blast radius
- Announced IPv4 addresses
- 366,336
- Threat-listed addresses
- 3
- Threat density
- 0.0008 %
- Routed prefixes
- 121
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 8 of this network’s 8 BGP neighbours.
- IIJ - Internet Initiative Japan Inc. · AS2497
- KDDI - KDDI CORPORATION · AS2516
- BIGLOBE - BIGLOBE Inc. · AS2518
- VECTANT - ARTERIA Networks Corporation · AS2519
- HURRICANE - Hurricane Electric LLC · AS6939
- RETN-AS - RETN Limited · AS9002
- JTCL-JP-AS - JCOM Co., Ltd. · AS9824
- Tamatele-NET - Tamashima TV Inc. · AS23775
Reputation
13.2reputation score (NEUTRAL)
AS7524 (HANSHIN - ITEC HANKYU HANSHIN CO.,LTD., JP) has a reputation score of 63.6 (NEUTRAL).
- Threat density
- 66.0/100
- Graph metrics
- 65.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
- ITEC HANKYU HANSHIN CO.,LTD.
Threat-feed evidence
Related pages
Pivot from AS7524 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.