Skip to content

Hostname

megaphonetv.com

Last fetched

megaphonetv.com resolves to 34.174.185.168, announced in 34.176.64.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. megaphonetv.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 · megaphonetv.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/megaphonetv.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of megaphonetv.com owner
Contact emails
megaphonetv.com@proxy.dreamhost.com, 2dd4e850-2460-425a-92ac-d57e219479d8@identity-protect.org, ab7e1d51-04a3-41f8-936b-bf95ce6b32bc@identity-protect.org, f5d6aa8a-a39f-4fa1-aa68-acb6c191d752@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-310.awsdns-38.com
  • ns-892.awsdns-47.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-1222.awsdns-24.org
  • ns-1871.awsdns-41.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

  • include: cmail1.com
  • include: createsend.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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