Skip to content

Hostname

zieglergroup.com

Last fetched

zieglergroup.com resolves to 13.227.192.109, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. zieglergroup.com 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 · zieglergroup.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/zieglergroup.com

Resolution chain

IPv6 resolution

No AAAA record for zieglergroup.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
webdomain@dornach-intl.com, noreply@data-protected.net, 214dd983-28a0-47c2-a860-5ba48445b3df@identity-protect.org, 241865c6-80e4-4bd5-962b-b4a59820dcd4@identity-protect.org, 2f1259d2-842a-4d39-8d8c-1c8ef75c46cd@identity-protect.org, 3059c366-865c-4e71-a18a-2c6d96527da7@identity-protect.org, 3d993907-98a1-480c-8c14-d23e2c2a92fc@identity-protect.org, 64b20ca0-9d3f-47fa-8f7f-528d5a5580a5@identity-protect.org, 7c8d6c8f-6258-4dfa-8069-3cf9454c7d4a@identity-protect.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-369.awsdns-46.com
  • ns-1014.awsdns-62.net
  • ns-1456.awsdns-54.org
  • ns-1776.awsdns-30.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 128.59.0.0/16
  • ip: 1.1.1.0/24
  • ip: 81.246.46.1/26
  • include: _spf.google.com
  • a: zieglergroup.com
  • mx: zieglergroup.com
  • include: 19526545.spf01.hubspotemail.net
  • ip: 89.91.15.227

Threat-feed evidence

History

Related pages

Pivot from zieglergroup.com 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: "zieglergroup.com"})-[: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.