Skip to content

Hostname

datenzuhause.at

Last fetched

datenzuhause.at resolves to 193.109.230.114, announced in 193.109.230.0/24 by DATENZUHAUSE - Datenzuhause GmbH in AT. datenzuhause.at is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · datenzuhause.atRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/datenzuhause.at

Resolution chain

IPv6 resolution

No AAAA record for datenzuhause.at is recorded in WhisperGraph.

Attribution

datenzuhause

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for datenzuhause.at. 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
admin.datenzuhause.at
aushaenge.datenzuhause.at
bastel.datenzuhause.at
chat.datenzuhause.at
chat1.datenzuhause.at
dateien.datenzuhause.at
daten.datenzuhause.at
dns1.datenzuhause.at
dns2.datenzuhause.at
dns3.datenzuhause.at
dns4.datenzuhause.at
dokumente.datenzuhause.at

Showing 12 of 37. View all subdomains →

Mail and authentication

Nameservers

  • dns1.datenzuhause.at
  • dns2.datenzuhause.at
  • dns3.datenzuhause.at
  • dns4.datenzuhause.at
  • 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.datenzuhause.at

SPF policy

  • a: datenzuhause.at
  • mx: datenzuhause.at

Threat-feed evidence

History

Related pages

Pivot from datenzuhause.at 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: "datenzuhause.at"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.