IPv4 address
31.13.172.22
Last fetched
31.13.172.22 is announced in 31.13.172.0/23 by TWK-KL-AS - DEMANDO GmbH and geolocates to DE. 31.13.172.22 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
- 31.13.172.0/23
- Announcing network
- TWK-KL-AS - DEMANDO GmbH
- RIR-registered prefix
- 31.13.168.0/21
- 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
- saarland.app
- mail.saarland.app
- rieckhof.biz
- kontakt.rieckhof.biz
- mail.rieckhof.biz
- www.rieckhof.biz
- intelly.cloud
- mail.intelly.cloud
- saar.cloud
- dukenet.saar.cloud
- test.saar.cloud
- www.saar.cloud
- saarland.cloud
- 220-ms-mail-01.saarland.cloud
- 220-ms-mail-03.saarland.cloud
- 220-ms-mail-04.saarland.cloud
- he-cp-01.saarland.cloud
- he-ex-03.saarland.cloud
- hydra6.saarland.cloud
- ikarus-srv9.saarland.cloud
- ms-mail-01.saarland.cloud
- wildcard.saarland.cloud
- www.saarland.cloud
- hydra6.intellycloud.de
- devback01.hydra6.intellycloud.de
- devweb01.hydra6.intellycloud.de
- naheinander.de
- shs.gmbh
- brainpan.net
- mail.brainpan.net
- www.brainpan.net
- fireandflame.net
- mail.fireandflame.net
- www.fireandflame.net
- rieckhof.net
- mail.rieckhof.net
- www.rieckhof.net
- agfeo.saarland
- mail.agfeo.saarland
- auerswald.saarland
- mail.auerswald.saarland
- mail.deutschetelefon.saarland
- sophos.saarland
- mail.sophos.saarland
- 3cx-deb.systemhaus.saarland
- appdeploy.systemhaus.saarland
- distribution.systemhaus.saarland
- dl.systemhaus.saarland
- hilfe.systemhaus.saarland
- jira.systemhaus.saarland
Geographic detail
- Country
- DE
Threat-feed evidence
History
Related pages
Pivot from 31.13.172.22 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: "31.13.172.22"})
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.