Skip to content

Hostname

broadcastintel.com

Last fetched

broadcastintel.com resolves to 51.140.146.128, announced in 51.140.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in GB. broadcastintel.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 · broadcastintel.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/broadcastintel.com

Resolution chain

IPv6 resolution

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

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
media business insight
Contact emails
product.development@mbi.london

Subdomains

Subdomain
account.broadcastintel.com
auth.broadcastintel.com
subscribe.broadcastintel.com
www.broadcastintel.com

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

  • ns43.domaincontrol.com
  • ns44.domaincontrol.com
  • 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

MX records

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 52.210.120.91/32
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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