Hostname
getbhkw.de
Last fetched
getbhkw.de resolves to 149.224.157.87, announced in 149.224.0.0/16 by WTNET-AS - wilhelm.tel GmbH in DE. getbhkw.de 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
- known-clean
Nutrition Label
Resolution chain
- 149.224.157.87
149.224.0.0/16 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
- 149.224.177.84
149.224.0.0/16 · WTNET-AS - wilhelm.tel GmbH · Quickborn, DE
- 149.224.226.54
149.224.0.0/16 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
- 149.233.147.224
- 176.109.221.208
176.109.192.0/19 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
- 216.83.213.142
216.83.208.0/20 · WTNET-AS - wilhelm.tel GmbH · Halstenbek, DE
- 216.83.216.206
216.83.208.0/20 · WTNET-AS - wilhelm.tel GmbH · Barsbüttel, DE
- 31.29.59.79
31.29.32.0/19 · WTNET-AS - wilhelm.tel GmbH · Hamburg, DE
- 46.59.139.191
46.59.128.0/17 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
- 46.59.220.33
46.59.128.0/17 · WTNET-AS - wilhelm.tel GmbH · Hamburg, DE
- 79.213.31.254
79.192.0.0/10 · DTAG - Deutsche Telekom AG · Kirchhain, DE
- 91.51.233.78
91.0.0.0/10 · DTAG - Deutsche Telekom AG · Bremen, DE
- 95.163.161.38
95.163.160.0/20 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
- 195.250.0.217
195.250.0.0/20 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
- 77.223.22.138
77.223.16.0/20 · WTNET-AS - wilhelm.tel GmbH · Norderstedt, DE
IPv6 resolution
No AAAA record for getbhkw.de is recorded in WhisperGraph.
Attribution
wilhelm tel
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for getbhkw.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Mail and authentication
Nameservers
- ns1.asok.de
- ns2.asok.de
- ns3.asok.de
Threat-feed evidence
History
Related pages
Pivot from getbhkw.de into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "getbhkw.de"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.