Skip to content

Hostname

enzian.org

Last fetched

enzian.org resolves to 44.199.46.0, announced in 44.192.0.0/11 by AMAZON-AES - Amazon.com, Inc. in US. enzian.org 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 · enzian.orgRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/enzian.org

Resolution chain

IPv6 resolution

No AAAA record for enzian.org is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
christy west
Contact emails
cwest@enzian.org

Subdomains

Subdomain
autodiscover.enzian.org
demo.enzian.org
dev.enzian.org
elma.enzian.org
email.enzian.org
ftp.enzian.org
purchase.enzian.org
ticketing.enzian.org
transfer.enzian.org
www.enzian.org

Showing 10 of 10 subdomains (10 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-280.awsdns-35.com
  • ns-853.awsdns-42.net
  • 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
  • ns-1454.awsdns-53.org
  • ns-2034.awsdns-62.co.uk

MX records

  • enzian-org.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com

Threat-feed evidence

History

Related pages

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