Skip to content

Hostname

winning11.com

Last fetched

winning11.com resolves to 104.21.7.224, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. winning11.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 · winning11.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/winning11.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:431
Registrant organisation
ng yam cheung angus attn winning11.com care of network solutions
Contact emails
angus@angusng.com, b6erd7h4ruzq6kz@proxy.dreamhost.com, nv2pb39v74k@networksolutionsprivateregistration.com, u95dv9cf3rp@networksolutionsprivateregistration.com

Subdomains

Subdomain
mail.winning11.com
www.winning11.com

Showing 2 of 2 subdomains (2 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

  • coco.ns.cloudflare.com
  • walt.ns.cloudflare.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

  • mx1.mailchannels.net
  • mx2.mailchannels.net

SPF policy

  • ip: 118.140.102.1/24
  • a: winning11.com
  • mx: winning11.com
  • a: mail.winning11.com
  • a: smtp.winning11.com
  • a: cn.mx.ball.com.hk
  • a: hk.mx.ball.com.hk
  • a: jp.silly.hk

Threat-feed evidence

History

Related pages

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