Autonomous System
AS210558
Last fetched
AS210558 is operated by services-1337-gmbh - 1337 Services GmbH, registered in DE, and announces 33 prefixes to 9 BGP neighbours. AS210558 has a reputation score of 50.0 (HIGHLY_SUSPICIOUS); 554 of its 6,656 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 33
- BGP neighbours
- 9
- RPKI ROAs
- 34
- MOAS conflicts
- 0
- CAIDA AS-rank
- 19,728
- Customer-cone ASNs
- 1
- Facilities
- 30
- Internet exchanges
- 1
- Customer degree
- 0
- Peer degree
- 0
- Provider degree
- 9
- 2.58.56.0/24
- 13.143.247.0/24
- 45.80.158.0/24
- 45.83.28.0/24
- 45.83.31.0/24
- 45.88.186.0/24
- 45.92.1.0/24
- 45.94.31.0/24
- 45.138.16.0/24
- 45.141.215.0/24
- 45.152.149.0/24
- 45.154.98.0/24
- 84.54.33.0/24
- 91.206.169.0/24
- 124.198.131.0/24
- 124.198.132.0/24
- 147.90.182.0/24
- 147.90.219.0/24
- 158.173.51.0/24
- 185.19.40.0/24
- 185.241.208.0/24
- 185.241.211.0/24
- 192.159.99.0/24
- 193.26.115.0/24
- 194.26.192.0/24
Routing posture
- Hijack posture score
- 0.18
- Origin mismatches
- 1
Signals
- bulletproof-hostingHosts content other providers routinely take down.
Infrastructure presence
Internet exchanges (1 total)
Facilities (30 total)
- Digital Realty AMS17 - Amsterdam
- NIKHEF Amsterdam
- Digital Realty AMS9 - Amsterdam
- BIT-1
- Equinix EN1 - Enschede
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Equinix AM8 - Amsterdam, Gyroscoopweg
- InterDC Doetinchem
- BIT-2
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- Iron Mountain Data Center - Amsterdam (AMS-1)
- Digital Realty AMS18 - Amsterdam
- InterDC Enschede
- NorthC Amsterdam 1
- Previder PDC2
- Equinix AM3 - Amsterdam, Science Park
- Equinix AM11 - Amsterdam, Lemelerbergweg
- Equinix AM5 - Amsterdam, Schepenbergweg
- Interconnect Services DC2 Eindhoven
- Equinix AM6 - Amsterdam, Duivendrechtsekade
- NorthC Almere
- Equinix AM4 - Amsterdam, Science Park
- Greenhouse Datacenters DC2
- Greenhouse Datacenters DC1
Route origin authorizations
A sample of 10 of this network’s 34 ROAs.
- 124.198.131.0/24 · max length /24
- 124.198.132.0/24 · max length /24
- 147.90.182.0/24 · max length /24
- 147.90.214.0/24 · max length /24
- 147.90.219.0/24 · max length /24
- 158.173.51.0/24 · max length /24
- 185.19.40.0/24 · max length /24
- 185.241.208.0/24 · max length /24
- 185.241.211.0/24 · max length /24
- 192.159.99.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS210558.
Blast radius
- Announced IPv4 addresses
- 6,656
- Threat-listed addresses
- 554
- Threat density
- 8.3233 %
- Routed prefixes
- 26
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 9 of this network’s 9 BGP neighbours.
- PUSHPKT - PUSHPKT OU · AS3920
- IS-AS-1 - Interserver, Inc · AS19318
- AS-VULTR - The Constant Company, LLC · AS20473
- NOVOSERVE-AS - NovoServe B.V. · AS24875
- ERANIUM - Eranium B.V. · AS35133
- WLXLIMITED-AS-AP - WLX Limited · AS150670
- Mevspace - MEVSPACE sp. z o.o. · AS201814
- ZMC - ZMC MAR GRAPHIC DESIGN SRL-D · AS213323
- VIRTUO - 12651980 CANADA INC. · AS399486
Reputation
50.0reputation score (HIGHLY_SUSPICIOUS)
AS210558 (services-1337-gmbh - 1337 Services GmbH, DE) has a reputation score of 25.0 (HIGHLY_SUSPICIOUS). This ASN shows suspicious characteristics.
- Threat density
- 27.2/100
- Graph metrics
- 65.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
- 1337 Services GmbH
- RIR
- RIPE
- Registered
- Thu, 28 Oct 2021 13:16:15 GMT
- Abuse contact
- abuse@as210558.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS210558 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.