Skip to content

Hostname

hornblower.fandom.com

Last fetched

hornblower.fandom.com resolves to 199.232.208.194, announced in 199.232.208.0/22 by FASTLY - Fastly, Inc. in CA. hornblower.fandom.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 · hornblower.fandom.comRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/hornblower.fandom.com

Resolution chain

IPv6 resolution

No AAAA record for hornblower.fandom.com is recorded in WhisperGraph.

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for hornblower.fandom.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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

  • ns-330.awsdns-41.com
  • ns-763.awsdns-31.net
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • ns-1584.awsdns-06.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 74.120.184.0/21
  • ip: 208.68.167.128/28
  • include: _spf.google.com
  • include: sparkpostmail.com
  • a: spf.mail-sendgrid.wikia.com
  • include: mail.zendesk.com
  • include: servers.mcsv.net
  • include: _spf1.mailgun.org
  • include: _spf2.mailgun.org
  • include: _spf.eu.mailgun.org

Threat-feed evidence

History

Related pages

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