Skip to content

Hostname

labuanferry.com

Last fetched

labuanferry.com resolves to 139.162.7.203, announced in 139.162.0.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in SG. labuanferry.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed
Mon, 14 Sep 2026 23:25:39 GMT

Nutrition Label

WHISPER CANON · labuanferry.comRouting diversity1.5/10Peering density6.3/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/labuanferry.com

Resolution chain

IPv6 resolution

No AAAA record for labuanferry.com is recorded in WhisperGraph.

Attribution

akamai

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:460
Registrant organisation
big domain sdn bhd
Contact emails
unghock@gmail.com, z855p42q3cx@networksolutionsprivateregistration.com, mook@the.net.my

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns101.bigdomaincloud.com
  • ns102.bigdomaincloud.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

  • labuanferry.com

SPF policy

  • include: bigdomaincloud.com
  • include: spf.bigdomaincloud.com
  • a: labuanferry.com
  • mx: labuanferry.com
  • ip: 139.162.7.203

Threat-feed evidence

History

Related pages

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