Skip to content

Hostname

cubshq.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:895
Registrant organisation
contact privacy inc. customer 124202181
Contact emails
ozkglnd2zea1@contactprivacy.email, e3fb3d3af3ea77200cdfc3709109671c2762addd3b77ed7c571edec57c3305a4@cubshq.com.whoisproxy.org

Subdomains

Subdomain
images.cubshq.com
static.cubshq.com
t1.cubshq.com
www.cubshq.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

Mail and authentication

Nameservers

  • curt.ns.cloudflare.com
  • suzanne.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

  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

SPF policy

  • ip: 68.183.119.112/32
  • include: amazonses.com
  • include: google.com
  • include: _spf.google.com
  • include: _spf.mx.cloudflare.net

Threat-feed evidence

History

Related pages

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