Skip to content

Hostname

ezycargo.com

Last fetched

ezycargo.com resolves to 202.82.42.158, announced in 202.82.42.0/24 by PCCW-AS-AP - PCCW IMS Ltd (PCCW Business Internet Access) in HK. ezycargo.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 · ezycargo.comRouting diversity1.5/10Peering density7.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ezycargo.com

Resolution chain

IPv6 resolution

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

Attribution

pccw ims business access

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
global logistics system (hk) co
Contact emails
alfred@traxonasia.com, kv59q4r34dm@networksolutionsprivateregistration.com, keith.lam@glshk.com

Subdomains

Subdomain
adminimport.ezycargo.com
ez3.ezycargo.com
import.ezycargo.com
www.ezycargo.com

Showing 4 of 4 subdomains (4 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-299.awsdns-37.com
  • ns-541.awsdns-03.net
  • ns-1415.awsdns-48.org
  • ns-1700.awsdns-20.co.uk

MX records

  • ezycargo.com.inbound10.ttasia.com
  • ezycargo.com.inbound20.ttasia.com
  • ezycargo.com.inbound10.ttasia.net
  • ezycargo.com.inbound20.ttasia.net

SPF policy

  • include: amazonses.com
  • include: spf.glshk.com
  • include: spf5.glshk.com
  • include: spf.protection.outlook.com
  • include: sentry-eds.com
  • ip: 202.130.85.100
  • ip: 202.82.42.133
  • ip: 203.85.70.133
  • ip: 220.241.198.133

Threat-feed evidence

History

Related pages

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