Skip to content

Hostname

newsharecounts.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1034
Registrant organisation
artur brugeman
Contact emails
brugeman.artur@gmail.com, ew2tn3an4tn@networksolutionsprivateregistration.com, owner-11930203@newsharecounts.com.whoisprivacyservice.org, owner-8062941@newsharecounts.com.whoisprivacyservice.org, owner@newsharecounts.com.whoisprivacyservice.org

Subdomains

Subdomain
app.newsharecounts.com
public.newsharecounts.com
wildcard.newsharecounts.com
www.newsharecounts.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

  • adaline.ns.cloudflare.com
  • yahir.ns.cloudflare.com
  • ns1.pendingrenewaldeletion.com
  • ns2.pendingrenewaldeletion.com
  • ns10.worldnic.com
  • ns9.worldnic.com
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net

Threat-feed evidence

History

Related pages

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