Skip to content

Hostname

winupdate.live

Last fetched

winupdate.live resolves to 159.198.68.170, announced in 159.198.68.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. winupdate.live is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:51:26 GMT
Last seen on a feed
Sun, 13 Sep 2026 00:52:19 GMT

Nutrition Label

WHISPER CANON · winupdate.liveRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/winupdate.live

Resolution chain

IPv6 resolution

No AAAA record for winupdate.live is recorded in WhisperGraph.

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
15fddb6c50a240a7b1775521bbbe324f.protect@withheldforprivacy.com

Subdomains

Subdomain
www.winupdate.live

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.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

  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com

SPF policy

  • include: spf.efwd.registrar-servers.com

Threat-feed evidence

History

Related pages

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