Skip to content

Hostname

winnergroup.com

Last fetched

winnergroup.com resolves to 13.227.192.17, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. winnergroup.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 · winnergroup.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/winnergroup.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
whois agent
Contact emails
fqllgmvky@whoisprivacyprotect.com, mmcwnwdd@whoisprivacyprotect.com, xnckydpv@whoisprivacyprotect.com

Subdomains

Subdomain
coljuegos.winnergroup.com
mail.winnergroup.com
tr199138152.winnergroup.com
www.winnergroup.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-310.awsdns-38.com
  • ns-924.awsdns-51.net
  • 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
  • ns-1418.awsdns-49.org
  • ns-1589.awsdns-06.co.uk

MX records

  • winnergroup-com.mail.protection.outlook.com

SPF policy

  • include: spf.ipzmarketing.com
  • include: spf.protection.outlook.com
  • include: spfa.alinto.net
  • include: mailer.g-stock.net

Threat-feed evidence

History

Related pages

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