Autonomous System
AS45582
Last fetched
AS45582 is operated by VAINAVIINDUSTRIESLTD-IN - VAINAVI INDUSTIES LTD, INTERNET SERVICE PROVIDER, INDIA, registered in IN, and announces 67 prefixes to 12 BGP neighbours. AS45582 has a reputation score of 13.8 (NEUTRAL); 33 of its 14,336 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 67
- BGP neighbours
- 12
- RPKI ROAs
- 116
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,920
- Customer-cone ASNs
- 9
- Facilities
- 40
- Internet exchanges
- 3
- Customer degree
- 8
- Peer degree
- 2
- Provider degree
- 3
- 27.116.16.0/24
- 27.116.17.0/24
- 27.116.18.0/24
- 27.116.19.0/24
- 27.116.20.0/24
- 27.116.21.0/24
- 27.116.22.0/24
- 27.116.23.0/24
- 45.112.184.0/24
- 45.112.185.0/24
- 45.112.186.0/24
- 45.112.187.0/24
- 45.118.72.0/24
- 45.118.73.0/24
- 45.118.74.0/24
- 45.118.75.0/24
- 45.249.50.0/24
- 103.10.132.0/24
- 103.10.133.0/24
- 103.10.134.0/24
- 103.10.135.0/24
- 103.22.172.0/24
- 103.22.173.0/24
- 103.22.174.0/24
- 103.22.175.0/24
Infrastructure presence
Internet exchanges (3 total)
Facilities (40 total)
- TATA Communications Chennai
- CtrlS Mumbai DC1
- CtrlS Hyderabad DC1
- Web Werks Mumbai 1
- Equinix MB1 - Mumbai (GPX Mumbai 1)
- Sify Greenfort - Noida
- Sify ITPL - Bangalore
- Sify Vashi - Mumbai
- Sify Tidel-DC- Chennai
- Sify Rabale - Mumbai
- Sify Airoli-DC- Mumbai
- CtrlS Noida DC1
- CtrlS Bangalore DC1
- Sify-LDT-Kolkata
- Netmagic Chandivali - MUM-DC05
- TATA Communications VSB Hyderabad
- STT Mumbai 2
- STT Hyderabad 1
- Pi Datacenters Amaravati
- Equinix MB2 - Mumbai (GPX Mumbai 2)
- Sify-DLF-Kolkata
- Sify Global Delivery Center (Hyderabad)
- NIXI Bhopal
- NIXI Indore
- NIXI Panaji
Route origin authorizations
A sample of 10 of this network’s 116 ROAs.
- 103.10.132.0/22 · max length /24
- 103.124.28.0/23 · max length /24
- 103.126.42.0/23 · max length /24
- 103.146.130.0/24 · max length /24
- 103.146.131.0/24 · max length /24
- 103.166.218.0/24 · max length /24
- 103.178.208.0/23 · max length /24
- 103.196.4.0/22 · max length /24
- 103.211.168.0/23 · max length /23
- 103.211.168.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS45582.
Blast radius
- Announced IPv4 addresses
- 14,336
- Threat-listed addresses
- 33
- Threat density
- 0.2302 %
- Routed prefixes
- 57
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 12 of this network’s 12 BGP neighbours.
- BBIL-AP - BHARTI Airtel Ltd. · AS9498
- CLOUDFLARENET - Cloudflare, Inc. · AS14789
- TTSL-MEISISP - Tata Teleservices ISP AS · AS45820
- RVRNET-AS - RVR Infrastructure Limited Service provider hyderabad india · AS45884
- COUNTRYONLINE-AS-IN - Country Online Services PVT LTD · AS136290
- BHARATHI-AS-IN - BHARATHI TECHNOLOGIES · AS136307
- INDWFVE - Mahindra University · AS138510
- CHOTA-AS - Chota Bheam Industries · AS141858
- VIGLOBAL-AS-IN - VI GLOBAL FIBERTEL PVT LTD · AS149227
- KSCCL-AS-IN - Karimnagar Smart City Corporation Limited · AS151114
- IRINN-ASSAI678-AS-IN - AS SAI COMMUNICATION SERVICES PRIVATE LIMITED · AS154026
- IRINN-DIGI1234-AS-IN - DIGITAL FIBER TECH PRIVATE LIMITED · AS154500
Reputation
13.8reputation score (NEUTRAL)
AS45582 (VAINAVIINDUSTRIESLTD-IN - VAINAVI INDUSTIES LTD, INTERNET SERVICE PROVIDER, INDIA, IN) has a reputation score of 62.4 (NEUTRAL).
- Threat density
- 51.8/100
- Graph metrics
- 80.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
- RIR
- APNIC
- Registered
- Fri, 19 Dec 2008 05:50:38 GMT
- Abuse contact
- naresh@vilcom.in
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS45582 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.