Skip to content

Hostname

fyi.net

Last fetched

fyi.net is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. fyi.net 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 · fyi.netRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/fyi.net

Resolution chain

No IPv4 resolution is recorded for fyi.net in WhisperGraph.

IPv6 resolution

No AAAA record for fyi.net is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:2
Registrant organisation
fyi networks
Contact emails
nb6n699c6pm@networksolutionsprivateregistration.com, rr9q382f9mn@networksolutionsprivateregistration.com, sx2n295p7xy@networksolutionsprivateregistration.com, vs6pq3xt52h@networksolutionsprivateregistration.com, jtv@fyi.net, noc@fyi.net

Subdomains

Subdomain
mail.fyi.net
ns1.fyi.net
ns3.fyi.net
webmail.fyi.net

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

Mail and authentication

Nameservers

  • ns1.carrierzone.com
  • ns2.carrierzone.com
  • ns3.carrierzone.com
  • ns4.carrierzone.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

  • mx1c25.carrierzone.com
  • mx2c25.carrierzone.com
  • mx3c25.carrierzone.com
  • mx4c25.carrierzone.com

SPF policy

  • include: spfc25.carrierzone.com

Threat-feed evidence

History

Related pages

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