IPv4 address
212.91.232.53
Last fetched
212.91.232.53 is announced in 212.91.224.0/19 by DNSNET - DNS:NET Internet Service GmbH and geolocates to DE. 212.91.232.53 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
- 212.91.224.0/19
- Announcing network
- DNSNET - DNS:NET Internet Service GmbH
- RIR-registered prefix
- 212.91.224.0/19
- RPKI
- not-found
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
- arno-esch-stiftung.universum.com
- www.arno-esch-stiftung.universum.com
- old.fnst.universum.com
- rms.universum.com
- arno-esch-stiftung.de
- www.arno-esch-stiftung.de
- www.karl-hamann-stiftung.de
- xn--nrnberger-sicherheitstagung-i3c.de
- www.xn--nrnberger-sicherheitstagung-i3c.de
- fnst.org
- africa.fnst.org
- www.africa.fnst.org
- amman.fnst.org
- argentina.fnst.org
- www.argentina.fnst.org
- asia.fnst.org
- beirut.fnst.org
- bosnia-herzegovina.fnst.org
- brasil.fnst.org
- esee.fnst.org
- www.esee.fnst.org
- fnfsc.fnst.org
- fnfvietnam.fnst.org
- freedomis.fnst.org
- garage664.fnst.org
- humansoffreedom.fnst.org
- iaf.fnst.org
- indonesia.fnst.org
- innovationhub.fnst.org
- jerusalem.fnst.org
- korea.fnst.org
- kosovo.fnst.org
- la.fnst.org
- www.la.fnst.org
- lebanon.fnst.org
- malaysia.fnst.org
- mena.fnst.org
- msoe.fnst.org
- www.msoe.fnst.org
- myanmar.fnst.org
- www.myanmar.fnst.org
- myanmar-en.fnst.org
- paisesandinos.fnst.org
- pakistan.fnst.org
- philippines.fnst.org
- russia.fnst.org
- www.russia.fnst.org
- serbia.fnst.org
- sooe.fnst.org
- southasia.fnst.org
Geographic detail
- City
- Berlin, DE
- Country
- DE
Threat-feed evidence
History
Related pages
Pivot from 212.91.232.53 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: "212.91.232.53"})
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.