Skip to content

Hostname

hiyaparty.com

Last fetched

hiyaparty.com resolves to 8.219.144.218, announced in 8.219.128.0/17 by ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. in SG. hiyaparty.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 · hiyaparty.comRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/hiyaparty.com

Resolution chain

IPv6 resolution

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

Attribution

hangzhou alibaba advertising

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of hiyaparty.com owner
Contact emails
0bd3de83-f62a-4d00-93f5-367b762989df@identity-protect.org, 1d200150-698b-43b7-b5ec-d24cffd4be80@identity-protect.org, 337c2f46-1102-4431-8102-e4c82c7001fd@identity-protect.org, 33912a62-b5f5-4de9-97d2-1f1b5572bcb5@identity-protect.org, 9296a52e-bf4b-42cb-afc7-b83ea2bcd860@identity-protect.org, 98f517ab-9254-492d-aae0-1ca1451119e3@identity-protect.org, b8c93b39-f476-441f-9700-0eb1c240fe17@identity-protect.org

Subdomains

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-70.awsdns-08.com
  • ns-535.awsdns-02.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-1025.awsdns-00.org
  • ns-1583.awsdns-05.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

SPF policy

  • include: amazonses.com
  • include: spf.mxhichina.com

Threat-feed evidence

History

Related pages

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