Skip to content

Hostname

f168.ing

Last fetched

f168.ing resolves to 104.21.53.250, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. f168.ing is listed by 2 threat feeds; reconciled level CRITICAL.

Threat posture

60threat score (procedure-native scale)

CRITICAL

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Command-and-control

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:44:47 GMT
Last seen on a feed
Tue, 15 Sep 2026 00:18:36 GMT

Nutrition Label

WHISPER CANON · f168.ingRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/f168.ing

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
97d75076987b4e1a8c056e1e0781248d.protect@withheldforprivacy.com

Subdomains

Subdomain
www.f168.ing

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

Sample outbound links

Mail and authentication

Nameservers

  • aaron.ns.cloudflare.com
  • felicity.ns.cloudflare.com
  • ignat.ns.cloudflare.com
  • maleah.ns.cloudflare.com
  • michelle.ns.cloudflare.com
  • ziggy.ns.cloudflare.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

Threat-feed evidence

History

Related pages

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