Skip to content

Hostname

noahgroup.hk

Last fetched

noahgroup.hk resolves to 47.75.233.53, announced in 47.75.128.0/17 by ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. in HK. noahgroup.hk 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 · noahgroup.hkRouting diversity1.5/10Peering density7.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/noahgroup.hk

Resolution chain

IPv6 resolution

No AAAA record for noahgroup.hk is recorded in WhisperGraph.

Attribution

hangzhou alibaba advertising

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for noahgroup.hk. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
autodiscover.noahgroup.hk
mail.noahgroup.hk
www.noahgroup.hk

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • vip3.alidns.com
  • vip4.alidns.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

  • noahgroup-hk.mail.protection.outlook.com

SPF policy

  • ip: 101.231.75.105/28
  • ip: 58.33.122.112/28
  • ip: 112.65.140.146/29
  • ip: 116.236.213.146/30
  • ip: 220.196.31.160/28
  • ip: 58.246.51.206/29
  • ip: 101.52.248.96/29
  • include: spf.protection.outlook.com
  • a: noahgroup.hk
  • mx: noahgroup.hk
  • ip: 20.157.213.37
  • ip: 20.187.124.43

Threat-feed evidence

History

Related pages

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