Skip to content

Hostname

freedombeacon.com

Last fetched

freedombeacon.com resolves to 104.21.92.223, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. freedombeacon.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 · freedombeacon.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/freedombeacon.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
j. taylor
Contact emails
admin@freedombeacon.com, contact@freedombeacon.com, domains@hugedomains.com, 12ba8308f0ea4f968a7d972325dd4c37.protect@withheldforprivacy.com, 43f2ed4555654c319f8d297df03b693f.protect@withheldforprivacy.com, ad3fb95278c34d40970f71f25a04bbf6.protect@withheldforprivacy.com, d99f298b7d1b4bf79dc2760ac0b51ed7.protect@withheldforprivacy.com

Subdomains

Subdomain
delivery.freedombeacon.com
mail.freedombeacon.com
rcms.freedombeacon.com
rs-stripe.freedombeacon.com
track.freedombeacon.com
www.freedombeacon.com

Showing 6 of 7. 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

  • alexia.ns.cloudflare.com
  • angelina.ns.cloudflare.com
  • jerome.ns.cloudflare.com
  • kellen.ns.cloudflare.com

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

  • ip: 216.24.224.0/20
  • mx: freedombeacon.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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