IPv4 address
167.172.106.197
Last fetched
167.172.106.197 is announced in 167.172.96.0/20 by DIGITALOCEAN-ASN - DigitalOcean, LLC and geolocates to DE. 167.172.106.197 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
- 167.172.96.0/20
- Announcing network
- DIGITALOCEAN-ASN - DigitalOcean, LLC
- RIR-registered prefix
- 167.172.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
- kliniken-fmt.com
- cpanel.kliniken-fmt.com
- cpcalendars.kliniken-fmt.com
- cpcontacts.kliniken-fmt.com
- mail.kliniken-fmt.com
- webmail.kliniken-fmt.com
- www.kliniken-fmt.com
- varisano.com
- mail.varisano.com
- kliniken-fmt.de
- www.kliniken-fmt.de
- kliniken-mtk.de
- karriere.kliniken-mtk.de
- www.karriere.kliniken-mtk.de
- www.kliniken-mtk.de
- klinikumfrankfurt.de
- www.klinikumfrankfurt.de
- klinikumfrankfurt-karriere.de
- www.klinikumfrankfurt-karriere.de
- krankenhaus-badsoden.de
- www.krankenhaus-badsoden.de
- krankenhaus-hofheim.de
- www.krankenhaus-hofheim.de
- main-taunus-privatklinik.de
- www.main-taunus-privatklinik.de
- kliniken-fmt.sb2a.de
- next.kliniken-fmt.sb2a.de
- previous.kliniken-fmt.sb2a.de
- www.kliniken-fmt.sb2a.de
- kliniken-fmt-testing.sb2a.de
- next.kliniken-fmt-testing.sb2a.de
- previous.kliniken-fmt-testing.sb2a.de
- www.kliniken-fmt-testing.sb2a.de
- varisano.de
- www.varisano.de
- kliniken-fmt.net
- www.kliniken-fmt.net
- kliniken-fmt.org
- varisano.org
- mail.varisano.org
Geographic detail
- City
- Frankfurt am Main, DE
- Country
- DE
Threat-feed evidence
History
Related pages
Pivot from 167.172.106.197 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: "167.172.106.197"})
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.