Skip to content

Hostname

zeenea.com

Last fetched

zeenea.com resolves to 193.160.66.255, announced in 193.160.66.0/23 by AS-HOSTINGER - Hostinger International Limited in NL. zeenea.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 · zeenea.comRouting diversity1.5/10Peering density6.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/zeenea.com

Resolution chain

IPv6 resolution

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

Attribution

hostinger international

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
luc legardeur
Contact emails
1a8d6e016d1659c824a4c928cd0fa5f1-2185664@contact.gandi.net, 2652d2307a44d8a191141189af2dca9d-6071546@contact.gandi.net, a0316b77bedc6e011448628eb1b504cd-6071546@contact.gandi.net

Subdomains

Subdomain
beta.zeenea.com
demo.zeenea.com
docs.zeenea.com
info.zeenea.com
podcast.zeenea.com
releases.zeenea.com
support.zeenea.com
trail.zeenea.com
www.zeenea.com

Showing 9 of 9 subdomains (9 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-161-c.gandi.net
  • ns-175-b.gandi.net
  • ns-180-a.gandi.net
  • ns1.gandi.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: mail.zendesk.com
  • include: 3342447.spf08.hubspotemail.net

Threat-feed evidence

History

Related pages

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