Skip to content

Hostname

icf.sr

Last fetched

icf.sr resolves to 64.91.240.56, announced in 64.91.224.0/19 by LIQUIDWEB - Liquid Web, L.L.C in US. icf.sr 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 · icf.srRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/icf.sr

Resolution chain

IPv6 resolution

No AAAA record for icf.sr is recorded in WhisperGraph.

Attribution

liquid

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for icf.sr. 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.

Subdomains

Subdomain
account.icf.sr
alert.icf.sr
cloud.icf.sr
mail.icf.sr
sr.icf.sr
support.icf.sr
www.icf.sr

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

  • ns200.cloudx-security.com
  • ns201.cloudx-security.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

  • icf.sr

SPF policy

  • a: icf.sr
  • mx: icf.sr
  • ip: 104.193.111.95
  • ip: 64.91.240.56

Threat-feed evidence

History

Related pages

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