Autonomous System
AS52896
Last fetched
AS52896 is operated by AS52896 - BDNET SOLUCOES TECNOLOGICAS LTDA ME, registered in BR, and announces 2 prefixes to 1 BGP neighbour. AS52896 has a reputation score of 19.1 (NEUTRAL).
Nutrition Label
Routing footprint
- Announced prefixes
- 2
- BGP neighbours
- 1
- RPKI ROAs
- 2
- MOAS conflicts
- 0
- Facilities
- 16
- Internet exchanges
- 1
Infrastructure presence
Internet exchanges (1 total)
Facilities (16 total)
- Cirion Rio de Janeiro - RIO1
- Equinix RJ1 - Rio de Janeiro
- LNCC
- Equinix RJ2 - Rio de Janeiro
- Teleporto Rio de Janeiro
- Linkfull Rio de Janeiro
- BR.Digital Rio de Janeiro (RJO1)
- Datacenter UFINET BRASIL (Novo Teleporto)
- Durand Pix - Globenet RJ
- Elea RJO1 - Rio de Janeiro
- Mundivox do Brasil
- PIX Embratel RJ
- BR.Digital Rio de Janeiro (RJO3)
- Scala Data Centers SGIGSM01
- Equinix RJ3 - Rio de Janeiro
- Takoda RJ01
Route origin authorizations
A sample of 2 of this network’s 2 ROAs.
- 177.184.48.0/20 · max length /24
- 2804:a98::/32 · max length /34
Upstreams
The networks that most often share an observed BGP path with AS52896.
Blast radius
Blast radius is temporarily unavailable.
The threat-density procedure returned no result for this ASN. Refresh in a moment to retry — fresh data is fetched on the next visit.
Peering ecosystem
A sample of 1 of this network’s 1 BGP neighbours.
- AS268696 - Tuddo Telecom Ltda. · AS268696
Reputation
19.1reputation score (NEUTRAL)
AS52896 (AS52896 - BDNET SOLUCOES TECNOLOGICAS LTDA ME, BR) has a reputation score of 51.7 (NEUTRAL).
- Threat density
- 57.1/100
- Graph metrics
- 30.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
- BDNET SOLUCOES TECNOLOGICAS LTDA ME
- RIR
- LACNIC
- Registered
- Thu, 19 Jul 2012 11:56:08 GMT
Threat-feed evidence
Related pages
Pivot from AS52896 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.