Skip to content

Hostname

sharexhub.com

Last fetched

sharexhub.com resolves to 160.30.208.11, announced in 160.30.208.0/24 by WEBHOSTINGHOLDINGS - Webhosting Holdings LLC in SG. sharexhub.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 · sharexhub.comRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.7/10canon.whisper.security/host/sharexhub.com

Resolution chain

IPv6 resolution

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

Attribution

webhosting holdings

ORIGIN_AS

WHOIS identity

Registrar
iana:168
Registrant organisation
domain proxy service. lcn.com
Contact emails
ukproxy@lcn.com

Subdomains

Subdomain
chat.sharexhub.com
mail.sharexhub.com
webmail.sharexhub.com
whatsapp.sharexhub.com
www.sharexhub.com

Showing 5 of 6. View all subdomains →

Mail and authentication

Nameservers

  • 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
  • ns5.private-nameserver.net
  • ns6.private-nameserver.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

MX records

  • mx1.mxfilter.net
  • mx2.mxfilter.net
  • mx3.mxfilter.net

SPF policy

  • a: sharexhub.com
  • mx: sharexhub.com
  • include: spf.mxyeet.net
  • ip: 160.30.208.11

Threat-feed evidence

History

Related pages

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