Skip to content

Hostname

lfcarry.com

Last fetched

lfcarry.com resolves to 104.26.6.41, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. lfcarry.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 · lfcarry.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/lfcarry.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
digital companion services pte.
Contact emails
anton.nachatoy@legionfarm.com, 312d48336a38443193133ca1e52e4ff6.protect@withheldforprivacy.com, lfcarry.com@whoisproxy.ru

Subdomains

Subdomain
api.lfcarry.com
auth.lfcarry.com
auth2.lfcarry.com
axie.lfcarry.com
blog.lfcarry.com
chat.lfcarry.com
docs.lfcarry.com
email.lfcarry.com
fm.lfcarry.com
img.lfcarry.com
job.lfcarry.com
mailing.lfcarry.com

Showing 12 of 21. 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

  • ben.ns.cloudflare.com
  • connie.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

SPF policy

  • include: _spf.getresponse.com
  • include: _spf.google.com
  • a: lfcarry.com
  • mx: lfcarry.com
  • include: spf.mandrillapp.com
  • include: trustpilotservice.com
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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