Skip to content

Hostname

hitentertainment.com

Last fetched

hitentertainment.com resolves to 15.197.167.90, announced in 15.197.160.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. hitentertainment.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 · hitentertainment.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/hitentertainment.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
domain administrator
Contact emails
nshanks@hitentertainment.com, proxyadm@mattel.com

Subdomains

Subdomain
apps.hitentertainment.com
autodiscover.hitentertainment.com
events.hitentertainment.com
lonmail.hitentertainment.com
metrics.hitentertainment.com
parents.hitentertainment.com
registrations.hitentertainment.com
webmail.hitentertainment.com
www.hitentertainment.com

Showing 9 of 10. 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

  • ns1.markmonitor.com
  • ns2.markmonitor.com
  • ns3.markmonitor.com
  • ns4.markmonitor.com
  • ns5.markmonitor.com
  • ns6.markmonitor.com
  • ns7.markmonitor.com

MX records

  • hitentertainment-com.mail.protection.outlook.com

SPF policy

  • include: mattel.com
  • ip: 156.20.30.143
  • ip: 195.108.1.26
  • ip: 199.89.199.212
  • ip: 199.89.199.76
  • ip: 199.89.199.85
  • ip: 202.64.121.134
  • ip: 209.34.72.104
  • ip: 63.100.125.35

Threat-feed evidence

History

Related pages

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