IPv4 address
213.160.76.2
Last fetched
213.160.76.2 is announced in 213.160.64.0/19 by ROUTING - Hosting.de GmbH and geolocates to DE. 213.160.76.2 is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- no-data
Nutrition Label
Attribution
- Announced prefix
- 213.160.64.0/19
- Announcing network
- ROUTING - Hosting.de GmbH
- RIR-registered prefix
- 213.160.64.0/19
- RPKI
- valid
Anycast detection
This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.
Reverse DNS
- corvette65.berlin
- corvetteclub.berlin
- unger-partner.berlin
- charident.com
- charimed.com
- denx-europe.com
- www.denx-europe.com
- intelligdent.com
- navigdent.com
- nicunited.com
- www.nicunited.com
- petrajambon.com
- robo-c.com
- surgiguide.com
- www.surgiguide.com
- surgiscope.com
- tectodart.com
- backup-planet.de
- www.backup-planet.de
- backupplanet.de
- www.backupplanet.de
- bollmann-kg.de
- www.bollmann-kg.de
- entfernungsrechner.de
- www.entfernungsrechner.de
- ersatzwagen-bei-unfall.de
- www.ersatzwagen-bei-unfall.de
- upgrade.festival-open-systems.de
- gblf.de
- web25467.ihrserver.de
- intelligdent.de
- www.intelligdent.de
- kp7.de
- www.kp7.de
- kr7.de
- www.kr7.de
- krankenversicherungsantraege.de
- www.krankenversicherungsantraege.de
- krankenversicherungsantrag.de
- www.krankenversicherungsantrag.de
- krankenversicherungsvertrag.de
- www.krankenversicherungsvertrag.de
- lebensversicherungsvertrag.de
- www.lebensversicherungsvertrag.de
- lorbach-bam.de
- www.lorbach-bam.de
- navigdent.de
- www.navigdent.de
- petrajambon.de
- www.petrajambon.de
Geographic detail
- City
- Aachen, DE
- Country
- DE
- Dominant city of the prefix
- Aachen, DE
Threat-feed evidence
History
Related pages
Pivot from 213.160.76.2 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "213.160.76.2"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.