Skip to content

Hostname

gshopper.com

Last fetched

gshopper.com resolves to 47.251.33.224, announced in 47.251.0.0/17 by ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. in US. gshopper.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 · gshopper.comRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/gshopper.com

Resolution chain

IPv6 resolution

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

Attribution

hangzhou alibaba advertising

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
zaihe network technology co., ltd. shanghai
Contact emails
it@b5m.com, it@gshopper.com

Subdomains

Subdomain
accessories.gshopper.com
amazing.gshopper.com
apidocs.gshopper.com
autoparts.gshopper.com
bags.gshopper.com
battery.gshopper.com
bazaar.gshopper.com
beautiful.gshopper.com
beauty.gshopper.com
bicycles.gshopper.com
bigdeal.gshopper.com
blog.gshopper.com

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

  • ent01.dnspod.com
  • ent02.dnspod.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

  • mxbiz1.qq.com
  • mxbiz2.qq.com

SPF policy

  • include: spf.ipzmarketing.com
  • include: spf.mail.qq.com

Threat-feed evidence

History

Related pages

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