Skip to content

Hostname

fantasyfi.io

Last fetched

fantasyfi.io resolves to 3.144.0.1, announced in 3.144.0.0/13 by AMAZON-02 - Amazon.com, Inc. in US. fantasyfi.io 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 · fantasyfi.ioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/fantasyfi.io

Resolution chain

IPv6 resolution

No AAAA record for fantasyfi.io is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf

Subdomains

Subdomain
betadev-origin.fantasyfi.io
betadev.fantasyfi.io
dev-gitlab.fantasyfi.io
dev.fantasyfi.io
go.fantasyfi.io
payment.fantasyfi.io
play.fantasyfi.io
stg.fantasyfi.io
www.fantasyfi.io

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

  • ns-293.awsdns-36.com
  • ns-977.awsdns-58.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-1260.awsdns-29.org
  • ns-1977.awsdns-55.co.uk

MX records

  • mx1-hosting.jellyfish.systems
  • mx2-hosting.jellyfish.systems
  • mx3-hosting.jellyfish.systems

SPF policy

  • include: spf.privateemail.com
  • include: spf.web-hosting.com
  • include: zcsend.net
  • ip: 192.64.117.155

Threat-feed evidence

History

Related pages

Pivot from fantasyfi.io 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: "fantasyfi.io"})-[: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.