Skip to content

Hostname

footyfactor.com

Last fetched

footyfactor.com resolves to 178.79.161.89, announced in 178.79.128.0/18 by AKAMAI-LINODE-AP - Akamai Connected Cloud in GB. footyfactor.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 · footyfactor.comRouting diversity1.5/10Peering density6.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/footyfactor.com

Resolution chain

IPv6 resolution

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

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
pk9fr5eb3ha@networksolutionsprivateregistration.com, s46q47s343v@networksolutionsprivateregistration.com, xk7a94uf9k6@networksolutionsprivateregistration.com

Subdomains

Subdomain
www.footyfactor.com

Showing 1 of 1 subdomain (1 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

Mail and authentication

Nameservers

  • ns79.worldnic.com
  • ns80.worldnic.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

  • mx001.netsol.xion.oxcs.net
  • mx002.netsol.xion.oxcs.net

SPF policy

  • include: spf.registeredsite.com
  • include: spf.cloudus.oxcs.net

Threat-feed evidence

History

Related pages

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