Autonomous System
AS33480
Last fetched
AS33480 is operated by WEBWERKSAS1 - Web Werks, registered in US, and announces 57 prefixes to 8 BGP neighbours. AS33480 has a reputation score of 14.4 (NEUTRAL); 4 of its 12,032 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 57
- BGP neighbours
- 8
- RPKI ROAs
- 26
- MOAS conflicts
- 2
- CAIDA AS-rank
- 6,661
- Customer-cone ASNs
- 3
- Facilities
- 36
- Internet exchanges
- 2
- Customer degree
- 2
- Peer degree
- 54
- Provider degree
- 7
- 66.7.148.0/24
- 66.7.149.0/24
- 80.91.87.0/24
- 103.52.180.0/24
- 103.52.182.0/24
- 103.52.183.0/24
- 103.66.104.0/24
- 103.66.105.0/24
- 103.66.106.0/24
- 103.66.107.0/24
- 103.69.40.0/24
- 103.78.244.0/24
- 103.78.246.0/24
- 103.228.154.0/24
- 103.251.95.0/24
- 140.228.17.0/24
- 150.129.242.0/24
- 150.242.142.0/24
- 150.242.143.0/24
- 175.158.64.0/24
- 175.158.66.0/24
- 175.158.70.0/24
- 175.158.71.0/24
- 175.158.95.0/24
- 180.188.228.0/24
Infrastructure presence
Internet exchanges (2 total)
Facilities (36 total)
- CtrlS Lucknow DC1
- CtrlS Patna DC1
- NIXI Indore
- NIXI Bhopal
- NIXI Panaji
- Ishan Technologies Baroda
- NIXI Raipur
- NIXI Coimbatore
- Ishan Technologies Nashik
- Ishan Technologies Nagpur
- Ishan Technologies Raipur
- Ishan Technologies Jabalpur
- Ishan Technologies Cuttack
- Ishan Technologies Surat
- Ishan Technologies Rajkot
- Ishan Technologies Ahmedabad
- SIFY COCHIN
- SIFY Chandigarh
- SIFY Visakhapatnam
- SIFY Trivandrum
- SIFY Ludhiana
- SIFY Ranchi
- Sify Bareilly
- TATA Communications Mumbai
- Web Werks Pune 1
Route origin authorizations
A sample of 10 of this network’s 26 ROAs.
- 202.162.234.0/24 · max length /24
- 202.162.235.0/24 · max length /24
- 202.162.236.0/24 · max length /24
- 202.162.237.0/24 · max length /24
- 202.162.238.0/24 · max length /24
- 202.162.239.0/24 · max length /24
- 202.162.240.0/24 · max length /24
- 202.162.241.0/24 · max length /24
- 202.162.242.0/24 · max length /24
- 202.162.243.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS33480.
Blast radius
- Announced IPv4 addresses
- 12,032
- Threat-listed addresses
- 4
- Threat density
- 0.0332 %
- Routed prefixes
- 47
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.
- COGENT-174 - Cogent Communications, LLC · AS174
- D102-PHL-1 - Data102 · AS17185
- HTIL-TTML-IN-AP - Tata Teleservices Maharashtra Ltd · AS17762
- IPTP - IPTP LTD · AS41095
- AS-ANEXIA - Anexia Cloud Solutions GmbH · AS42473
- TTSL-MEISISP - Tata Teleservices ISP AS · AS45820
- WEBWERKS-AS-IN - Web Werks India Pvt. Ltd. · AS132762
- webwerks--AS - Web Werks India Pvt. Ltd. · AS132969
MOAS / hijack watch
2 announced prefixes conflict with AS33480 — another network announces the same address space. A sample:
Reputation
14.4reputation score (NEUTRAL)
AS33480 (WEBWERKSAS1 - Web Werks, US) has a reputation score of 61.1 (NEUTRAL).
- Threat density
- 66.0/100
- Graph metrics
- 65.0/100
- Historical behaviour
- 75.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
- Web Werks
- RIR
- ARIN
- Registered
- Wed, 29 Dec 2004 19:17:56 GMT
- Abuse contact
- abuse@unisecure.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS33480 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.