Skip to content
Install MCP

Autonomous System

AS41881

Last fetched

AS41881 is operated by Fanava-AS - Fanava Group, registered in IR, and announces 61 prefixes to 22 BGP neighbours. AS41881 has a reputation score of 16.2 (NEUTRAL); 6 of its 18,688 announced IPv4 addresses appear on threat feeds.

Nutrition Label

WHISPER CANON · AS41881Routing diversity8.9/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/41881

Routing footprint

Announced prefixes
61
BGP neighbours
22
RPKI ROAs
157
MOAS conflicts
0
CAIDA AS-rank
6,425
Customer-cone ASNs
3
Facilities
0
Internet exchanges
0
Customer degree
2
Peer degree
17
Provider degree
3

Routing posture

Hijack posture score
0.17
Route leaks
16

Leak types observed: TYPE4_PEER_TO_PROVIDER.

Route origin authorizations

A sample of 10 of this network’s 157 ROAs.

Upstreams

The networks that most often share an observed BGP path with AS41881.

Blast radius

Announced IPv4 addresses
18,688
Threat-listed addresses
6
Threat density
0.0321 %
Routed prefixes
59

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 22 of this network’s 22 BGP neighbours.

Reputation

16.2reputation score (NEUTRAL)

AS41881 (Fanava-AS - Fanava Group, IR) has a reputation score of 57.6 (NEUTRAL).

Threat density
38.1/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

Registered to
Fanava Group
RIR
RIPE
Registered
Wed, 08 Nov 2006 08:23:46 GMT
Abuse contact
abuse@fanava.net

This is the abuse contact WhisperGraph holds for the network.

Threat-feed evidence

Related pages

Pivot from AS41881 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, ixpCount
Run 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, observations
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.