Skip to content

Hostname

zooundco.de

Last fetched

zooundco.de resolves to 213.239.219.156, announced in 213.239.192.0/18 by HETZNER-AS - Hetzner Online GmbH in DE. zooundco.de 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 · zooundco.deRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/zooundco.de

Resolution chain

IPv6 resolution

No AAAA record for zooundco.de is recorded in WhisperGraph.

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for zooundco.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
franchise.zooundco.de
mail.zooundco.de
markt.zooundco.de
news.zooundco.de
partner.zooundco.de
service.zooundco.de
shop.zooundco.de
test.zooundco.de
upgrade-partner.zooundco.de
upgrade.zooundco.de
www.zooundco.de

Showing 11 of 12. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • isla.ns.cloudflare.com
  • sterling.ns.cloudflare.com
  • ns.second-ns.com
  • ns3.second-ns.de
  • ns1.your-server.de

MX records

  • mail.zooundco.de

SPF policy

  • ip: 195.243.59.96/28
  • include: spf.protection.outlook.com
  • a: zooundco.de
  • mx: zooundco.de
  • ip: 136.243.65.225
  • ip: 148.251.195.162
  • ip: 148.251.195.164
  • ip: 178.250.15.176
  • ip: 178.63.74.141
  • ip: 213.239.219.156

Threat-feed evidence

History

Related pages

Pivot from zooundco.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: "zooundco.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 20

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