Skip to content

Hostname

land-fx.com

Last fetched

land-fx.com resolves to 18.164.144.125, announced in 18.164.144.0/22 by AMAZON-02 - Amazon.com, Inc. in IN. land-fx.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 · land-fx.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/land-fx.com

Resolution chain

IPv6 resolution

No AAAA record for land-fx.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
land-fx.com@domainsbyproxy.com, ioanna@land-fx.com, seungwoo@land-fx.com

Subdomains

Subdomain
ct.land-fx.com
ib.land-fx.com
mypage.land-fx.com
pamm.land-fx.com
www.land-fx.com

Showing 5 of 5 subdomains (5 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-32.awsdns-04.com
  • ns-765.awsdns-31.net
  • ns-1458.awsdns-54.org
  • ns-1700.awsdns-20.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: aspmx.l.google.com
  • include: alt1.aspmx.l.google.com
  • include: alt2.aspmx.l.google.com
  • include: aspmx2.googlemail.com
  • include: aspmx3.googlemail.com
  • mx: land-fx.com
  • ip: 1.234.136.140
  • ip: 18.180.81.240
  • ip: 211.56.66.205
  • ip: 211.56.66.206
  • ip: 211.56.66.217
  • ip: 211.56.66.221
  • ip: 54.150.221.59

Threat-feed evidence

History

Related pages

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