Hostname
klingel.de
Last fetched
klingel.de resolves to 34.144.248.61, announced in 34.144.128.0/17 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. klingel.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
- 34.144.248.61
34.144.128.0/17 · GOOGLE-CLOUD-PLATFORM - Google LLC · Kansas City, US
IPv6 resolution
No AAAA record for klingel.de is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for klingel.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
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
- dns009.arvato-systems.de
- dns017.arvato-systems.de
- ns1.arvato-systems.de
- ns2.arvato-systems.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
- mail.bader.de
- mail2.bader.de
- mail3.bader.de
SPF policy
- ip: 185.228.148.132/32
- include: emsmtp.com
- include: spf.protection.outlook.com
- include: mail.zendesk.com
- a: mail.bader.de
- a: mail2.bader.de
- mx: klingel.de
- include: spf.servicemail24.de
- a: production.eu01.bader.demandware.net
- include: emarsys.net
- ip: 194.120.109.80
- ip: 194.42.108.104
- ip: 194.42.108.105
- ip: 194.42.108.109
- ip: 194.42.108.11
- ip: 194.42.108.110
- ip: 194.42.108.6
Threat-feed evidence
History
Related pages
Pivot from klingel.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: "klingel.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.