Skip to content

Hostname

evostore.com.np

Last fetched

evostore.com.np resolves to 104.21.85.13, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. evostore.com.np 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 20:06:23 GMT

Nutrition Label

WHISPER CANON · evostore.com.npRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/evostore.com.np

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for evostore.com.np. 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

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • bruce.ns.cloudflare.com
  • lina.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

  • mx.zoho.com
  • mx2.zoho.com
  • mx3.zoho.com

SPF policy

  • include: _netblocks.google.com
  • include: _netblocks6.google.com
  • include: zohomail.com
  • a: evostore.com.np
  • mx: evostore.com.np
  • ip: 194.195.112.195

Threat-feed evidence

History

Related pages

Pivot from evostore.com.np 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: "evostore.com.np"})-[: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.