Skip to content

Autonomous System

AS3214

Last fetched

AS3214 is operated by XTOM - xTom GmbH, registered in DE, and announces 167 prefixes to 117 BGP neighbours. AS3214 has a reputation score of 16.0 (NEUTRAL); 57 of its 26,112 announced IPv4 addresses appear on threat feeds.

Nutrition Label

WHISPER CANON · AS3214Routing diversity10.0/10Peering density8.3/10MOAS conflict⚠ 3 conflictsThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/3214

Routing footprint

Announced prefixes
167
BGP neighbours
117
RPKI ROAs
506
MOAS conflicts
3
CAIDA AS-rank
506
Customer-cone ASNs
92
Facilities
92
Internet exchanges
10
Customer degree
13
Peer degree
689
Provider degree
11

Routing posture

Hijack posture score
0.11
Route leaks
6

Leak types observed: TYPE2_LATERAL_PEER_TO_PEER, TYPE4_PEER_TO_PROVIDER.

Infrastructure presence

Route origin authorizations

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

Upstreams

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

Blast radius

Announced IPv4 addresses
26,112
Threat-listed addresses
57
Threat density
0.2183 %
Routed prefixes
102

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

MOAS / hijack watch

3 announced prefixes conflict with AS3214 — another network announces the same address space. A sample:

Reputation

16.0reputation score (NEUTRAL)

AS3214 (XTOM - xTom GmbH, DE) has a reputation score of 58.0 (NEUTRAL).

Threat density
49.9/100
Graph metrics
90.0/100
Historical behaviour
60.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
xTom GmbH
RIR
RIPE
Registered
Mon, 16 Nov 2015 13:48:20 GMT
Abuse contact
abuse@xtom.com

This is the abuse contact WhisperGraph holds for the network.

Threat-feed evidence

Related pages

Pivot from AS3214 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.