167.235.216.92

Threat posture

Threat feeds listing this

0

Verdict coverage

no-data

Nutrition Label

Attribution

Announced prefix

167.235.0.0/16

Announcing network

HETZNER-AS - Hetzner Online GmbH

RIR-registered prefix

167.235.0.0/16

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

• ahnefeld.smartdis.de
• airbus.smartdis.de
• arnholdt.smartdis.de
• bertram.smartdis.de
• demo.smartdis.de
• dev.smartdis.de
• fermont.smartdis.de
• geuer.smartdis.de
• hirsch.smartdis.de
• hirsch-demo.smartdis.de
• hirsch-test.smartdis.de
• inwork.smartdis.de
• jakob-burkhart.smartdis.de
• jakobburkhart.smartdis.de
• jnt.smartdis.de
• kruegel.smartdis.de
• lauer.smartdis.de
• load.smartdis.de
• master.smartdis.de
• neometrik.smartdis.de
• neometrik-api.smartdis.de
• neometrik2.smartdis.de
• neometrik3.smartdis.de
• neumoe.smartdis.de
• osm.smartdis.de
• a.osm.smartdis.de
• b.osm.smartdis.de
• c.osm.smartdis.de
• d.osm.smartdis.de
• wildcard.osm.smartdis.de
• osrm.smartdis.de
• wildcard.osrm.smartdis.de
• paulus.smartdis.de
• reiss.smartdis.de
• relogg-partner-test1.smartdis.de
• relogg-partner-test2.smartdis.de
• relogg-test.smartdis.de
• roggendorf.smartdis.de
• rossbach.smartdis.de
• sander.smartdis.de
• sander-test.smartdis.de
• scholz.smartdis.de
• slave-1.smartdis.de
• socket.smartdis.de
• starke.smartdis.de
• test.smartdis.de
• test-dash.smartdis.de
• test2.smartdis.de
• test3.smartdis.de
• www.smartdis.de

Geographic detail

City

Falkenstein, DE

Country

DE

Threat-feed evidence

History

Related pages

Pivot from 167.235.216.92 into the prefix, network and country that carry it.

• Whisper Internet Directory · Home
• TLD · .com
• Live MOAS conflicts
• Prefix · 167.235.0.0/16
• Network · HETZNER-AS - Hetzner Online GmbH
• Country · DE
• Hostname · ahnefeld.smartdis.de
• Glossary · What is anycast?

Cypher and MCP

Reproduce this address's routing attribution against graph.whisper.security:

MATCH (ip:IPV4 {name: "167.235.216.92"})
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 country

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