Hostname
kitchenking.de
Last fetched
kitchenking.de resolves to 168.119.14.37, announced in 168.119.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. kitchenking.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
- 168.119.14.37
168.119.0.0/16 · HETZNER-AS - Hetzner Online GmbH · Falkenstein, DE
IPv6 resolution
Attribution
hetzner
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for kitchenking.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
| Subdomain |
|---|
| mail.kitchenking.de |
| mx.kitchenking.de |
| post.kitchenking.de |
| shop.kitchenking.de |
| www.kitchenking.de |
Showing 5 of 5 subdomains (5 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- robotns3.second-ns.com
- ns1.first-ns.de
- robotns2.second-ns.de
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mx.kitchenking.de
- dedivirt4000.your-server.de
SPF policy
- include: spf.protection.outlook.com
- a: kitchenking.de
- mx: kitchenking.de
- a: mx.netzbest.de
- include: spf.server-he.de
- a: wp12078737.server-he.de
- a: dedivirt4000.your-server.de
- ip: 168.119.14.48
- ip: 2a01:488:42:1000:523:eb3d:0:0
- ip: 2a01:488:42:1000:523:eb3d:ff65:8fc6
Threat-feed evidence
History
Related pages
Pivot from kitchenking.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: "kitchenking.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.